Care for a snowcone from Hades? JSalas uses VS.NET 2003
It's no secret that I'm not a big fan of the Visual Studio .NET IDE. Don't get me wrong....I loves me some VS2K5, but I've not really gotten off on its predecessors, what with the forced code-behind model, layers upon layers of files and extra gimmicks that take away from the web development purist I pride myself in being. Give me ASP.NET Web Matrix, Query Analyzer, and Notepad and I'm one blissful person. (Also, not being a computer science or engineering major - I have a BBA in Marketing...yikes! - I like writing code, as it makes me feel smart.)
That having been said, you may throw tomatoes...now.
I've been using my copy of VS.NET 2003 extensively over the last few weeks, getting ready for my company's NCAA March Madness Challenge, an online contest using the tournament bracket control available from
TourneyLogic. I don't normally use third-party products, but the control is best used with Microsoft's IDE, and the API was so extensive I couldn't not use it if I was to finish my project in time for the tournament. And by all that is holy...I like it.
The one thing I have enjoyed about the IDE since I started messing with the ealy beta versions in 2002 was the ease for XML web services. But I've enjoyed several aspects of the IDE, more so than I thought I would, beyond IntelliSense. Go figure.
Was that a pig I saw flying outside?