Jay Kimble

.Net 1.x is dead! I'm the first to announce this in case you missed it.  So if you are using old ASP.Net 1.x then you should be thinking about upgrading your environments because that is outdated technology, my friend.  I want all readers of this blog to approach their immediate supervisor and demand that “we load the latest technology on our production servers. It's not fair that we have to use this outdated  technology.“  Why?  Because all the headline information that we get today is for ASP 2.0; it's the big story! So, it must be released right?  

Check this out to see what I mean:

(yep every cover article is ASP.Net 2.0 related) So I figure if it's been revealed then it must be “released.”  Let me dig out that copy of Whidbey (I don't have a community drop of VS.Net 2005, yet).  Wait this isn't a release version... hmmm let me see where can I buy Vs.net 2005... uhhh, hmmm... it's not released... What can I get?? Oh, a technology preview?!? It's not a beta yet?!? so when will it be released??  In the next couple months I bet. No?!?  When then?  Next year?!?  It must be early in the year, right? No?!? Late first quarter, early second??!!?!?! 

So why am I being barraged by this?  I'm paying good money for this magazine (why is it filled with articles about “vaporware“?  and unfortunately that is what ASP.Net 2.0 is -- I want it as bad as the next guy)

My good friend and co-worker, d.code recently posted on futuritis last month when the last issue MSDN Magazine came out. And I want to echo his comments! 

A few articles on the upcoming features are cool, but could the bulk of articles be about what I'm currently using (don't throw current technology into just the Q&A columns).  I don't have time to waste reading about technology that isn't here yet (and isn't coming for close to a year from now!) 

[BTW, the current issue according to the site -- I don't have my issue yet -- has 8 .Net articles for VS.Net 2005 and 8 .Net 1.1 articles (even coverage, kind of), but the big front page items are all ASP.Net 2.0 related... I could maybe argue for the developer toolbox article (come on we're way off... even coverage shouldn't be happening quite yet)... but evidently nothing else must be going on, so .Net 1.1 is dead  <sigh>]