.NET Zone is brought to you in partnership with:

I’ve been a Windows developer since 3.0 and caught the Visual Basic wave early with v1. I’ve released a “production” application in every version of VB since then (except VB for DOS). Focusing on enterprise, line-of-business development I’ve built Call Center Applications, Mortgage finance systems, Customer Relationship Management tools and more recently I’ve been in the Litigation Support/Electronic Data Discovery/Electronically Stored Information space. Greg is a DZone MVB and is not an employee of DZone and has posted 481 posts at DZone. You can read more from them at their website. View Full User Profile

New Visual Source Safe Upgrade Tool Released

  • submit to reddit

Visual Studio ALM + Team Foundation Server Blog - New Visual Source Safe Upgrade Tool is Available!

"In the last month I have seen multiple requests for a new Visual Source Safe Upgrade tool – and here it is!

The Visual Source Safe Upgrade tool provides a Wizard Based UI for upgrading Visual Source Safe repositories to Team Foundation Server 2012, 2010 or Team Foundation Service (http://tfs.visualstudio.com/)

Upgrades the follow from Visual SourceSafe to Team Foundation Server (TFS) version control:

  • Code projects
  • Files
  • Version history
  • Labels
  • User information

Documentation can be found at:


Don't laugh (I know you are, admit it...) but I think you'd be surprised how many SourceSafe hives that are still out there and in daily use. Yeah, yeah, I know it's hard to believe, but it's true. But with this tool and the five free users for the Team Foundation Service, the TFS that comes with MSDN subscriptions and this tool, maybe we can finally, finally put VSS to rest? If you're still one of those VSS users, don't despair, just plan you move off. It's time. Really. (and I've done it and it believe me you'll not regret it)

Published at DZone with permission of Greg Duncan, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)