Chris,
I think I've figured this one out. Based on this Q article [1], you can
add a site to the Trusted Sites zone at the machine level [2]. I've
found that the easiest way to do this is to (temporarily) add the site
to Trusted Sites from the IE UI. This will create the appropriate
registry k
According this page [1], "Object-remoting scenarios are not supported
for partially trusted code applications."
[1]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetse
c/html/Aptcatypes.asp?frame=true
-Original Message-
From: Steve Albert [mailto:[EMAIL PROTECTED]]
S
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 d
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 d
accomplish what you want.
Thanks,
Michael
- Original Message -----
From: "John Cavnar-Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 29, 2002 11:15 AM
Subject: Re: [ADVANCED-DOTNET] remoting from browser, security bug (?)
This is by design
I can't answer the SOAP question, but as to the security question, do
this:
Login in to your machine as a local administrator (you're not running as
a local admin all the time, are you?) Open the .Net Framework
configuration tool. Navigate to the Runtime Security Policy and choose
the machine le
