I think it has something to do with the level of security you have set for intranet in IE. I may be mistaken, but I think the security we set using the config wizard is only for managed apps and that we can't set a higher level then what is available in the over all security settings. Just a guess because I ran into the same problem. All I have to say is that I am putting all this stuff aside in hopes MS fixes bugs and documents things better. When I say bugs, I mean I have an app that will only run with fulltrust, but it doesn't have any code or controls that would be requesting a high level of security. Anyway, we will wait and see.
-----Original Message----- From: Chris Sells [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 5: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.
