Some of my wonderful cyberpals linked to my FUHGETABOUTIT! post. Thanks, guys! It was written from the heart. Meandering Dave not only gave good link juice, but actually spent some time today converting an ASP.NET 1.1 app to 2.0 and described the experience in his post ASP.Net Conversion Stories. Day 1. What a set a cantaloupes on that guy, eh? I could've copied his post, pasted it in my blog, put my name on it, and it would've been jake. I mean, I would have used the same tone and asked the same questions Dave did, like "what the hell did you do to the solution explorer?"
I've been wondering about that myself. One issue Dave didn't mention in his play-by-play was that in VS2003, when I was working with a file it was highlighted in the Solution Explorer, always within clicking distance. Now in this fancy-schmancy VS2005 IDE, I double-click on a compile error in the task list after migrating my 1.1 app, an .ASPX file opens in the editor window with the error "this class already contains a definition for txtName"--one of those little migration glitches because the ASPX page doesn't inherit from the codebehind page anymore--and I'm scrolling through the Solution Explorer folder looking for the darn file I need to edit. What a pain THAT is.
But hey, I want to move to VS2005 because the IDE is mostly marvelous. I simply need to repeat my buddy Dave's question, "what the hell did you do to the solution explorer?"
Here's a helpful graphic, by the way, from one of the MSDN pages I read last night, explaining some of the differences in the ASP.NET 2.0 inheritance model.
