Sunday, December 16, 2007

SourceSafe 2005 Update (KB943847)

Microsoft Downloads - Visual SourceSafe 2005 Update

"...

This update is a rollup of bug fixes for Visual Source Safe. The fixed bugs include stability, performance, data integrity, and usability enhancements in many areas of the product. It also improves compatibility with Visual Studio 2008 and Windows Vista™. A comprehensive list of fixes is publsihed in the Microsoft Knowledgebase Article. The article can be found by following the appropriate link under Additional Information on this page.

  • This update may be installed before or after installing Visual Studio.
  • It is recommended that this update be installed before using SourceSafe inside Visual Studio 2008 (formerly codenamed “Orcas”). Once installed, SourceSafe 2005 is compatible with all Orcas releases.
  • The update only needs to be installed once.
  • The update can be installed over any existing SourceSafe 2005 hotfixes. In addition, future hotfixes will contain all of the changes from this update (cumulative). Older builds will never overwrite newer builds.
  • It is recommended that you backup your SourceSafe databases before installing this update.

..."

Note To Self: Install this at work (sigh).

While all my .Net 2.0+ code (i.e. where I use VS2005,VS2008) is in TFS, my older VB6 (yes, I still have production VB6 code... Hey, it's making money for the firm... ) and .Net 1.1 code (I've already scheduled these for upgrading to 3.5) is still in SourceSafe, so I should keep it up to date.

But boy am I looking forward to the day I can retire SourceSafe. Source control via TFS is just so much more... more... more.

3 comments:

artlung said...

SourceSafe makes me very very sad. So glad I can choose workplaces that don't use it.

Greg said...

Yeah... don't rub it in or anything...

JK :)

What's really sad is that we have development teams who don't have a desire or drive to even think about moving off of SourceSafe. It's in the med/long term plans to begin to think about moving to TFS.

sigh...

Anonymous said...

I would consider something more solid for source control, like Accurev, or Perforce if you don't care about process, before jumping to another MS product. JMHO