The Project Location is Not Trusted

By: Justin Braun
Posted on: November 25, 2007

This dialog box appears if you attempt to open or create a client project on a Universal Naming Convention (UNC) path. By default, a UNC path is not a trusted location for a project. Your project might not run correctly when you attempt to debug or run from this location.

If you need to work with code inside Visual Studio that is located on a network or remote location (non-trusted project location), you can modify the .NET Code Access Security Policy using the .NET Framework Configuration Tool and the Code Access Security Policy Tool.

MSDN has an article on what’s required to add UNC or network locations as trusted project locations.

Link: http://msdn2.microsoft.com/en-us/library/bs2bkwxc(VS.80).aspx

Related Articles

C#: Persisting User Settings After An App Upgrade

Seems like it should work without too much pain, but the fact of the matter is each time you increme

Creating an Add-on for Internet Explorer with Add-In Express

Introduction For some time I have had a few ideas for Internet Explorer add-ons that I’d like to

PowerShell with Compellent and Exchange 2010

I’ve been doing lots of work in the lab lately with Exchange 2010 to understand all the new change