Visual C# Express 2005
-
I still didn't try it, but I intend doing it on a Virtual PC machine: I know I won't be able to assess performance, but I can safely use it without worrying about destroying my machine. Yes, even I am blogging now!
-
I'm using VS.NET 2005 with VS.NET 2003 and I haven't had any problems. The only thing I did have an issue with (until I realized that there's an easy way to fix it) was with ASP.NET apps running on 2.0 instead of 1.1. But then I saw the "ASP.NET" tab under the properties pages in IIS...and there's a handy little version-switcher right there. :)
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?" -Hockey on being a geek
-
Yep we're using it here at work alongside 2003. No problems. The only downsides I see is the memory usage is much higher (something like ~130 MB virtual memory size after running it for a few hours, compared to 2003's ~70MB size). Additionally all your various tools built under 1.1 (profiler, memory watcher, etc) won't work on your 2.0 apps. #include "witty_sig.h"
-
I still didn't try it, but I intend doing it on a Virtual PC machine: I know I won't be able to assess performance, but I can safely use it without worrying about destroying my machine. Yes, even I am blogging now!
Same here, it's the only way to test out betas IMHO. - Anders Money talks, but all mine ever says is "Goodbye!" ShotKeeper, my Photo Album / Organizer Application[^]
My Photos[^] New developersite: RealDevs.Net -
I've been doing it and everything seems to be fine. Signature under construction.