http://forums.asp.net/1012.aspxDiscuss issues, strategies, tips, etc. for migrating from Visual Studio .NET 2003 to Visual Studio 2005enCommunityServer 2007 SP1 (Build: 20510.895)http://forums.asp.net/thread/1819273.aspxTue, 24 Jul 2007 01:55:50 GMT4c671506-2930-414c-a40b-8bf57ded5924:1819273Javier LunaJavier Luna0http://forums.asp.net/thread/1819273.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=1012&PostID=1819273<p>There non exists Visual Source Safe 2003.</p> <p>Visual Studio 2003&nbsp;has use Visual Source Safe 6d. But if you dont have used Visual Source Safe 6d then you would have to install Visual Source Safe 2005 now.</p>http://forums.asp.net/thread/1818729.aspxMon, 23 Jul 2007 18:54:49 GMT4c671506-2930-414c-a40b-8bf57ded5924:1818729mappermapper0http://forums.asp.net/thread/1818729.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=1012&PostID=1818729<font size="3"><font face="Times New Roman">At work we&nbsp;upgraded visual studio 2003 to 2005. We havent used source safe yet but are planning on installing it.</font></font> <p><font size="3"><font face="Times New Roman">Is using source safe 2003 with visual studio 2005 environment alright to do? We dont want to get&nbsp;the new 2005 source safe licenses if we dont have to, we just need the basic vss functionality anyway. Anyone else doing the same? Have ya come across any problems? Is 2005 backwards compatible to check in/out files within our project environment? Anything to watch out for? I havent used source save since visual studio 6. It basically work the same right? Thanks for any information you can provide. Or links&nbsp;to sites I should read.</font></font></p> <p>&nbsp;</p>