I am using visual studio 2008 and the latest version of vault 4.1.1 and the enhanced client. I am attempting to open a solution from scratch and it is not working. I have tried two different approaches. Is there any work around to these issues? I can send my entire source repository to someone to debug. It is only 10 MB.
APPROACH 1 – “Open from Vault”
Error of “Microsoft Visual C# Intellisense has stopped working”. I did the registry update thing mentioned in another bug report.
I tried this before and consistently got a different error – one about the Solution Items folder missing its binding. I got the same error regarding another solution level folder and was not able to work around it by selecting the repository folder. My solution has a Solution Folder called Tools with a bunch of projects in it. Visual studio stores these projects at their root level rather than inside a folder called “Tools”.
APPROACH 2 – “Get latest version”
I went into the vault client and did a “get latest version” for the entire solution into a new empty folder. I then started up visual studio and tried to open the solution from the folder directly. Visual studio seemed to open it up correctly but none of the projects appear to be under source control. I try “Go Online” and get a dialogue that says the project X is bound to vault but has no valid working folder in its current on disk location. I choose to locate the project in the repository. Now every project in Visual Studio appears as a renegade.
can not open a solution from vault
Moderator: SourceGear
We're still working with Microsoft to resolve the Intellisense error you saw in approach 1. We're hopeful that VS 2008 SP1 will resolve it completely, though Vault 4.1.2 will make it less common.
Approach 2 actually worked, you just have changes in your project files that need to be checked in. Check out each project file (make sure the Modfied Local File option is NOT set to Overwrite), then check them in.
Approach 2 actually worked, you just have changes in your project files that need to be checked in. Check out each project file (make sure the Modfied Local File option is NOT set to Overwrite), then check them in.
Ian Olsen
SourceGear
SourceGear
We finally figured this one out. Microsoft acknowledged a bug in Visual Studio that had the same symptoms as this. It ended up being unrelated and unfortunately just threw us off the scent for several weeks.
The symptoms are this: you're performing an Open From Vault or a Get Latest Version (more specifically a Get Latest Version that requires the solution or at least one project to reload, because the file changed). You get a dialog saying Intellisense has stopped working, sometimes followed by Visual Studio crashing.
The fix will be included in Vault 4.1.3 and Fortress 1.1.3. We haven't yet announced a release date, but if this issue affects your team and you'd like a pre-release of the client (which will work with your existing 4.1.x server) you can email me using the button below or directly: ian at sourcegear dot com.
The symptoms are this: you're performing an Open From Vault or a Get Latest Version (more specifically a Get Latest Version that requires the solution or at least one project to reload, because the file changed). You get a dialog saying Intellisense has stopped working, sometimes followed by Visual Studio crashing.
The fix will be included in Vault 4.1.3 and Fortress 1.1.3. We haven't yet announced a release date, but if this issue affects your team and you'd like a pre-release of the client (which will work with your existing 4.1.x server) you can email me using the button below or directly: ian at sourcegear dot com.
Ian Olsen
SourceGear
SourceGear