VS2010 Crash when installing Vault CLient 5.0.4

[isalvo]

I'm running Windows 7 (32bit) and Visual Studio 2010. After I installed Vault client 5.0.4 Visual Studio now crashes on startup. The error message displayed reads "Microsoft Visual Studio has stopped working.. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available". Under VS Options \ Source Control the current source control plug-in is set to "none". I've tried to set it to "SourceGear Vault Visual Studio Enhanced" or "SourceGear Vault Classic Client", but it does not keep the setting or solve the problem. Other developers in the organization are having the same problem. We noticed this does not seem to affect users running Windows 7 64bit though.

[Beth]

I have received your email in support as well and responded via email.

HS: 221315

[jtfml]

I am experiencing the same thing with Vault Pro 5.1.1 (single user mode), Visual Studio 2010, and Windows 7 64-bit. It happens at the point that Vault normally asks me to sign in. This started happening approximately 2-3 weeks ago, also approximately when the ATI FirePro graphics driver was updated. I've tried reverting the driver, reinstalling the driver, with no resolution. I tried running with only the Microsoft Windows 7 graphics driver installed and I was able to open the project (at probably 640x480 resolution). Reinstalling the ATI FirePro driver caused it to stop working again. I copied my project to a new location (not matching Vault's working folder path) and the project will open with the ATI driver installed. I renamed the old project folder, renamed the new project folder to match the original, and now the original will open (from the new folder path, but same disk location), and the new that previously opened now causes VS to crash, seemingly because the path now matches the working folder path.

I've seen other issues like files not being checked out when I edit them and subsequently being classified as Renegade. Before that was only extremely annoying. Now I'm unable to use Vault as a source control application. I hope you have a resolution and can provide it quickly. I've spent 5-6 hours on the phone with Microsoft Support and using remote control through their EasyAssist application and they have not been able to resolve it. I spent 1.5 hours on the phone with HP doing everything imaginable with the graphics drivers. I feel like my recent experiments with folder renaming points directly at Vault. I've been a fan for a long time (6 years). Please keep me as a fan...

[Beth]

Prior to 2-3 weeks ago, did you have the issue of files not checking out? Any other issues prior to the driver change?

Are you able to create a new dummy project (make it a simple one) in Visual Studio and add it to Vault? If not, what is the behavior you receive?

[jtfml]

I have had issues with some files not checking out ever since the upgrade to 5.1.1.

I was able to add a new project to Vault. I have been able to work with Vault in VS 2010, with minor issues, for a few months. It's scary that projects that have worked for a while don't work anymore. Not all projects act this way, but more and more projects are starting to crash VS. I've been afraid to try any VS 2005 projects.

[Beth]

Does every user have the same issue or is it limited to one machine?

Do you have any Visual Studio Add-Ins such as the Productivity Power Tools?

Are you using the Vault Classic Client or the Vault Enhanced Client? That setting is found in the VS Tools - Options - Source Control - Plugin.

Are all users using the same client in Visual Studio?

[jtfml]

I'm using Vault as a single user. I'm using the enhanced client. The only "add-in" I have is the Windows Phone 7 developer tools (which doesn't attempt to interact with Vault, but I wish it did).

Yesterday I decided I needed to continue working regardless of the source control situation and so using the Vault client software I checked out the whole project, did my work in the copy of the project I previously made in another folder (I permanently removed the binding), then copied the modified files into the project's original working folder location, and then checked that back in. There were differences in the solution file that I didn't track and make note of. Now the project will open from the original location, but now the project is not "bound". I'm about to try binding it again... That appears to have reestablished the binding and the project will now open in its proper location, although I have not tried working with it yet.

[u]IF[/u] this resolves the current situation, it's still a bad thing because I don't know what caused the original failure and so I don't know if it will happen again and I can't be sure that it will be recoverable in the future. I now have about 4 copies of my projects scattered around my hard drive and other drives, not to mention backups that may or may not be containing bad copies of the files. Not knowing if I am safe is the worst part.

[Beth]

This might be easier to troubleshoot if I can see it directly. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread? Even if it appears to be working now, it might be good to prepare ahead of time to troubleshoot when something happens.

HS: 222854