ASP.Net projects not loading in VS.Net after SP2 for XP installed

[Guest]

Hi,

I am having a problem with .Net / Visual Studio that I can't find the cause
of. I have searched newsgroups and the web and find people with similar but
different (I think) problems. Here's the issue and some of what I've found
out - I really hope it's familiar to someone and there's an answer!

I have a solution with about a dozen projects, including 2 asp.net web
applications and 1 asp.net web service project. Having migrated to a new
development machine I can get all projects added into the solution except for
the 2 asp.net web application projects. The error I receive is (the somewhat
notorious, it seems) "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."

Initially, as I had copied the whole solution from my old pc, it seemed that
SP2's Zone Identifiers were causing the problem. I tried running
ZoneStripper
(http://www.jameskovacs.com/blog/PermaLink.aspx?guid=6985963b-3d85-41ae-bca8-5f9efe2a79c7) but that didn't help.

In case that utility didn't work for me, I deleted one of the asp.net web
app project folders and pulled it out of VSS using the VS.Net "Add Project
From Source Control..." menu. This went through the usual steps of creating
the project folder and getting some initial project files but then threw up
the above error, followed by the dialog "Unable to read the project file
'MyApp.csproj'. The system cannot find the path specified".

So, still no joy.

Next, seeing that some of the project files had been successfully pulled out
of VSS by VS.Net, I tried to "Add Existing Project..." to the solution. In
the file dialog that appears, I navigated to and select the MyApp.csproj
file. Lo and behold the project gets added, all the source gets pulled from
VSS and all's well for a while.

Unfortunately, after closing the solution, next time I open the solution
(which now contains the MyApp asp.net project) I get the same errors as
before. In order to work on the project, I have to remove the project from
the solution and repeat the "Add Existing Project..." process again.

Other factors that might be relevant are:
* My whole solution is on the local disk (C
* I'm using WinXP SP2, VS.Net 2002 & .Net 1.0 SP3
* I don't see any button on the Explorer Properties page for a project file
about "Unblocking" the file or any source code files

All other postings I've seen appear to relate to either people putting their
project files on a network share or people whose files came from another
computer; neither seems to be the case here.

Anyway, thank you for wading though all that! If anyone can shed any light
on what's going on and why I'm seeing these errors, I will be most grateful.


Conan

 

[Kevin Yu [MSFT]]

Hi Conan,

We have reviewed this issue and are currently researching on it. We will
update you ASAP. Thanks for your patience!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[Steven Cheng[MSFT]]

Hi Conan,

Welcome to ASPNET newsgroup.
As for the problem you mentioned, I did see some other community members
posting the same issue in the group. Some one even encountering the problem
on WIN2003 machine( though I didn't correctly repro the problem they
mentioned ).

I think the problem you're suffering is somewhat related to the solution
file or the ASP.NET project file's location setting. As you mentioend that
you're using VSS, is it possible that after you close and reopen your
solution, the solution or project file is retrieved from the VSS database
and override your modification? Would you please perform the following
steps:

1. temporarly isolate your solution and the ASP.NET projects from VSS so
that your modification won't be revert back to the original when we do
some modification on it. (Like you've tried before that removing and adding
the asp.net projects again)

2. Generally the "The project location is not fully trusted" error occured
when project files are located in a UNCShared. If your files are all on
local disk, I think we may have a check in the Solution file and asp.net
project's webinfo file( these files contains the url location of your
projects). If you're using Visual C#, the webinfo file's extension will be
csproj.webinfo , if using VisualBasic.net , it'll be vbproj.webinfo. Please
open the webinfo file of your asp.net projects, you'll found something like

<VisualStudioUNCWeb>
<Web URLPath = "http://localhost/DotNetNuke/DotNetNuke.vbproj" />
</VisualStudioUNCWeb>

in the .webinfo file. Also, the same URL will exist in the Solution file.
If you find the URL is pointed to the original site's remote url , you can
try changing them to your local url(the according localhost/... path) to
see whether it helps.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Guest]

Hi Steven,

Thanks for responding to my query. There's good news and bad news from my
side.

The good news is that I have managed to load my projects successfully now.
The bad news is that I still don't understand what the problem was or where
it lay, which is a bit of a shame.

For the record, and in case it helps anyone else out there, here's what I've
done.

I started, as you've suggested with step one and went to unbind all my
projects from VSS. This wasn't initially possible as, whenever I clicked on
the "Change Source Control..." menu item, after few seconds I received an
error dialog containing the text "Unspecified Error". I decided to remove
the project that is failing to load properly from the solution (I had added
this temporarily after opening the solution via "Add Existing Project..." as
described in my previous post).

Once the problematic project was gone I could unbind all other projects in
the "Change Source Control..." window. When I re-added the problem project,
I couldn't unbind it as it caused the "Unspecified Error" again. As I was
unable to complete step one from your post, I resorted to blowing away the
whole solution directory structure and starting afresh (something of a last
resort, considering how long it takes to get all the projects from a remote
VSS repository & reconfigure them).

I created a new blank solution and set about doing an "Add project from
source control" for each project. All projects loaded in fine as expected
except the problem project. Adding this one caused a dialog stating that
adding the project had failed and that closing and re-opening the solution
would fix the problem. Doing that didn't fix it, so I went to "Add existing
project..." and navigated to the problem project's csproj file. This threw
up several errors in succession about missing files but they must have been
subsequently created as the solution now works fine and all projects open
correctly when I open the solution.

I can only assume that the problem was caused by something set in the
solution file as that's really all I think that's changed. If the problem
reoccurs or I find out what was at the bottom of it all, I'll post my
findings.

Thank you for your time and help.


Conan

 

[Steven Cheng[MSFT]]

Thanks for your response Conan,

Seems you completely create a new blank solution and move those projects
into it and it can worked though that cost a lot of effort. Have you
checked the
<VisualStudioUNCWeb>
<Web URLPath = "http://localhost/DotNetNuke/DotNetNuke.vbproj" />
</VisualStudioUNCWeb>

setting in the web project's " .csproj.webinfo" file or the corresponding
url of the webprojects in your solution file? (We can open them through
notepad to check the content as plain text , they're xml). If the url path
in those file are not the correct path according to your local IIS's server
address(http://localhost/....), please try changing them to the correct
local address and try again to see whether this can help(without recreate
new solution and add/remove the webproject timely).

Anyway, I still think this is a problem caused by project files in VSS
enabled enviornment since VS.NET2003 has put too much location related info
in the project file which will cause problems in source control scenario.
I've also seen such problems before. Anyway, please feel free to post here
if you have any new findings.

Thanks & Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Guest]

Hi Steven,

Yes, I forgot to mention that. I did check the urls in the webinfo and
solution files and they all were set correctly to the same url.

Conan

 

[Steven Cheng[MSFT]]

OK, Thanks again for your followup.

En, that's really not what I've expected. Anyway, please feel free to post
here if you figure out or encoutering the problem again later. Also, for
such problem, I recommend that you create a demo solution which contains a
webproject and add them into VSS and do some tests, that can help use get a
clearer view of such problem.

Wish you good luck!

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Guest]

FWIW we had this problem where we got the "unable to read the project file"
when we tried to add a web service to a solution. The web service was able to
load into other projects with no problem. We could see the project and it
worked just fine but something was wrong with the Solution configuration that
would not load it. The problem began because the person had the project
incorrectly named in the solution so they removed it from their computer and
downloaded it again from Source Safe.

There is some bug where the Solution has a hidden configuration for web
services or web projects that is not totally cleaned up when you try to
remove it.

Our solution, which isn't really acceptable, was to totally create a new
solution and re-add the projects.

 

[Guest]

FWIW we had this problem where we got the "unable to read the project file"
when we tried to add a web service to a solution. The web service was able to
load into other projects with no problem. We could see the project and it
worked just fine but something was wrong with the Solution configuration that
would not load it. The problem began because the person had the project
incorrectly named in the solution so they removed it from their computer and
downloaded it again from Source Safe.

There is some bug where the Solution has a hidden configuration for web
services or web projects that is not totally cleaned up when you try to
remove it.

Our solution, which isn't really acceptable, was to totally create a new
solution and re-add the projects.

 

[Hans-Christian Holm]

I also got this error when moving a solution to another computer. I
have no idea whatsoever what caused the error, but removing the .suo
file did the trick for me.

 

[Guest]

Hi,

We had the same problem.
This error was due to changing the name of the project (.csproj).

The content of the file .csproj.vspscc (Visual Studio Source Control Project
Metadata File) in the sourcesafe project has a wrong filename to .csproj.

Extract the file .csproj.vspscc and correct the filename of the .csproj and
the error disappear.

Here is a sample of the .csproj.vspscc file
""
{
"FILE_VERSION" = "9237"
"ENLISTMENT_CHOICE" = "COMPULSORY"
"PROJECT_FILE_RELATIVE_PATH" = ""
"NUMBER_OF_EXCLUDED_FILES" = "0"
"ORIGINAL_PROJECT_FILE_PATH" = "http://localhost/Project/Web.csproj"
"NUMBER_OF_NESTED_PROJECTS" = "0"
"SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROVIDER"
}


Correcting the value for "ORIGINAL_PROJECT_FILE_PATH" resolve our problem.

Bye!