[ACCEPTED]-Warning displayed when adding solution to Team Foundation Server 2010-tfs

Accepted answer
Score: 52

Your solution folder structure should resemble:

Solution Root folder
├── .sln solution file       
│
├── Project1 folder
│   └── Project1.csproj   (or .vbproj)
│
├── Project2 folder
│   └── Project2.csproj   (or .vbproj)
.
.
.

0

Score: 7

As described in this Visual Studio forum 11 post (link below), the basic issue is that 10 a project in the solution is outside of 9 the sub-tree that the solution itself is 8 in. This can possibly lead to problems if 7 another user maps the different subtrees 6 differently in his workspaces than the user 5 that is checking in. The cross-tree references 4 will no longer work. The dialog is only 3 a warning, but can be continued if you know 2 your team doesn't split up the code tree 1 with complex workspace mappings.

https://social.msdn.microsoft.com/Forums/vstudio/en-US/29579a28-9de0-4fc6-a253-b38191aa4fdc/must-projects-be-added-under-binding-root-of-solution?forum=tfsversioncontrol

Score: 5

For me it was like this that I tried to 5 add the solution from another location already. I 4 then had to clean the workspace which was 3 created for the other location.

For Visual 2 Studio 2013 you can find the workspace settings 1 under:

File -> Source Control -> Advanced -> Workspaces...
  1. On the Manage Workspaces dialog select your workspace you work with
  2. Hit Edit....
  3. On the Edit Workspace <yourworkspacename> dialog
  4. clear the "wrong" location

Try to add the solution again.

Score: 0

The following issue can sympomatically manifest 14 the error you reported. Remember, referenced 13 assemblies need not be in any specific location 12 in either TFS or in the file system of your 11 workstation.

An underlying problem is that 10 some types of projects default to the "Client" version 9 of the targeted .NET Framework. The Client versions 8 strip out assemblies that are usually not 7 used in deployable projects. Furthermore, any 6 assembly your project references must also 5 not reference assemblies omitted by the 4 Client profile.

Simply change the Target framework 3 setting of your project to the full framework 2 version.

Check out my blog post, regarding 1 this issue: http://thecurlybrace.blogspot.com/2010/09/visual-studio-wears-sabots.html

More Related questions