I am using Visual Studio 2005 SP1 with Vault client 3.5.2
I have an ASP.net 2.0 project in Visual Studio that is nicely set up in Vault. Whenever I try and check anything out of Vault from within the Solution Explorer in Visual Studio (by typing in a code file, or right clicking on an item and selecting "check out") the Visual Studio compiler crashes and throws an error. This is irritating because while it doesn't actually crash the entire visual studio session it does require a second web debug process that has a different port number.
I can use these two products together fine for Windows Forms. Check out works etc. It only happens with ASP.net web projects.
I've seen some posts on ensuring the right version of the Vault plugin for Visual Studio but I can't find any documentation on how to research this.
Visual Studio 2005 Crash when checking out ASP.net files
Moderator: SourceGear
-
- Posts: 2
- Joined: Thu Feb 21, 2008 11:17 am
There's only one plugin available in Vault 3.x and earlier -- the Classic client integration.
Does this crash happen for any user on any machine?
Is there anything in the Vault Server log that corresponds to the crash?
(It's sgvault.log in %windir%\temp\sgvault.
Does this crash happen for any user on any machine?
Is there anything in the Vault Server log that corresponds to the crash?
(It's sgvault.log in %windir%\temp\sgvault.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 2
- Joined: Thu Feb 21, 2008 11:17 am
Nothing in log
There's nothing in the server log that looks fishy. All transactions associated with my user account appear to have the word "success" associated with them.
The check out completes successfully and I can continue working in VS2005. However, I can't build or run my application and have to close VS2005 and reopen it to do these tasks.
Error screen attached.
The check out completes successfully and I can continue working in VS2005. However, I can't build or run my application and have to close VS2005 and reopen it to do these tasks.
Error screen attached.
- Attachments
-
- Erro screenshot
- Error.JPG (33.77 KiB) Viewed 1994 times
One thing to try is a fresh open from source control. Backup the local directories that currently contain the project, open Visual Studio and use the command File->Source Control->Open From Source Control into clean working directories.
Or if this is a web project, rather than a web application, try Open->Website->Source Control.
Or if this is a web project, rather than a web application, try Open->Website->Source Control.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager