When you use VS 2005, it automatically loads the .NET Framework 2.0 CLR, and the Vault IDE client uses that. Likewise, Visual Studio 2003 loads the .Net Framework 1.1 CLR for use by the Vault IDE.
However, VB 6 predates .NET, so the Vault IDE Client has to load a framework and due to its compilation defaults to loading the .NET Framework 1.1. This should work on most machines with both the 1.1 and 2.0 Frameworks. Since you don't have the 1.1 Framework on your machine, the VB6.exe.config forces the Vault IDE client within VB 6 to load the .NET Framework 2.0.
This isn't a bug, but a configuration issue, and you have found the proper way to configure your machine to use VB 6 without having the .Net Framework 1.1 installed.
Another route would be to install the .Net Framework 1.1 on your VB 6 / Vault client machines - http://msdn2.microsoft.com/en-us/netfra ... 69264.aspx
We'll add a KB article with details about these solutions in the event other users want Vault integration with VB 6 and only have the .NET Framework 2.0 installed.
VB6 - Vault Integration Issues
Moderator: SourceGear
-
- Posts: 9
- Joined: Wed Jan 25, 2006 12:18 pm
Great..thanks for the explanation
Ahaaaa now I fully understand.
Thanks a lot Linda.
Can't you make the vault client check to see if 1.1 is installed and if it is not use 2.xxx?
At any rate, now I completely understand the issue and would appreciate a kb article on this.
thanks a lot.
Thanks a lot Linda.
Can't you make the vault client check to see if 1.1 is installed and if it is not use 2.xxx?
At any rate, now I completely understand the issue and would appreciate a kb article on this.
thanks a lot.
Matt