VSS 2005 and VS .NET 2003? (for HTTP support)

VSS 2005 and VS .NET 2003? (for HTTP support)

• jarrods

  Hi Afredo,
  
  That is good news. You probably want to make sure everyone is aware of this because I can tell you it's not clear at all reading the doc
  
  Is HTTP supported by the VSS 2005 client on a VS NET 2003 installation The event link you give seems to be broken.
  
  Thanks for your answer anyway.
  Simon.
  
  

• RH63

  Alfredo Mendez MSFT wrote:

  Yes HTTP will be supported on a VS .NET 2003 installation

  Sorry, could you expand on that  
  
  Are you saying that from within Visual Studio .NET 2003 I can use the Remote Internet Access plug-in client to communicate with a Visual SourceSafe 2005 database over HTTP
  

• MikeCade

  
  Thanks for letting me know the webcast link is not working. Apparently the archived webcast is not online anymore... I will need to find somewhere else to host it.
  
  To answer your question: Yes HTTP will be supported on a VS .NET 2003 installation
  
  

• N.S. Farr

  Simon Mourier wrote:

  I think it's a pitty that there is absolutely no "bridges" between the 2005 line of products and the previous ones. If one wants to use VSS 2005, one has to use VS 2005, and therefore use the .NET Framework 2.0.

  I sympathise with that point of view but I think Microsoft would argue there are bridges - you can use VSS 2005 with VS 2003, you just don't get the new functionality introduced with VSS 2005 if you don't use the new client. 
  
  Remember, you also don't get those cool new features if you use the VSS 2005 explorer, you only get them when you combine VS .NET 2005 and VSS 2005. 
  
  

  Implications are huge, even if considerable efforts have been made to make the .NET Framework 2.0 compatible at all levels (source, side by side, ...) with 1.1. IMHO, many customers would like to buy those cool new tools but stick with the 1.1 Framework for a while.

  Certainly if you are not planning to convert your main development over to VS .NET 2005 then there probably isn't so much incentive to buy VSS 2005.
  
  I may be being unduly optomistic but I'm not too worried about having VS2003 and VS 2005 installed side-by-side.  So far VS .NET 2002 and VS.NET 2003 have co-existed just fine on our systems (except for disk space getting tight on some of our older developer boxes).
  
  Also, the Mainstream Support lifecycles for VS .NET 2003 and Visual SourceSafe 6.0 are approaching retirement so if you want to be using fully supported software you may have to upgrade in the next few years for that reason even if generics and new namespaces and the rest of VS.NET 2005 features aren't enough to persuade you to buy it.
  

• Brian Oldenburg

  Yes, that is correct.

  You can use SourceSafe’s Remote Access (http) Plug-In with VS 2003.
  Since there is not automated provider switching in VS2003, you will need to use a source control provider switcher like the one at http://www.codeproject.com/tools/sccswitcher.asp
  or manually change the MSSCCI provider in the registry under
  [HLM\Software\SourceCodeControlProvider]
  ProviderRegKey="Software\Microsoft\SourceSafe\RemoteAccess"

  
  
  

• n00b_5876

  Cool.  Somehow I had got hold of the idea that the new plug-ins only worked with VS 2005.
  
  I assume I just install the VSS 2005 client on the VS 2003 system and the plug-in for VS 2003 is installed too
  
  Is the regular SourceSafe plug-in also updated so it can take advantage of the LAN Helper service
  
  Will these new plug-ins work for Visual Studio .NEt 2002 also
  

• Milind Vengurlekar

  Just to be extra clear:

  • SourceSafe 2005 can be used with VS 2003
  • You do not need to switch your developement to .NET Framework 2.0 to use SourceSafe 2005

  There is a number of improvements done at the engine level that you will benefit from: Unicode content, multiple timezone development, performance, reliability, 3rd party diff/merge, etc.
  
  Take a look at the webcast below, it is a bit old, but it is a good high-level summary of the features in SourceSafe 2005:
  http://msevents.microsoft.com/CUI/EventDetail.aspx EventID=1032254284
  
  Regards,

  
  
  

• anagram

  Thanks for your answers Frank
  
  I think it's a pitty that there is absolutely no "bridges" between the 2005 line of products and the previous ones. If one wants to use VSS 2005, one has to use VS 2005, and therefore use the .NET Framework 2.0.
  
  Implications are huge, even if considerable efforts have been made to make the .NET Framework 2.0 compatible at all levels (source, side by side, ...) with 1.1.
  IMHO, many customers would like to buy those cool new tools but stick with the 1.1 Framework for a while.
  
  
  

• LouLny

  Simon Mourier wrote:

  Can we use VSS 2005 (I am especially interested by HTTP support) with VS.NET 2003

  You can access VSS 2005 from Visual Studio 2003 but you only get the 'old' VSS client in VS2003 so you don't get any of the new functionality (like HTTP).
  
  

  BTW: if it's not I think it's really stupid

  Just another decision based on limited resources.  However much effort it would take to retro-fit the new VSS client to VS 2003 is that really the best use of those resources or would we rather they worked on some other VS2005 feature (like say edit-and-continue)
  
• VSS 2005 and VS .NET 2003? (for HTTP support)