ASP.NET 2.0 is magic..and not in a good way
Call me a control freak, but I really dislike the magical aspects of VS 2005 & ASP.NET 2.0. 
You know, the times where HAL VS2005 says "We'll fix that up for you, don't worry how".
Or "You don't have to write code, just give us a hint and we'll do all the work!".
Pfffffffffffffffft
The "project" debacle didn't help; the new magical "web app" and "web site" project types that do special things. Here's the thing - PROJECTS WEREN'T BROKEN.
But this magic is just for newbies, right? To make it easier for non-programmers to develop web sites using ASP.NET?
So tell me why I'm wasting hours of billable time today having to fix this magic when some code was moved from a web app to a normal assembly. Oh, sorry, that won't work - the magical "we'll fix that" pixie dust isn't there in the types of projects that we actually use.
(an example: I now have to go through and declare dozens of members in my codebehind that in a web app are magically defined)
Scott, I wish you'd listened when we all expressed our opinions on this. It really didn't work out you know.
Sing it together - remove the magic! kill declarative programming!
ASP.NET 3.5 Web Hosting: 3 Months FREE + FREE Setup - CLICK HERE!