What is this "VS 2003 Compatible Client"???
Moderator: SourceGear
What is this "VS 2003 Compatible Client"???
In VS.NET 2005 in the File menu...Source Code Control there is a link to a VS 2003 Compatible Client. What is this for? Why am I seeing this in VS 2005? What should I be using instead of this client?
The 2003 compatible client is our old MSSCCI based IDE client. We chose to ship it so that people who are already using that IDE client will continue to be able to use any solutions that are already bound to it. We encourage people who are using 2005 to use the new client.
To change which IDE client you are using, you will need to unbind the solution and projects from the 2003 client, reload the solution. Now select the 2005 client as your default provider, and select Bind from the solution's context menu. Browse to the location of the solution file, and hit OK.
To change which IDE client you are using, you will need to unbind the solution and projects from the 2003 client, reload the solution. Now select the 2005 client as your default provider, and select Bind from the solution's context menu. Browse to the location of the solution file, and hit OK.
Last edited by jeremy_sg on Sun Jun 03, 2007 9:41 am, edited 1 time in total.
Where in the documentation is this outlined? How would I know this? Why isn't there a message when VS.NET 2005 is set to use the 2005 client to "upgrade" a solution for me when loading it? Naturally there are many concerns about unbinding and rebinding, typically once source code control is "under way" you don't want to mess with it in VS.NET, IMHO.To change which IDE client you are using, you will need to unbind the solution and projects from the 2003 client, reload the solution. Now select the 2005 client as your default provider, and select Bind from the solution's context menu. Browse to the location of the solution file, and hit OK.
What does the VS 2005 client do for me? Where is it? Am I still using the Vault GUI? Your documention or any other reference I have searched for tells me nothing, shows me nothing, of what this client does, looks like, etc. other than a pending checkins tool window, which I closed.
The other problem, of course, is there is no VS 2005 client on my Vista x64 machine. Most likely you all have not done any testing or development against Vista x64 to learn about WOW64 registry, folder structure, VSIP, etc. I've gone through this with two other companies (VistaDB, and AxTools - CodeSmart) where people are totally ignoring x64. I admit, until I loaded up Vista x64 I wasn't smart on it, and now that I have gone down this path, and in my opinion with more users installing Vista x64 with all the latest computers now using EM64T processors, you better get familiar with it! It affects installers, VS integration, everything! I would have expected SourceGear to be keyed into this with wanting broader client support but totally missing the boat in the x64 realm. I read the notes in the installer process and it just says "Windows Vista" not a specific x86 or x64 variant.