Posted by Mike Saunders on September 16, 2008 at 07:17:04:
In Reply to: VB.Net Project posted by Greg on September 15, 2008 at 06:53:52:
I think Serge is on the right track.
Perhaps more detail on the error message could be provided.
A While ago I remember something similiar, (currently all my apps run from a local path.)
If you google for "fully trust a network folder" you will find some more info.
Please note that I have never done this and am just passing along the information.
Use it at your own discretion and risk.
From www.experts-exchange.com
Okay, some background first. IT managers and home users have been having problems with viruses, spyware and other unwanted software. The question is, how do you trust an application to do what it is supposed to do, without giving it full rights to do everything. Microsoft's answer in the .NET environment is something called Code Access Security.
Trained .NET developers are able to determine which privileges their software needs, and to request it as part of the installation. Since installed software is normally run from a local hard disk, Microsoft decided that typical machines should trust code that is run from there. However, code that is run from a networked drive, or an Intranet system, may not be as trustworthy, and code from the Internet......
So how does it work? This is a bit of a lengthy topic, but essentially there are two parts to it. Firstly, there are code groups that associate software with permission sets. Secondly, these Permission Sets group a set of smaller permissions, such as "Allow read-only access to files on my computer". As part of software configuration or installation you need to do one of the following things:
1) Trust the location where the software is located directly, or
2) Install the software such that it becomes trusted, or
3) Configure the security system so that it is not a problem
Note that the reason VB6 code doesn't do this is that it doesn't have the notion of code security. As a result, it has a much greater potential to be hacked and end up doing something you don't want.
So, to configure .NET to trust a share, follow the instructions in http://blogs.msdn.com/shawnfa/archive/2004/12/30/344554.aspx. Note that this should work on any machine that .NET Framework 2.0 (not SDK) has been installed. If the DLLs or executable change, you won't need to change the policy.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.