(Not logged on) | Register | Log On

You can subscribe to this discussion group using an RSS feed reader. .NET Questions

Questions and Answers on any aspect of .NET.

This discussion group is now closed.

Have a question about .NET development? Try stackoverflow.com, a worldwide community of great developers asking and answering questions 24 hours a day.

The archives of .NET Questions contain years of Q&A. Even older .NET Questions are still online, too.

The project location is not trusted.

No, it's not the obvious solution.

We all know that by default you get this if you open a project stored on a UNC path.  But we also know that you can change the security policies so that code on your local intranet, or on a specific path, gets FullTrust just like local machine code.

Which is what I did, long ago, and it worked fine...until this morning.  Last night I could open projects stored on my (home) server, and everything worked great.  This morning I'm getting "The project location is not trusted", even though I've double- and triple-checked the .NET security settings.

Any ideas?  (In the meantime I'm going to go reinstall .NET 2.0 or something.)
Kyralessa Send private email
Friday, April 21, 2006
 
 
Got it.  After much frustration.

It turned out the problem was sparked by TiddlyWiki, discussed in a thread on the Business on Software board.

In order to get TiddlyWiki to live on my network share, but still work (and save) in IE, I added my server as a Trusted Zone in IE.

So my code fell under the Local Intranet set of permissions, but also the Trusted Zone set of permissions.  .NET chose to use the most restrictive set of permissions (Trusted Zone).  Once I removed the server from Trusted Zones, I was back to normal.

(Which doesn't explain why things worked last night but not today, since it was _two_ days ago that I set up TiddlyWiki, but whatever.)
Kyralessa Send private email
Friday, April 21, 2006
 
 
Well.

I thought I could solve both problems by adding the specific network folder to Trusted Sites instead of the whole server.  But every time I try to add the folder (e.g. \\MYSERVER\MyPath\MyFolder) to Trusted Sites in IE, when I come back it's changed it to the whole server (e.g. \\MYSERVER).  Which naturally brings back the permissions problem.

I tried various kinds of formatting (forward slashes, using file://, not using file://), but nothing works.  I even tried mapping a network drive to the path I want and using that, but it still gets around me and puts in the whole server.

So, again:  Any advice?  Does anyone have any insight on why it's apparently impossible to add just one folder (instead of a whole PC) to Trusted Sites in IE?
Kyralessa Send private email
Friday, April 21, 2006
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz