VSS 2005?
-
The company I work for is going to upgrade our 2 Visual Studio.NET 2003 licensed copies to Visual Studio.NET 2005 Professional Edition. I just finished doing a basic comparison (and there is no way they will spring for the Team Editions and we don't have an MSDN Subscription) and NEITHER VS.NET 2005 Standard and Professional include Visual Source Safe 2005. In both cases the prices on microsoft.com listed VSS 2005 as "Sold Separately". So, my question in 2 parts: 1) Will VS.NET 2005 continue to work properly with VSS 6.0d in the likely case that we do not upgrade Visual Source Safe? 2) In the case that the upgrade is not required for Source Safe (from 6.0d to 2005) are there really good reasons to upgrade? I've always hated VSS but we've always used it because it was always included with every Visual Studio version I've ever worked with (back at least through version 4.x). Are there significant enhancements in 2005? Thanks!
-
The company I work for is going to upgrade our 2 Visual Studio.NET 2003 licensed copies to Visual Studio.NET 2005 Professional Edition. I just finished doing a basic comparison (and there is no way they will spring for the Team Editions and we don't have an MSDN Subscription) and NEITHER VS.NET 2005 Standard and Professional include Visual Source Safe 2005. In both cases the prices on microsoft.com listed VSS 2005 as "Sold Separately". So, my question in 2 parts: 1) Will VS.NET 2005 continue to work properly with VSS 6.0d in the likely case that we do not upgrade Visual Source Safe? 2) In the case that the upgrade is not required for Source Safe (from 6.0d to 2005) are there really good reasons to upgrade? I've always hated VSS but we've always used it because it was always included with every Visual Studio version I've ever worked with (back at least through version 4.x). Are there significant enhancements in 2005? Thanks!
Matt Philmon wrote:
- Will VS.NET 2005 continue to work properly with VSS 6.0d
By "work with," do you mean can both reside on the same development machine?
Matt Philmon wrote:
- In the case that the upgrade is not required for Source Safe (from 6.0d to 2005) are there really good reasons to upgrade?
Is there something that v6 does or doesn't do that the newest version addresses?
"The words of God are not like the oak leaf which dies and falls to the earth, but like the pine tree which stays green forever." - Native American Proverb
-
Matt Philmon wrote:
- Will VS.NET 2005 continue to work properly with VSS 6.0d
By "work with," do you mean can both reside on the same development machine?
Matt Philmon wrote:
- In the case that the upgrade is not required for Source Safe (from 6.0d to 2005) are there really good reasons to upgrade?
Is there something that v6 does or doesn't do that the newest version addresses?
"The words of God are not like the oak leaf which dies and falls to the earth, but like the pine tree which stays green forever." - Native American Proverb
DavidCrow wrote:
Is there something that v6 does or doesn't do that the newest version addresses?
I haven't used either version, but my company brought in a 'microsoft evangelist' to give a talk on what would be included in VS05. His answer to the diff between VSS6 and VSS05 was that Bill Gates issued a directive requiring the use of MS products internally and that as a result of being forced to eat thier own dogfood VSS was completely rewritten to 'not suck'.
-
Matt Philmon wrote:
- Will VS.NET 2005 continue to work properly with VSS 6.0d
By "work with," do you mean can both reside on the same development machine?
Matt Philmon wrote:
- In the case that the upgrade is not required for Source Safe (from 6.0d to 2005) are there really good reasons to upgrade?
Is there something that v6 does or doesn't do that the newest version addresses?
"The words of God are not like the oak leaf which dies and falls to the earth, but like the pine tree which stays green forever." - Native American Proverb
I mean, does VS.NET 2005 work with SourceSafe 6.0d if my company doesn't go for upgrading Sourcesafe?
-
I mean, does VS.NET 2005 work with SourceSafe 6.0d if my company doesn't go for upgrading Sourcesafe?
Matt Philmon wrote:
...does VS.NET 2005 work with SourceSafe 6.0d...
If you are referring to actually integrating the two together, I would presume not. But you can always use VSS as a standalone product. I use v6 of both, and I use VSS from outside of Visual Studio. Per an MSDN article by Chris Menegay, "Visual SourceSafe is still available and has been updated to work with Visual Studio 2005."
"The words of God are not like the oak leaf which dies and falls to the earth, but like the pine tree which stays green forever." - Native American Proverb
-
DavidCrow wrote:
Is there something that v6 does or doesn't do that the newest version addresses?
I haven't used either version, but my company brought in a 'microsoft evangelist' to give a talk on what would be included in VS05. His answer to the diff between VSS6 and VSS05 was that Bill Gates issued a directive requiring the use of MS products internally and that as a result of being forced to eat thier own dogfood VSS was completely rewritten to 'not suck'.
Does that mean the MS WASN'T using their own stuff to develop before?! :wtf: What were they using? CVS?:~ ------------------------------------- Do not do what has already been done. Absolute power corrupts absolutely.. but it ROCKS absolutely, too.
-
DavidCrow wrote:
Is there something that v6 does or doesn't do that the newest version addresses?
I haven't used either version, but my company brought in a 'microsoft evangelist' to give a talk on what would be included in VS05. His answer to the diff between VSS6 and VSS05 was that Bill Gates issued a directive requiring the use of MS products internally and that as a result of being forced to eat thier own dogfood VSS was completely rewritten to 'not suck'.
"not suck" is a relative term, and i ain't payin extra for it to find out. I'm using 6d at home. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
I mean, does VS.NET 2005 work with SourceSafe 6.0d if my company doesn't go for upgrading Sourcesafe?
The VSS 2005 client and VS.Net integration will work connecting to a 6.0d database. I've seen it work for a couple of minutes while looking at options for our migration to 2005, but I haven't put it to any real use other then just doing a get latest. VS2005 did not recognize the VSS6.0d client as a source provider or whatever term they use for a plugin to the IDE. 2005 does appear to add some type of web service protocol in addition to the file system one, but other then that and the new look I haven't seen any standout features.
-
DavidCrow wrote:
Is there something that v6 does or doesn't do that the newest version addresses?
I haven't used either version, but my company brought in a 'microsoft evangelist' to give a talk on what would be included in VS05. His answer to the diff between VSS6 and VSS05 was that Bill Gates issued a directive requiring the use of MS products internally and that as a result of being forced to eat thier own dogfood VSS was completely rewritten to 'not suck'.
Not ... entirely true. The difference between VSS6 and VSS6d (the 2005 version) is pretty minimal. I think the only potentially useful feature is the Web service interface. As for the "mandated" version, the evangelist was probably thinking of the upcoming Team System Version Control (Team Foundation Server - TFS), which was written from scratch (with a database back end). Sadly, still in Beta (although the release candidate should be 'early Februrary'). Pre: TFS, Microsoft used a modified version of Perforce internally for a while now (since NT 3.1, I think, maybe a bit longer) -------------- TTFN - Kent
-
The company I work for is going to upgrade our 2 Visual Studio.NET 2003 licensed copies to Visual Studio.NET 2005 Professional Edition. I just finished doing a basic comparison (and there is no way they will spring for the Team Editions and we don't have an MSDN Subscription) and NEITHER VS.NET 2005 Standard and Professional include Visual Source Safe 2005. In both cases the prices on microsoft.com listed VSS 2005 as "Sold Separately". So, my question in 2 parts: 1) Will VS.NET 2005 continue to work properly with VSS 6.0d in the likely case that we do not upgrade Visual Source Safe? 2) In the case that the upgrade is not required for Source Safe (from 6.0d to 2005) are there really good reasons to upgrade? I've always hated VSS but we've always used it because it was always included with every Visual Studio version I've ever worked with (back at least through version 4.x). Are there significant enhancements in 2005? Thanks!
If developers are in different networks without being connected by a VPN, VSS 2005 is a must.
-
The VSS 2005 client and VS.Net integration will work connecting to a 6.0d database. I've seen it work for a couple of minutes while looking at options for our migration to 2005, but I haven't put it to any real use other then just doing a get latest. VS2005 did not recognize the VSS6.0d client as a source provider or whatever term they use for a plugin to the IDE. 2005 does appear to add some type of web service protocol in addition to the file system one, but other then that and the new look I haven't seen any standout features.
Thanks guys. That helps. I'm sorta frustrated they separated the packages like that. VSS has always accompanied the VS with the Professional package.
-
Does that mean the MS WASN'T using their own stuff to develop before?! :wtf: What were they using? CVS?:~ ------------------------------------- Do not do what has already been done. Absolute power corrupts absolutely.. but it ROCKS absolutely, too.
Many teams develop their own internal tools that are specifically designed for their team's needs. Tom Archer (blog) Program Manager MSDN Online (Windows Vista and Visual C++) MICROSOFT
-
Matt Philmon wrote:
...does VS.NET 2005 work with SourceSafe 6.0d...
If you are referring to actually integrating the two together, I would presume not. But you can always use VSS as a standalone product. I use v6 of both, and I use VSS from outside of Visual Studio. Per an MSDN article by Chris Menegay, "Visual SourceSafe is still available and has been updated to work with Visual Studio 2005."
"The words of God are not like the oak leaf which dies and falls to the earth, but like the pine tree which stays green forever." - Native American Proverb
I started using VSS back before MS purchased it and have never liked the integration when that was added. It's the only source control system I use and I use it stand-alone with every product I develop Tom Archer (blog) Program Manager MSDN Online (Windows Vista and Visual C++) MICROSOFT
-
The company I work for is going to upgrade our 2 Visual Studio.NET 2003 licensed copies to Visual Studio.NET 2005 Professional Edition. I just finished doing a basic comparison (and there is no way they will spring for the Team Editions and we don't have an MSDN Subscription) and NEITHER VS.NET 2005 Standard and Professional include Visual Source Safe 2005. In both cases the prices on microsoft.com listed VSS 2005 as "Sold Separately". So, my question in 2 parts: 1) Will VS.NET 2005 continue to work properly with VSS 6.0d in the likely case that we do not upgrade Visual Source Safe? 2) In the case that the upgrade is not required for Source Safe (from 6.0d to 2005) are there really good reasons to upgrade? I've always hated VSS but we've always used it because it was always included with every Visual Studio version I've ever worked with (back at least through version 4.x). Are there significant enhancements in 2005? Thanks!
If by "work" you mean "a good product" then I'd start running away... Migration is a bee with an itch but give Subversion a shot. regards, Paul Watson Ireland Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Does that mean the MS WASN'T using their own stuff to develop before?! :wtf: What were they using? CVS?:~ ------------------------------------- Do not do what has already been done. Absolute power corrupts absolutely.. but it ROCKS absolutely, too.
You must not have used SourceSafe before. It has known problems scaling beyond 10-15 users and 5G of data. Microsoft couldn't have developed Notepad using SourceSafe as their version control. Given that some of the projects at MS have hundreds if not thousands of developers working on them, they must be using something else.
Software Zen:
delete this; -
Does that mean the MS WASN'T using their own stuff to develop before?! :wtf: What were they using? CVS?:~ ------------------------------------- Do not do what has already been done. Absolute power corrupts absolutely.. but it ROCKS absolutely, too.
Nicholas Wigant wrote:
What were they using? CVS
Thanks, the nightmares have come back now :(( The tigress is here :-D
-
You must not have used SourceSafe before. It has known problems scaling beyond 10-15 users and 5G of data. Microsoft couldn't have developed Notepad using SourceSafe as their version control. Given that some of the projects at MS have hundreds if not thousands of developers working on them, they must be using something else.
Software Zen:
delete this;I remember hearing that the MFC and ATL teams use SourceUnSafe - at least back in the pre-2005 versions; I believe many teams in Developer Division were moved over to what became Team Foundation Server for Visual Studio 2005. The Windows team uses something Microsoft call SourceDepot which is believed to be derived from Perforce. Mark Lucovsky, now at Google, was responsible for setting up SourceDepot and gave a presentation[^] to the USENIX Windows conference in 2000 about the development history of Windows 2000, in which he discussed the source control mechanisms originally used for Windows NT, how they were becoming unworkable for Windows 2000, how they adopted SourceDepot towards the end of the project and how they subsequently started work on Windows XP. Early in the Team Foundation cycle that team implied that the intention was for all teams at MS to move across to TFS and that therefore one of their goals was to be able to scale to the size of Windows. I suspect, though, that they probably missed this for 1.0 (which is of course not even released yet - the version released concurrently with VS 2005 is Beta 3). Stability. What an interesting concept. -- Chris Maunder
-
Thanks guys. That helps. I'm sorta frustrated they separated the packages like that. VSS has always accompanied the VS with the Professional package.
Not quite. VSS was included with the Enterprise Edition of VS2002 and VS2003, not Professional. Unfortunately VS2005 does not have an Enterprise Edition, as most of its features are now part of Team System. Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
You must not have used SourceSafe before. It has known problems scaling beyond 10-15 users and 5G of data. Microsoft couldn't have developed Notepad using SourceSafe as their version control. Given that some of the projects at MS have hundreds if not thousands of developers working on them, they must be using something else.
Software Zen:
delete this;Yes I have TRIED to set up VSS. Didn't work for even 3 developers on our system. Of course that was probably more user error than the application:~ ------------------------------------- Do not do what has already been done. Absolute power corrupts absolutely.. but it ROCKS absolutely, too.
