VS.Net 2003 on Windows Server 2003

[Joe Fallon]

I just set up a new box and am trying to get into a web project.
I moved from Windows 2000 Server where this app worked fine.

Now I get this error message when opening the solution file:
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 receive
unexpected security exceptions.

I tried some of the hints in Help but no luck.
I am not sure what to do next.

Any advice on how to handle this?

 

[John Soulis [MSFT]]

Not sure if this applies, but you can let me know.
This is due to a change in IE security on Windows 2003
Server. It now uses the "Internet Explorer Enhanced Security
Configuration." This
change is discussed in article 815141 Internet Explorer Enhanced Security
Configuration Changes the Browsing Experience
http://support.microsoft.com/?id=815141. The effects of this change are
discussed
Use an
FQDN or IP Address http://support.microsoft.com/?id=303650. Basically, IE
no
longer trusts Network shares at the local Intranet level, but considers
them to be at the Internet level.

To resolve this, we can either move the Code Group that grants trust to the
Internet_Zone, (or directly under All_Code) or we can specifically add the
URL to
the trusted web sites list in IE. For this you go into IE and from the
Tool menu
select "Internet Options" and then the Security tab. Select Local Intranet
and
click on the Sites button, then the Advanced button on the next dialog.
This
should take you to a dialog where you can enter your share under "Add this
Web site
to the zone:". Enter File://ComputerName and click on Add. It should add
the
machine to the "Web sites" list. Click OK until you get back to IE. This
specifically adds the machine to the LocalIntranet_Zone, so you may want to
use the
other solution if you don't want to trust the entire machine.

Thank you,
John Soulis
Microsoft, ASP.NET

This posting is provided "AS IS", with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

 

[Joe Fallon]

John,
Thank for posting.
But the Security error was a red herring.

The REAL problem is you can't copy a web project from one PC to another when
it is under VSS source control.
Once I resolved the VSS issue everything was fine.
(I used a Support call to MS tech support - they were great!)

PS - When using VSS over a VPN, be sure to turn off Anti-Virus software!
It runs 10-20 times faster!!