Hi,

Does Visual Sourcesafe 2005 work with Visual Studio.NET Professional 2003?
We're about to implement a source control system and I'd rather purchase
2005 instead of v6 if it does infact work with VS.NET Pro 2003.

Thanks.

Jerry

Jerry,
I have used VSS 2005 with VS 2003 & VS 2002, I have not noticed any adverse
effects, however its only been a couple of smaller projects so far.

--
Hope this helps
Jay [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net


"Jerry Spivey" <jspivey (AT) vestas-awt (DOT) com> wrote

Jay,

Thanks. That was the impression I got from reading a few Googlized posts.
Pretty freaking difficult to find much on VSS2005. I've ordered the VS.NET
Team Eval from MS which as I read it does include VSS2005 so I'll be able to
eval the product.

Jerry


"Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_MVP (AT) tsbradley (DOT) net> wrote in
message news:%23I%23EGXPAGHA.3048 (AT) TK2MSFTNGP15 (DOT) phx.gbl...

Hi Jerry,

VSS2005 has been tested with VS2005 and VS2003 and it should work.
It may also work with other IDEs like VS2002 or VS6, but it has not been
tested much in those configurations

--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.


"Jerry Spivey" <jspivey (AT) vestas-awt (DOT) com> wrote

In fact, I've just found a minor compatibility issue when using VS2002 and
VSS2005.

The bug is in VS2002 side. If you create a project in VS2002 and try to add
it to source control using VSS2005, you get an error message "Comment it too
long", which doesn't make any sense because the user doesn't specify any
comments during add to source control.
The reason is that VS2002 creates some temporary files like
~sak65c5834901c6014f.tmp to detect whether the source control provider
supports shared checkouts. VS2005 uses a comment like "Temporary file
created by Visual Studio .NET to detect Microsoft Visual SourceSafe
capabilities.", which is 97 characters long, and disregards that maximum
checkout comment length for VSS is 63 characters. VSS2005 does a better job
of verifying these lengths and displays the error message. There isn't any
major functionality impaired by this issue.

VS2003 doesn't have this issue because it checks the provider capabilities
differently, without creating the temporary files.

--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.


"Alin Constantin [MSFT]" <cnila (AT) tfosorcim (DOT) moc> wrote