R
rrodri
Guest
I have Visual Studio 2003 installed in my PC since I have legacy projects to maintain.
A few days ago I installed Visual Studio 2017 and TFS in the same machine.
Now when I open a legacy project from Visual Studio 2003, it cannot detect visual SourceSafe provider, instead it detects TFS and tries to bind the project to it, so I cannot open it.
I have found some information in google related to registry keys that I need to change since from Visual Studio 2003 it is not possible to switch between MSSCCI providers. But none of the attempts I have tried works.
Please, help me and tell me what registry keys and changes I have to done in order to my legacy projects can be opened again in Visual Studio 2003 and bound to SourceSafe.
I have answered it here but no working solutions are provided.
Thanks in advance.
Continue reading...
A few days ago I installed Visual Studio 2017 and TFS in the same machine.
Now when I open a legacy project from Visual Studio 2003, it cannot detect visual SourceSafe provider, instead it detects TFS and tries to bind the project to it, so I cannot open it.
I have found some information in google related to registry keys that I need to change since from Visual Studio 2003 it is not possible to switch between MSSCCI providers. But none of the attempts I have tried works.
Please, help me and tell me what registry keys and changes I have to done in order to my legacy projects can be opened again in Visual Studio 2003 and bound to SourceSafe.
I have answered it here but no working solutions are provided.
Thanks in advance.
Continue reading...