VS 6 and VS 2005 - which SourceSafe versions are compatible?

[HF]

Hi,

We are currently doing all our development using Visual Studio 6 (yes, we're
a bit behind), with Visual SourceSafe 6.0d for source control. We will be
upgrading to Visual Studio 2005 in the near future, but will need to be able
to us VS 6 as well during a transition period.

* Is Visual SourceSafe 6.0d compatible with, i.e. does it integrate with,
Visual Studio 2005?
* If we were to upgrade to Visual SourceSafe 2005: Would this be compatible
with, i.e. will it integrate with, Visual Studio 6?
* Which version of SourceSafe will be our best choice if we require
integration with both VS6 and VS2005 at the same time?

Regards,
HF

[Cowboy (Gregory A. Beamer)]

You have a couple of options:
1. Stick wtih 6.0d
2. Use the new VSS
3. Switch to TFS source control

Currently TFS is not backward compatible with VS 6, so it is the least
useful option if you want both on the same source control.

I am not sure of the compatibility of 6.0d with Visual Studio 2005 nor the
new VSS with VS 6. I wish I had this information.

If it were me, I would have two repositories, even if it was in different
products. I know this is not optimal, but it reduces confusion at this time.
I would, personally, choose TFS as the new repository, as it will be
backward compatible next year and a much better source control system for
too many reasons. You can transition 6.0d later. The downside is at least
one of your purchases needs to be Team System Suite, which is an additional
cost. If you have MSDN Universal subscriptions, you have until June 30, 2006
to bite this bullet at the reduced upgrade to Team Suite cost of $1200.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************

Post by HF
Hi,
We are currently doing all our development using Visual Studio 6 (yes, we're
a bit behind), with Visual SourceSafe 6.0d for source control. We will be
upgrading to Visual Studio 2005 in the near future, but will need to be able
to us VS 6 as well during a transition period.
* Is Visual SourceSafe 6.0d compatible with, i.e. does it integrate with,
Visual Studio 2005?
* If we were to upgrade to Visual SourceSafe 2005: Would this be compatible
with, i.e. will it integrate with, Visual Studio 6?
* Which version of SourceSafe will be our best choice if we require
integration with both VS6 and VS2005 at the same time?
Regards,
HF

[HF]

Post by Cowboy (Gregory A. Beamer)
If it were me, I would have two repositories, even if it was in different
products. I know this is not optimal, but it reduces confusion at this time.

I've heard that you can't have both VSS 6 and VSS 2005 installed on the same
computer. Is this wrong, or maybe it might work for clients but not for
servers?

- HF

[Cowboy (Gregory A. Beamer)]

That is probably right. Have not checked with VSS 6 and VSS 2005, so I was
focused more on the TFS source control, although, looking back at it, I did
not make that very clear.

With VS 2005, you have the option of othe types of source control, as well,
on a project basis. CVS becomes a better option, for example.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************

Post by HF

Post by Cowboy (Gregory A. Beamer)
If it were me, I would have two repositories, even if it was in different
products. I know this is not optimal, but it reduces confusion at this

time.
I've heard that you can't have both VSS 6 and VSS 2005 installed on the same
computer. Is this wrong, or maybe it might work for clients but not for
servers?
- HF

[Oenone]

Post by HF
I've heard that you can't have both VSS 6 and VSS 2005 installed on
the same computer. Is this wrong, or maybe it might work for clients
but not for servers?

I think I may be able to answer most of your questions here:

1. VSS6.0d integrated perfectly with VS2003, and so I'd be extremely
surprised if it doesn't integrate with VS2005 (though I haven't actually
tried this).

2. VSS2005 will integrate fine with Visual Studio 6. If (after uninstalling
VSS6.0d) you find that all the SourceSafe integration options have
disappeared from your VB IDE, you can re-enable them by adding this line to
the end of your C:\Windows\vbaddin.ini file:

vbscc=1

3. You certainly CAN have VSS6.0d and VSS2005 installed on the same machine
(i.e., nothing stops you from doing it), but the documentation for VSS2005
strongly recommends that you uninstall any old versions of VSS first. I
didn't read this (typical impatient developer) and had a LOT of unexplained
crashes and lock-ups in VS2005. Since completely uninstalling VSS6.0d and
VSS2005 and then reinstalling VSS2005, I've not had any crashes at all.

4. VSS2005 is fully backward-compatible with VSS6.0d, and uses exactly the
same database structure.

Hope that helps,

[Robert Beaubien]

Gregory,

How do I take advantage of that $1200 upgrade? I have contacted MSDN
support for that upgrade option and I seem to be getting the run-around
saying it will instead cost me $3500 to upgrade (which also terminates the
rest of my universal subscription).
--
- Robert Beaubien
- President
- Kool Software
-

Post by Cowboy (Gregory A. Beamer)
1. Stick wtih 6.0d
2. Use the new VSS
3. Switch to TFS source control
Currently TFS is not backward compatible with VS 6, so it is the least
useful option if you want both on the same source control.
I am not sure of the compatibility of 6.0d with Visual Studio 2005 nor the
new VSS with VS 6. I wish I had this information.
If it were me, I would have two repositories, even if it was in different
products. I know this is not optimal, but it reduces confusion at this
time. I would, personally, choose TFS as the new repository, as it will be
backward compatible next year and a much better source control system for
too many reasons. You can transition 6.0d later. The downside is at least
one of your purchases needs to be Team System Suite, which is an
additional cost. If you have MSDN Universal subscriptions, you have until
June 30, 2006 to bite this bullet at the reduced upgrade to Team Suite
cost of $1200.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***********************************************
Think Outside the Box!
***********************************************

Post by HF
Hi,
We are currently doing all our development using Visual Studio 6 (yes, we're
a bit behind), with Visual SourceSafe 6.0d for source control. We will be
upgrading to Visual Studio 2005 in the near future, but will need to be able
to us VS 6 as well during a transition period.
* Is Visual SourceSafe 6.0d compatible with, i.e. does it integrate with,
Visual Studio 2005?
* If we were to upgrade to Visual SourceSafe 2005: Would this be compatible
with, i.e. will it integrate with, Visual Studio 6?
* Which version of SourceSafe will be our best choice if we require
integration with both VS6 and VS2005 at the same time?
Regards,
HF

[Alin Constantin [MSFT]]

Post by HF
* Is Visual SourceSafe 6.0d compatible with, i.e. does it integrate with,
Visual Studio 2005?

Yes, it does.

Post by HF
* If we were to upgrade to Visual SourceSafe 2005: Would this be compatible
with, i.e. will it integrate with, Visual Studio 6?

VSS testers haven't focused on this combination. VSS2005 was only tested
with VS2003 and VS2005.
However, I've used VSS2005 on a few small projects with VS6 and I haven't
seen any problems.

Post by HF
* Which version of SourceSafe will be our best choice if we require
integration with both VS6 and VS2005 at the same time?

Personally I'd go with VSS2005. I'd recommend it if you'll have to deal with
Unicode or Utf-8 files, with web projects or will want to use delete/rename
propagation feature in VS2005.

Post by HF
I've heard that you can't have both VSS 6 and VSS 2005 installed on the
same

computer. Is this wrong, or maybe it might work for clients but not for
servers?

Well, you can have both VSS6 and VSS2005 installed on a computer and use the
SSExplorer/SSAdmin side-by-side, but the plugin that VisualStudio use is not
side-by-side. The last registered ssscc.dll wins, and will be used by both
IDEs. So, last VSS version installed will be used. If you really like to
have them both installed and play with them, you'll have to manually switch
the registered plugin (using "regsvr32.exe ssscc.dll" command in the VSS
binaries folder) depending on your needs.

Alin