VS 2010 wizard resulted in weird solution file

[gsmalter]

Here's what happened when using VS 2010 and the enhanced Vault client during the automatic wizard conversion from 2008 -> 2010.

Before:
Microsoft Visual Studio Solution File, Format Version 10.00
# Visual Studio 2008
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Standard Library", "Standard Library\Standard Library.csproj", "{7EED5926-9FE0-44DB-9B5F-5A6856CE392E}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Test Web Site", "Test Web Site\Test Web Site.csproj", "{1FEF500E-B420-42D6-8702-D998CDF65C23}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Red Stapler Library Tester", "Red Stapler Library Tester\Red Stapler Library Tester.csproj", "{19980628-FB8A-42EA-9FB3-B9F511DF3D1E}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Solution Files", "Solution Files\Solution Files.csproj", "{D1934BF3-2370-49BD-8FE7-3781E575C448}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Library", "Library\Library.csproj", "{3398B3A5-8445-410E-A69B-33EE3E914A03}"
EndProject
Global
GlobalSection(VaultVsipSolution-v2) = preSolution
VaultHost = http://vault.redstapler.biz/VaultService
VaultRepositoryID = 1
VaultRepositoryGUID = d1552337-a5cb-483f-b8db-ff08fed05e69
ProjectCount = 5
ProjectRelativeDiskPath1 = Standard Library\Standard Library.csproj
ProjectRelativeDiskPath2 = Test Web Site\Test Web Site.csproj
ProjectRelativeDiskPath3 = Red Stapler Library Tester\Red Stapler Library Tester.csproj
ProjectRelativeDiskPath4 = Solution Files\Solution Files.csproj
ProjectRelativeDiskPath5 = Library\Library.csproj
EndGlobalSection
---------------------------------------------------------------------------------------------------------------------------
After:
Microsoft Visual Studio Solution File, Format Version 11.00
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Standard Library", "Standard Library\Standard Library.csproj", "{7EED5926-9FE0-44DB-9B5F-5A6856CE392E}"
EndProject
Project("{00000000-0000-0000-0000-000000000000}") = "Test Web Site", "Test Web Site\Test Web Site.csproj", "{1FEF500E-B420-42D6-8702-D998CDF65C23}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Red Stapler Library Tester", "Red Stapler Library Tester\Red Stapler Library Tester.csproj", "{19980628-FB8A-42EA-9FB3-B9F511DF3D1E}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Solution Files", "Solution Files\Solution Files.csproj", "{D1934BF3-2370-49BD-8FE7-3781E575C448}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Library", "Library\Library.csproj", "{3398B3A5-8445-410E-A69B-33EE3E914A03}"
EndProject
Global
GlobalSection(VaultVsipSolution-v2) = preSolution
VaultHost = https://vault.redstapler.biz/VaultService
VaultRepositoryID = 1
VaultRepositoryGUID = d1552337-a5cb-483f-b8db-ff08fed05e69
ProjectCount = 4
ProjectRelativeDiskPath1 = Standard Library\Standard Library.csproj
ProjectRelativeDiskPath2 = Red Stapler Library Tester\Red Stapler Library Tester.csproj
ProjectRelativeDiskPath3 = Solution Files\Solution Files.csproj
ProjectRelativeDiskPath4 = Library\Library.csproj
EndGlobalSection
---------------------------------------------------------------------------------------------------------------------------

The project count shrunk from 5 to 4. The Test Web Site project got left out somehow. It still appears at the top, but with a zeroed-out GUID. Things still seem to work properly, though (but I haven't really tried much).

Is this config file section ignored or something?

[Beth]

Did you have the solution and project unbound or checked out during the upgrade?

Do you have more to upgrade?

I will try to set up something similar and test it.

Can you take a screenshot of what you see under File - Vault Source Control - Change Vault Bindings? Is everything showing a valid binding?

[gsmalter]

I had everything checked in when I started. The VS Wizard checked stuff out automatically.

All Vault Bindings are listed as valid, and I get the lock icons on the files even for the project that is missing from the solution file.

My guess is that the reason the project got left out is because it failed to migrate on the first try (because I wasn't running as admin, and because it's an IIS web site, I need to be - still). I bet if I undo checkout, run as admin, and re-migrate, it will work.

I guess the most bothersome thing is that despite the mangled solution file, nothing appears to be wrong. So, it's like the solution file data doesn't matter.

[gsmalter]

As I predicted, undoing checkout on the entire solution and re-migrating with VS 2010 open as an admin avoided this issue. It's still troubling, though, that it is possible to get it out of sync, and that vault information in the solution file appears to get ignored (why is it there?) seeing as everything seems to work even when it's wrong.

[Beth]

We just released Vault 5.0.4 that has some fixes for integration with VS 2010.