This is by design. Strong-named assemblies (like System.Runtime.Remoting) can not be called by partially trusted code (code that has any permission set other than full trust) unless that strong named assembly is decorated with the AllowPartiallyTrustedCallers attribute. System.Runtime.Remoting does not have that attribute, with good reason. You will either need to give your component full trust or use another mechanism to communicate with the server. Why do you want to use remoting from within IE?
-----Original Message----- From: Steve Albert [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 2:26 AM To: [EMAIL PROTECTED] Subject: [DOTNET] remoting from browser, security bug (?) Hi. I'm writing a winforms control which is hosted in IE. I'd like to use remoting to communiate with the server. If I give FullTrust (CAS right) to the component it works fine. But if I give Everything or give all rights to the component (one by one, granting everything, including skip security check) it doesn't work. I wrote a very simple control with only one button, and a method constructing a new TcpChannel object. Here is the code (very, very simple): private void Test() { MessageBox.Show( "c" ); new System.Runtime.Remoting.Channels.Tcp.TcpChannel(); } private void button1_Click(object sender, System.EventArgs e) { MessageBox.Show( "calling test now..." ); Test(); } First message box is shown, second is not (!!!). Security error exception thrown. It seems to me it must be thrown by the JIT. any suggestions? has anyone tried to do remoting from an IE hosted winforms control with properly configured security? thanks, Steve You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
