How to allow ... Visual Studio Source Management Notification "Recently projects were added for this solution"

Question

After some use of Visual Studio 2008, when you open a solution that has been tested in the Visual Studio Team Foundation, a dialog box appears with the message:

Recently, projects have been added to this decision. Do you want to get them from the source?

This happens every time a solution is downloaded (even if no projects have been added). The only way I found to eliminate this minor annoyance is to completely rebuild the SLN file.

Has anyone found a better / easier way?

Answer 1

Hey, this actually happened to me about 4 years ago.

Firstly, it seems to me that someone from your team does not have all the updates that apply to their installation in the visual studio. Go and update all updates to the latest service pack for your version of VS.

Once this is done, untie the solution, fix the file, reinstall it and tell everyone to be the last in your TFS project.

See http://social.msdn.microsoft.com/Forums/en-US/tfsversioncontrol/thread/c2822ef1-d5a9-4039-9d3e-498892ce70b6

http://www.nivisec.com/2008/09/vsts-projects-have-recently-been-added.html

(broken link: http://technorati.com/posts/Yadz3Mj1pxHPSJLlnUs1tL1sIwU5jXa5rNBbIAnYdvs%3D )

Answer 2

I had it recently after we moved a number of projects into a solution. In the end, I decided that every project really appears in the solution file several times with path information! Thus, although the path in the main link of the project was correct, it was incorrect further down the file.

So, go to the .sln file and make sure that the paths in all are specified for each project.

For example, the first link for one of my projects:

Project("{F184B08F-C81C-45F6-A57F-5ABD9991F28F}") = "ObexPushVB", "Samples\ObjectPush\ObexPushVB\ObexPushVB.vbproj", "{E3692A59-D636-48E8-9B57-7DA80A88E517}" EndProject 

In my case, the path was updated correctly. But then we have for this project:

 SccProjectUniqueName8 = Samples\\ObjectPush\\ObexPushVB\\ObexPushVB.vbproj SccProjectTopLevelParentUniqueName8 = InTheHand.Net.Personal.sln SccProjectName8 = Samples/ObjectPush/ObexPushVB SccLocalPath8 = Samples\\ObjectPush\\ObexPushVB 

So, all of these paths need to be updated too! After I fixed it manually, everything was fine. (The sample is after BTW correction).

Answer 3

This message will also appear if your solution has a link to a project whose location is outside the solution catalog, but it does not physically exist (i.e. you did not check it before opening the solution). Then VSS (or TFS) will send you this message and clicking "OK" will automatically receive the latest information about the project that is missing, so your solution will not have any downloaded projects.

EDIT

A reading that bothers me again. Basically, you get a message if your solution has a source binding to a project that is not inside the folder where your solution is located, and that the external project does not physically exist on your computer. Clicking OK will check the project for you.

Answer 4

In my case, it was a link to a test project that was deleted.

I noticed that when I inspected all the projects in the solution explorer. Our team uses folders with solutions, so it was not normally visible, and because it was a test project that had no effect on the application.

After deleting a project from the solution, messages are no longer displayed.

Answer 5

I am working with Visual Studio 2013.

For me, this happened after changing the folder structure of my solution (I added a subfolder for the project directly to the source code explorer). I got rid of this boring error by removing all projects from my solution using explorer. After that, I closed Visual Studio, manually edited the .sln file, and deleted the entire section:

 GlobalSection(TeamFoundationVersionControl) = preSolution 

To finish, I simply added the projects back to the solution as "Existing Projects" using explorer. Visual Studio automatically recreates the remote section of the .sln file.

Answer 6

The same error message may occur if someone adds a project, edited the edited solution file, but does not add the project directory to the source code.

To shorten the long history, this error may mean that there is a link to the .csproj file in the .sln file, but .csproj itself is physically absent.

Answer 7

In my case, I renamed the (n) (uploaded) project to VS. He correctly transferred the project to a new folder, and the data was not lost. However, the solution file still pointed to the old directory, which still existed but was empty (so the project could not actually be loaded).

After removing the project from the solution (which was not a problem because the folder was already empty), the problem was resolved.

Re-adding a project from a new location was not a problem either.

Answer 8

I had this problem after moving several unit test projects that were under source control (VSTS) to another folder. After that, whenever I opened a branch, I would add that "Projects have recently been added to this solution. Would you like to get them from the control source?" mistake.

For some reason, the csproj file from the trunk was not under source control, which meant it was missing from the forked version. I believe this happens sometimes after moving projects controlled by the source.

To fix this, I opened the source source trunk, used Source Control Explorer to add the missing file (s), then merged the trunk with branches to copy through the missing csproj file.

After that, I was able to open forked versions without warning.