VS 2003 Unable to get the Project from the web server

Adding a local VSS copy from test server

[dcat0917]

My team recently upgraded from VS 2002 to VS 2003 .NET and in turn I was asked to convert the VSS project to 2003 when creating the local copy on my machine. I was able to successfully install VS 2003, with 1.1 framework SDK no problem.

I have done this a few times before with no problems. I created a virtual directory in IIS before adding the project locally. I then performed a VS - File - Source Control - Open from Source Control - logged into VSS - pointed to the Solution I desired to copy down to my local directory where my IIS virtual project resides and whamo..everything installed perfectly. I now have a local source controlled copy of the upgraded 2003 application.

Now the problem: Following the same procedure, my colleague gets the "Unable to get the Project from the web server" message when he selects the VSS project Solution to copy down. We have scoured MSDN etc for some resolution. I found a link on this site addressing this exact problem ealier this year that was resolved by following my procedure.

We suspect that VSS cannot resolve the path properly for his machine but cannot determine why. I have verified security on all folders and in VSS for the user.

Can anyone give some thoughts on what may be causing this error? Apologies for the long post and thanks in advance.

dcat0917

[Easy_Coder]

I ran into something very similar last year and to date its been unsolveable...

I did the same thing you did... upgraded vs.net from 2002 to 2003. All of my projects are completely kosher except for this one project.

The error message I receive indicates that I'm unable to open the project becasue the .net framework is not installed on the server. The framework is on the server though.

I worked on this for about 2 straight weeks with a team of support engineers and no matter what we did nothing changed. We even blew away the entire project from the server so that I could recreate the site from scratch... no worky!

To this day the only way I can open this project is to use an old machine that is still running Visual Studio .Net 2002.

[dcat0917]

Thanks for the feedback Easy_Coder;

Certainly uplifting information (argh)...I guess the upside is we've only beat our heads on the table for two days now!

Updated attempts to correct this have included:
1.Cleaning out the VSWebCache folder in Doc-Settings on both local and build server for our developers name.
2.Adding the Solution first, then adding the Project - no go.
Since I do have a perfectly working project on my machine this is doubly frustrating. Our next step may involve removing the project from Source Safe then re-adding it. I am hesitant to do this as I may then lose my working copy.

I'm supporting a couple hundred users with the application and I really am getting frustrated with this. Maybe I need to back it off to 2002 again...

[Easy_Coder]

I guess the upside is we've only beat our heads on the table for two days now!

Thats what I call finding opportunity... If I can jog my memory on anything else I'll sticky you.

[dcat0917]

Well after many lives and a lot of ammunition we were able to get around this lovely generic message. Going from Korby Pernell's post at: [blogs.msdn.com...]
I decided to nuke the VSS connections and create a non-source controlled version on my local, then add that back into VSS. The thought was then to have my staff get the updated project from VSS to their locals via "Add from source Control". The same error message.

I then had one of my guys replicate my process from his machine (thinking some authority I may have or setting we have missed)with the intent that I would then get the project to my local machine. This worked! We both now have a working source controlled project.

We covered about every scenario with IIS virtual directories, VSWebCache folder, Front Page Extensions. Nothing but due dilligence got this done. Apologies, but nothing more to offer the community on this frustrating error other than cover the obvious, then keep pounding at it. (Maybe that should be the new MS marketing plug?)

Regards

[tomasz]

I had similiar problem too, try;
1. Remove all project files including IIS virtual directory from the local box.
2. Create new project using VS2003 which will create new v directory.
3. Copy you old projects files to that location.