Lifetime of ASP.NET 1.x Projects
I had an idea--making some of the new cool ASP.NET 2.0 features available to the 1.x audience too. I started implementing the idea through my MSDN Magazine articles, specifically in the Cutting Edge column. Thus far I wrote about personalization, image management, themes, cache dependency. Future articles may revolve around master pages and Web Parts.
Feedback is excellent. Great.
Next step is (would have been?) stuffing it all into a book adding a few more chapters with real-world and advanced scenarios (i.e., DHTML programming with ASP.NET, HTTP handlers, modules). Publishers are enthusiastic at first but then soon realize that the book could hardly be out before this September, subsequently facing a potentially short lifetime: six months?
Rumors, in fact, say that the first quarter of 2005 is considered a good time for the final 2.0 platform. Let's assume this is correct, and let's assume that MS makes the announcement the Friday night or in the week of an important conference.
Are you really ready to jump on the 2.0 bandwagon the next Monday? How long do you realistically think will it take to step up to the new platform? I believe that with the exception of those who adhere to early-adopter programs, "normal" people will wait at least 3 to 6 months to take the plunge. And this amount of people is a huge number.
Are you ready to drop 1.x applications to start working (and re-design them, actually) with the 2.0 platform? (Which is great, indeed.)
Do you think you need (and invest on) more advanced 1.x education and, why not, training? You can maintain and enhance current projects while positioning yourself well for the next big release of your apps.
Let me hear your thoughts!