By lowellheddings via weblogs.asp.net Published: Feb 11 2007 / 18:48
Honestly, I'm flat out stunned that VS.NET didn't allow for this before now. How has anyone been doing legacy development before now?
Multiple installations of VS.NET installed on one machine. They mostly cooperate nicely but it is still a pain. I am constantly starting the wrong version, having all 3 versions installed on my work machine.
Same here.
Sad actually but true. Java IDEs have been able to target multiple VMs for years. Another example of Java's clear superiority over .NET.
@sproket: remember, toolset != framework. at most, this is an example of the superiority of Java IDEs over Visual Studio.NET.
Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.
Comments
daniel replied ago:
Honestly, I'm flat out stunned that VS.NET didn't allow for this before now. How has anyone been doing legacy development before now?
clintonforbes replied ago:
Multiple installations of VS.NET installed on one machine. They mostly cooperate nicely but it is still a pain. I am constantly starting the wrong version, having all 3 versions installed on my work machine.
Lowell Heddings replied ago:
Same here.
sproket replied ago:
Sad actually but true. Java IDEs have been able to target multiple VMs for years. Another example of Java's clear superiority over .NET.
supdegrave replied ago:
@sproket: remember, toolset != framework. at most, this is an example of the superiority of Java IDEs over Visual Studio.NET.
Voters For This Link (12)
Voters Against This Link (0)