http://dn.codegear.com/article/33011 2008-12-01T20:07:30-08:00 Jeremy North http://threads.codegear.com/threads/threads.exe/userall?commentid=38335 http://threads.codegear.com/threads/threads.exe/view?commentid=38335 2005-04-12T06:42:20-07:00 2005-04-12T06:42:20-07:00

re: Moving a Visual SourceSafe project to StarTeam

Thanks for the feedback Craig.I have made some modifications to the original article based on your comments.cheers,Jeremy Craig Stuntz http://threads.codegear.com/threads/threads.exe/userall?commentid=38321 http://threads.codegear.com/threads/threads.exe/view?commentid=38321 2005-04-05T18:55:01-07:00 2005-04-05T18:55:01-07:00

Moving a Visual SourceSafe project to StarTeam

This is very good for as far as it goes. But when you have completed the steps in this article you *don't* have a native StarTeam archive. Rather, you've wrapped SourceSafe in a StarTeam project. If your SourceSafe DB is unavailable, you won't be able to access it.To complete the process and have a fully native StarTeam vault you must follow the "Go Native" process outlined in the StarTeam administrator's guide. It's pretty simple, but will take some time if your DB is large.Also, there are a few gotchas not covered here. The manual does a pretty good job of covering them. You should create StarTeam users for everyone in your SourceSafe history (you don't need a license for them; the user just needs to exist to keep your history correct). Certain SourceSafe features such as tracking renamed and branched files as a single item will import as separate items in StarTeam. Etc.