Oh yeah :-) The funny thing is...there is a way around all this stuff. Create an Exe and download it to the machine, then run it. Have that Exe call a Web Service that returns a byte array(s) which is my dll(s) and exe. Then save the array(s) as a file(s) on the harddrive, then kick of the new exe. This will by-pass all that security stuff. So, in a way, the security patch doesn't work....just makes it harder for us to do what we want and puts the pressure on the user to know what he is doing when he runs an Exe that he downloaded.
-----Original Message----- From: Brent E. Rector [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 10:37 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Strongly named assemblies require Full Trust ??? It was a patch that enabled this behavior. It is by design and will not be changing (at least for the foreseeable future). -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -----Original Message----- From: franklin gray [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 8:31 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Strongly named assemblies require Full Trust ??? I have seen something like this too and have put it off hoping MS will come up with a patch soon. -----Original Message----- From: Wayne Kelly [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 1:41 AM To: [EMAIL PROTECTED] Subject: [DOTNET] Strongly named assemblies require Full Trust ??? It appears that to refer to a strongly named assembly, you need to be executing with the "Full Trust" permission set". I created a "Class Library" assembly and defined in it a static method called Foo. I gave that assembly a strong name by specifying a key file. I then created a console application that refered to the strongly named assembly and called the Foo method. If I run the console application with "Full Trust" then it works fine, but if I run it with only the "Everything" permission set, it throws a security exception. If I remove the strong name from the class library then it works fine even with only the "Intranet Zone" permission set. Why should this be? 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. 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.
