Vault & Visual Studio C# 2005 Express Edition Beta

Shane · Post by **Shane** » Wed Jun 30, 2004 4:01 pm

Visual Basic 6.0
Vault 2.0.3

Having installed the 2005 Express Edition Beta I was unable to load my Visual Basic 6 projects that were saved using Vault. Has anyone else downloaded the beta and experienced this?

dan · Post by **dan** » Thu Jul 01, 2004 7:50 am

The Vault IDE component does not yet work with Whidbey. We are hoping our upcoming 2.0.4 release will be compatible.

ericsink · Post by **ericsink** » Thu Jul 01, 2004 9:00 am

Do the Express editions even support source control integration at all? I heard a rumor that they do not, but I haven't tried them yet.

cdaniel · Post by **cdaniel** » Thu Jul 01, 2004 10:29 am

My understanding is that the Express Editions do not support SCC integration at all, but I too have not downloaded any of them to find out.

technophile · Post by **technophile** » Sat Jul 03, 2004 5:58 pm

Yes, they do, as far as I can tell -- at least, I've downloaded and installed VC# 2005 Express and it does have an options dialog to select your source-control plugin.

Post by **jclausius** » Thu Jul 08, 2004 8:21 pm

I ran across this blog tonight - http://weblogs.asp.net/mspedding/archiv ... 76494.aspx

The problem turned out to be very simple, which you install the vs express betas they change the framework version for all you existing ASP.NET applications. Of course Vault has a web services interface and now that Framework version for that ASP.NET application is incorrectly set to v2 rather than v1.1.

The solution is simple open up the Internet Services Manager and change the ASP.Net version for "VaultService" and "VaultShadowFolder". This can be done by right clicking on the web application in the tree view, selecting properties and the ASP.NET tab.

I wonder if aspnet_regiis.exe /i within the v1.1.4322 would solve the problem.

On another note - has anyone played with modifying VaultGUIClient.exe.config on a system that also has Whidbey installed? Supposedly adding the 1.1 .Net binding information solves the problem of .Net 1.1 and .Net 2.0, but I haven't had time to try it out. Anyone else tried this idea?

Wes · Post by **Wes** » Fri Oct 15, 2004 4:20 pm

Has anyone actually got this work in Visual C# Express Beta? For what ever reason I don't even see it in the list of possible source control plugins in the options.

If this is actually working for anyone can you please share how you got it to work?

Thanks,
Wes

Post by **jclausius** » Fri Oct 15, 2004 8:28 pm

Wes:

The Express product lines do not support "integrated" source code control. See the "Source Code Control" feature in http://lab.msdn.microsoft.com/vs2005/pr ... fault.aspx for more information.

However, that does not mean you cannot use Vault. The stand-alone GUI and Command Line clients work just fine. In fact, there are those who prefer to use the native Vault GUI client outside any IDE.

Wes · Post by **Wes** » Fri Oct 15, 2004 9:05 pm

jclausius, thanks for the reply. I checked out the link and you are right that it is not officially supported. I'm just asking because in C# Express, there is a source control plug-in option, and if it is not supported I wonder what this is for exactly.

I know I can use the Vault GUI outside the IDE and that is actually how I am doing it right now, I was just curious if it was possible.

Thanks again,
Wes
http://weblogs.asp.net/whaggard/

Post by **jclausius** » Fri Oct 15, 2004 9:52 pm

Wes:

I could be mistaken, but I believe someone from MS either blogged or posted in a newsgroup the disabled Source Code Control menu items would be totally removed in the next release of the Express products.

Again, I know I read this, but couldn't find an "official link". Perhaps someone else has run across this information via blog, feedster search or usenet posting?