[Note: This post focuses on Microsoft Visual Studio. Suggesting other tools may not be overly useful or valid! Alternative methods to solve the problem below would be priceless -- but if nothing else, a useful link is being shared.]
Perhaps I’m making things overly difficult, but it seems like a major pain to copy Visual Studio 2005 projects when the project is in Visual Source Safe.
Granted, I’m not a Visual Studio wizard, nor do I have a lot of experience with it. These days, I mainly use it to manage my database sync scripts (via the wonders of SSIS aka SQL Server Integration Services). I have several sets of scripts for several sets of environments. Of course, none are the same… but they’re all close. Each is stored in VSS for version control purposes.
Copying an existing project to a new one is a major pain! I did manage to find a guide, “VS.NET and VSS: Copy Solution to new solution” that was written several years ago. It works, but geeze… what an ordeal.
That guide was written when the previous version of Visual Studio was king. Is there an easier way to do this with VS 2005?
Possibly Related posts:
September 28th, 2007 
Tags: 
I’ve experienced similar things before…glad to see I’m not alone.
I am a newbie in Visual Studio projects and your article has helped me gain some insights. Thank you.
[...] still find it an incredible pain in the butt to copy Visual Studio projects that are in Visual Source Safe. There has got to be a better [...]
http://www.kinook.com/CopyWiz/