I'm trying to migrate code analysis settings from a Team project to a solution. Only thing that happens is that the message "No migration occurred: No files from solution are under source control" shows up in the VS status bar. The solution file and all the projects it contains ARE under source control.
IWe have three Team projects on our Team foundation server. The migration works fine for one of them (first in alphabetical order), but not for the other two.
I guess the problem is that VS looks in the wrong Team project, ie one that does not contain the solution file I want to migrate to. But I can't find a way to explicitly specify which Team project I want to migrate from. It does not help to remove the other Team projects from my Team Explorer.
How is this supposed to work
No migration occurred: No files from solution are under source control
Pparl0627
Gunilla,
I just wanted to make sure that I understood your scenario. You have 3 team projects on the same team server.
Team Project A -> Solution 1
Team Project B -> Solution 2
Team Project C -> Solution 3
The issue was that Migrating settings to soln 2 resulted in an error. If this is the case, this has been fixed in post beta 3 builds and we did a test pass to verify that.
Thanks for the report.
Ravs
Code Analysis Team, VSTS
dsilberhorn
Hi,
If my memory serves me well, we fixed this post beta 3. We'll do a test pass to make sure this scenario is working.
Thanks for the report.
Jeffrey van Gogh
Code Analysis Development Team
Chikodef
Yes, this is exactly my problem.
Does "post beta 3" mean that the fix will be available with the release of TFS
pberkhof
If it worked that way, it would be perfectly OK with me.
My problem is that I can do A->1 but not B->4.
And what I think is happening is that VS/TFS tries to do A->4 when I intend B->4. At least that would account for the error message saying "not under source control".
dpatel
I think this might be a limitation of the product. A team project can have multiple solutions inside of it, you can migrate from one parent level team project to any of the child level solutions inside of it, but you can't cross over into the solutions of another team project.
For example, let's say you have the following on Team Foundation Server:
Team Project A -> Solution 1, Solution 2, Solution 3
Team Project B -> Solution 4, Solution 5, Solution 6
In this scenario, you could migrate policy settings from A->1,2,3 or from B->4,5,6 but not from A->4,5,6 or B->1,2,3.
Eric Jarvi
http://blogs.msdn.com/ejarvi
gareth andrew lewis
Yes, that's right. The fix will be available with the release version.
Thanks,
Ravs