Exception System.Security.SecurityException has accured

[Guest]

Hi

The Visual Basic 2003 application that I wrote was installed on Windows 2003
Server and we are trying to acess it across the network from Windows XP Pro
but we are getting An Exception System.Security.SecurityException has accured
when we try and run it.

The application is a Executable the network administrator do not want to add
the application to the .Net Wizard Trust because they fear that it will open
up a bunch of security problems on the entire network. So I was wondering if
there is any way to include some code in the application to make it without
any trust levels? If so can you please give me a example of how to do it.
Checked the internet and I was unable to find any that would work with my
application.

I am using windows server 2003 and if you add a application .net trust
assembley how can I do this please?



Thanks
Phillip Taylor

 

[Norman Yuan]

Since the code is not installed on running computer locally, instead it is
loaded from a network share, it is considered as "unsafe" by default, hence
the error. You must configutre the .NET FW on the running computer to give
required trust, so that the code loaded from outside computer can run, using
either .NET Configuration applet or .NET Framework configuration wizard.

Why your netwrok admiistrator does not want to do that? It seems he need to
do some study on that. The .NET configuration tool is just designed for
that. He should learn how to configure it properly. It is not like that if
you do the configuration, then you get the computer wide open. You simply
have to know how to do it and do it correctly.

If you have a few small .NET destop apps that you'd like load from a network
share, in order to simplify deployment, you can use the .NET configuration
applet or Caspol.exe tool to configure a new work folder as trusted code
group (make it read-only to all users, and only the admin can copy files
in). I usualy give full trust, but you can give different level of trust
based on need. However, if the .NET app is big or complicated, create an
installation package and install it locally would be better.