   Coding with Different Versions of VS.NET
  ok,so here''s an annoyance for which i am hoping there is a cure:the short:Can I get VS.NET 2003 to run .NET 2002 formated solution files without converting them?the long:So at home i have VS.NET 2002, at work i have VS.NET 2003.  I occasionally run out of things to do at work and like to work on hobby projects to help me learn more at the edges of my knowledge.  However I''ve discovered that .NET 2003 refuses to run .NET 2002 project solutions without converting them to .NET 2003 format.  THe problem is that .NET 2002 obviously can''t realy the 2003 solution format so once i convert it at work, it no longer works at home.  a-NOY-ing.My current and horrible solution is to maintain 2 seperate solution files one for 2002 and one for 2003.  I tend to not make many changes in the project settings so this is normally ok, but sometimes i go crazy and add libraries, change runtime libraies, etc and re-making all the changes at home has sometimes taken upwards of an hour.So how can I make these 2 different versions play nice without spending the $500+ for an upgrade to my home edition?  Am I just being retarded?  I swear that i''ve run a VC6 project in .NET 2002 without converting it, but maybe my memory is failing as it so often does...-me 
  I have a similar issue, I produce some open source libraries and examples and the like, and while I personally use VS2003 a lot of my users cry because they use 2002, sharpdevelop, monodevelop, c# builder, etc...  So I''m in the process of changing my build system to <a href="http://nant.sourceforge.net/">NAnt</a> and my project/solutions to use <a href="http://premake.sourceforge.net/wiki/pmwiki.php">Premake</a>, perhaps Premake would be of use to you... ;  yeah, i can code up makefiles no problem and those work find.  i''m just inherrently lazy and don''t like the upkeep required for such systems.  i''ve never really played with ant all that much but it is an appealing option.i just want VS.NET to be able to "save-as..." an older version and to be able to read older versions, just like MS Word and the other MS Office products.whatever, not really a big deal.-me ;  There are some tools out there that can convert from vs2003 files to 2002 ones. Try google. ;  <smacks head>word, i''m retarded for not looking.http://www.eggheadcafe.com/articles/20030425.aspthanks-me 