index > Team Foundation Server - Version Control > Moving Workspace in Team Foundation ( Web Site Project )

Moving Workspace in Team Foundation ( Web Site Project )

I am struggling to solve the following problem with no success yet.

I had

1 VSTF Solution file + 1 Web Site Project + 1 DLL Project + ...

I moved files and directories between projects. [Checked in] --> Worked fine

I removed all local files from C: and removed workspace reference from VSTF IDE.

( Completely cleared up)

I re-created workspace in disk D: and retreived all project files from VSTF.

Then I was getting some of the warnings like

"Some of the properties associated with the solution could not be read."

But bad enough, original web site project became a goner from solution explore and a bogus empty web project popped up !

( "MyWebSite" --> "MyWebSite_1" )

I tried many things, so far the least destructive solution is to double click solution file from outside windows file explorer rather than from VSTF's source control view.

Here is my questions about microsoft VSTF:

[1] Why does solution file keep absolute file path for web site project inside ?

( eg. "C:\MyWork\MyProject" )

: This should be OK with single user development, I am not sure that is good idea for team members though.

[2] Does above problem tell us to have same absolute local workspace path for web site project development ?

Any suggestions would make my weekend better. Thank you.

Sunkyu Hwang

Why the solution file has an absolute path to the web project is a question for the team that implemented Web projects in Visual Studio. Team Foundation Version Control does not put this value in there. I recommend posting this question to http://forums.asp.net/ (according to this post). Generally, I've seen absolute paths when a relative path will not work (e.g. the two items are on seperate drives).

I am not sure I follow what you mean by the same absolute local workspace path for web site project development. I am going to answer this with the assumption that you are asking if every developer needs to create a workspace with the same local mappings for this solution to work (e.g. everyone would have to put the project in c:\MyWork in the original setup).

Assuming you added the solution to TFS from within Visual Studio, the answer to this question is no, everyone does not need the same local mappings for the solution to open properly. I just verified this on my machine where I moved a web site from my d: drive to my f: drive and I was able to open the solution from my f: drive with no problems. Even though the paths are hard code in the solution file, Team Foundation Version Control can adjust these on the fly based on the relative server paths and your local workspace mappings. We do this for the case where a solution contains projects that exist on another drive.

One thing that could be going wrong is that the path cannot be adjusted on the fly because the project file is not mapped or does not exist locally. Please verify your workspace mappings and make sure your workspace is up to date by doing a "get".

How are you opening the solution? Are you opening it from the local disk or from the Source Control Explorer or from File, Source Control, Open from Source Control?

I was using a file based web site solution. Is this what you are using?

http://blogs.msdn.com

Ed Hintz

Ed,

I just recently encountered the same issue with a web project I have created in VS.Net 2003.

Created the project normally
I updated the virutal dir to point to my workspace path
Checked in the solution and project

After attempting to open a labeled version of the soution, a dialog box opens asking to create a new virtual dir named x_1 because x is already in use. As per your instructions I will post this to the ASP.Net forum, but I figured it would not hurt to post it here as well.

Ariel Valentin

how strange, I opened it as "an existing project from the web" and it created a new solution, when I diffed the files the "bad" solution had extra information in it. Here is a blog that I found helpful http://tonesnotes.com/blog/2003/11/visual_studio_net_2003_solutio.html.

So I guess the root of the problem was the solution after all.

Ariel Valentin

After spending many days, I have figured out that somehow solution file has been corrupted during various file and directory renaming.

Now, the question became "how to fix this problem?".

A couple of days ago, I happend to discover "change source control..." menu from the VSTF IDE, and found out that the solution file's binding to the source control was broken.

Simply re-bind the file with solution file was not successful.

So I have re-created a blank solution from local box and re-atach all our projects.

Then I was able to bind this solution file through source control where it magically removes most of absolute paths as well as adding many extras.

All this happened because I had no idea how source control binds solutions and projects.

If in future release of VSTF, any pop-ups warning broken bindings would surely make developer's life easier.

Sunkyu Hwang

Congrats on your success! Sadly, this continues to be an issue for every new project my team creates and I am afraid it is just easier (although not ideal) for us to have external solutions for each developer on the team.

Ariel Valentin

reply 6