I experienced the same problem when attempting to test my HTTP deployed application (which uses a database connection). The assembly is stong named and I couldn't get it to trust "this one assembly" or all with same public key. I ended up giving Local Intranet full trust so that I could move on with testing. How secure is that?
Seang -----Original Message----- From: Chris Sells [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 3:33 PM To: [EMAIL PROTECTED] Subject: [DOTNET] SP1 and trusting an assembly? When attempting to trust an assembly on my intranet (on my machine, actually) using the Trust an Assembly wizard, if I choose to just trust "This one assembly", the next page says: "Due to your existing security policy, the wizard is unable to increase the level of trust for this assembly. No changes were made to your policy." What is it about my "existing security policy" that stops me from trusting a particular assembly? The assembly is signed and I'm able to trust all assemblies with that key, but not just that one assembly. This is safer?!? Chris Sells http://www.sellsbrothers.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.
