> Not all assemblies are allowed to be excuted from the Internet Zone. You
> can use caspol.exe to configure the security for the different zones.
Unfortunately it is difficult to debug security exceptions in v1.0 and v1.1 of the framework, however this is one of the areas that the Visual Studio
team worked on for the upcoming Whidbey release, and you'll see a lot of improvement in their new features. From Whidbey Visual Studio you'll
be able to sandbox your app on the local machine, pretending that it is running with lesser permissions. Then when a security exception is thrown,
you'll be notified of the exact location that caused the exception, and some suggestions you can use to remove the security problem. For more
information, you can check out Ivan and Sebastian's PDC talk: http://microsoft.sitestream.com/PDC2003/ARC/ARC340_files/Default.htm
-Shawn
http://blogs.msdn.com/shawnfa

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they
originated.
--------------------
>From: fc308@hotmail.com
>Newsgroups: microsoft.public.dotnet.framework.clr
[quoted text clipped - 11 lines]
>NNTP-Posting-Date: Fri, 12 Dec 2003 10:28:34 +0000 (UTC)
>Path: cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08.phx.gbl!
newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!fu-berlin.de!postnews1.google.com!not-for-mail
>Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.clr:8975
>X-Tomcat-NG: microsoft.public.dotnet.framework.clr
[quoted text clipped - 13 lines]
>
>Cheers