“The project location is not trusted”

After installing Windows 7 and Visual Studio 2010 on my laptop, I ran into the well-known message “The project location is not trusted”. I thought all I had to do was follow the instructions in this MSDN article to get my development share to be trusted again, but this doesn’t seem to work.

I already tried adding the new child group under the Internet_Zone in stead of the LocalIntranet_Zone, and using the complete server name and the server IP address in stead of the name of the server. All of these steps did not solve the message popping up…

I’m open to any suggestions, ‘cause this problem is beginning to drive me nuts.

Published Wed, Aug 12 2009 7:55 PM by Rick van den Bosch
Filed under: ,

Comments

# re: “The project location is not trusted”

I believe this is a bug. I've had the same lack of success. I've even tried both the x32 and x64 version of the .net caspol.exe to set the paths from both v2 and v4. I know the .net framework configuration snap-in only is able to edit the x32 settings, so I assume there’s some issue around x64 and v4.

Previously I had the problem with VS 2008 when working with solution files stored on a network share and I was able to resolve it. I can open a solution file from a UNC location with 2008 fine, and then open the same file in 2010 produces the warning. I'll be submitting this to connect...

Saturday, September 19, 2009 10:20 AM by Derek Gabriel

Leave a Comment

(required) 
(required) 
(optional)
(required) 
Please add 6 and 3 and type the answer here: