How to getVS2003 source controled project to 2005 in 4.0

bluebsh · Post by **bluebsh** » Sun Jun 17, 2007 6:49 pm

I have a project that was source controlled in VS2005 using the 3.5 Vault client, we just upgraded to Vault 4.0 and now our projects only want to load under the Vault VS2003 source control plug-in... how do I make my project work with the new 2005 source control plug-in? thanks!

lbauer · Post by **lbauer** » Mon Jun 18, 2007 6:38 am

Here's a KB article that should help:

http://support.sourcegear.com/viewtopic.php?t=7937

bluebsh · Post by **bluebsh** » Mon Jun 18, 2007 7:49 am

Visual studio littearly crashes when I do those steps... when I get to the point of checking the solution back in after rebinding to the VS2005 client the pending checkins window flashes a bit then VS2005 throws a crash report window and restarts itself... (this is VS2005 SP1)

Post by **jeremy_sg** » Mon Jun 18, 2007 8:16 am

We're currently testing an automated way to convert solutions. Email me using the button below this post, and I'll mail it to you.

bluebsh · Post by **bluebsh** » Mon Jun 18, 2007 11:53 am

well I got it converted after some issues, but now I ran into a "system.notimplemented" issue with the VS2005 source control provider... when I check in an individual project, it works ok, but when I check in a solution it throws this error back

EventType: clr20r3 P1:devenv.exe P2: 8.0.50727.762 P3: 45716759
P4: mscorlib P5: 2.0.0.0 P6: 4333ab80 P7: 3069 P8: 4
P9: system.notimplementedexception

it only happens when i check in a solution that has 36 projects under it and solution folders... all the projects are C# dll's VB.NET exe's and VB.NET dll's along with one setup installer project...

is there any place I can get logs or dumps for you guys to look at to see whats going on here? it only does this in our largest project, smaller ones dont crash

Post by **jeremy_sg** » Mon Jun 18, 2007 12:00 pm

Can you turn on Vault client logging for the IDE and mail the log to me using the button below this post? I want to make sure that we track this down.

bluebsh · Post by **bluebsh** » Mon Jun 18, 2007 12:09 pm

will do, thanks

bluebsh · Post by **bluebsh** » Mon Jun 18, 2007 12:21 pm

not sure if its showing up in the logs or not, but ill post it here in a minute, but it crashes when the vault window pops up saying "Please Wait" as the title and "Checking In changes to {project} ..." {project} being the name of our solution

Edit: Message with log sent

bluebsh · Post by **bluebsh** » Tue Jun 19, 2007 11:33 am

anything useful in the logs i E-Mailed you through this board?

ian_sg · Post by **ian_sg** » Tue Jun 19, 2007 12:30 pm

The log gives me a good idea what's happening. Can you tell me what types of projects are in this solution? I'd like to reproduce this issue, and I believe it's unique to a particular kind of project you're using.

bluebsh · Post by **bluebsh** » Tue Jun 19, 2007 2:55 pm

here is the structure of the solution

Solution (Benefits)
- Solution Folder (Application)
-- VB.NET EXE Project (2x)
-- VB.NET Service Project (2x)
- Solution Folder (Data Access Layers)
-- VB.NET class Library Projects (2x)
- Solution Folder (Libraries)
-- Solution Folder (Divil Wizard)
--- TXT, CMH, DLL, and XML files (1x each)
-- Solution Older (Old)
--- DLL File (1x)
- Solution Folder (Plug-ins)
-- VB.NET Library (dll) (24x)
-- C# Library project (1x)
- Solution Folder (Reporting)
-- MS Reporting Services Report Library project
-- VB.NET Library (3x)
- Solution Folder (Setup)
-- .NET Setup project
-- VB.NET Library
VB.NET Library (3 of them)

bluebsh · Post by **bluebsh** » Tue Jun 19, 2007 2:56 pm

one more thing in the vault pending changes window if i do a commit all it works fine! just when i right click a solution and get commit in this specific project

ian_sg · Post by **ian_sg** » Thu Jun 21, 2007 8:00 am

Would you mind sending me your solution file for this? I need just the .sln file. It's got the project type GUIDs in it, which will allow me to verify that I'm working on the right project type(s) for your problem.

ian_sg · Post by **ian_sg** » Thu Jul 05, 2007 10:42 am

We figured this out via email. This issue is resolved in Vault 4.0.2/Fortress 1.0.2, to be released in the next few days.