|
| Project location not fully trusted by .Net runtime |
|
|
|
|
| Messages |
|
Related Types |
This message was discovered on microsoft.public.dotnet.languages.vb.
| Neil Robbins |
| GOOD ANSWER |
I am getting the following message when attempting to open a solution from
another computer on my network:
"The project location is not fully trusted by the .NET runtime. This is
usually because it is either a network share or mapped to a network share
not on the local machine. If the output path is under the project location,
your code will not execute as fully trusted and you may recieve unexpected
security exceptions."
Could anyone offer a way of getting a location on another machine to be
trusted?
Any help as always much appreciated.
|
|
|
| |
|
|
| |
| |
| CJ Taylor |
| GOOD ANSWER |
You have to set that up under your Enterprise Security Policy in your .NET
Conifguration under control panal.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/entsecpoladmin.asp
"Neil Robbins" <Click here to reveal e-mail address> wrote in message
news:%Click here to reveal e-mail address...
[Original message clipped]
|
|
|
| |
|
|
| |
| | |
| |
| Ben Bragdon |
| GOOD ANSWER |
So question for you -- I know that that's how you change the security policy machine by machine, but here's what I've got, and if you can figure it out you'll definately get a cookie (derr...or something). I have an entire network of machines that require me to change the "Local Intranet" setting in the policy configuration to the "Full Trust" setting. I'm trying to figure out a way to deploy the setting over the network without having to go to each machine and do it. Any ideas?
Thanks,
Ben
--------------------------------
From: Ben Bragdon
|
|
|
| |
|
|
| |
|
|
|
|
|
|
|
|
|
BootFX
Reliable and powerful .NET application framework. |
|
|
|
|
|
|
