SourceSafe and dot net 2.0

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

Hi,
How do I get my Source safe to interact with the 2.0 IDE.(Beta 2.0)
The IDE seems hell bent on having a team server.
I just want to be where I was with 2003, i.e. Able to checkin and out from
the IDE.
Thanks
Bob
 
Bob,

You need to change the the Source Control plug-in in the Options dialog box.
It displays the installed source control software that supports the VSIP
protocol. I haven't tested it, but I'm somewhat sure you need VSS 2005 for
this.
 
CT said:
You need to change the the Source Control plug-in in the Options dialog
box. It displays the installed source control software that supports the
VSIP protocol.
Click to expand...

I think that the "protocol" is called SCC (Source Code Control). VSIP is the
Visual Studio Integration Program (now called VS 2005 SDK) needed to build
SCC tools.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com
 
Previous IDEs could only use the default Source Code Control (SCC) provider
of your machine (HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
registry entry), but VS 2005 allows you to select any of them
(HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders
registry entry) using the menu Tools, Options, node Source Code Control,
Plug-in selection.

You don´t need VS Team System, any SCC-compliant provider will work.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com
 
The betas are more finely tuned for the next version of SourceSafe. I would
move up to at least RC if you continue having problems after trying the
suggestions elsewhere in this thread (RTM is better, of course, as it is an
official release).

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************
 
Hi Carsten,

I was also wrong. The "protocol" is MSSCCI (Microsoft Source Code Control
Interface), not SCC (Source Code Control) as I said.

MSSCCI used to be quite secret or NDA, but now it seems that it is part of
VSIP.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com
 
Hi Carlos,

Yes, I was about to write MSSCCI as I wrote about VSS in my latest book, but
I then decided to do a little research and that's why I came across VSIP.
Anyway, you're right, I should have mentioned MSSCCI as well, so thanks for
pointing that out. :-)
 
Back
Top