To beta or not to beta-- The previewer's dilemma
I went to the PDC. I got the bits. I played with Whidbey and ASP.NET 2.0. I fell in love.
Back in the real world of work, I'm about to start a 4-6 month project. During this project we'll have to:
- Use (or write our own) a page templating solution that will allow a consistent look and feel across the site with minimal effort per-page. Hmm, master pages would be perfect
- Allow personalization. Hmm, doesn't asp.net 2 have a personalization engine?
- We'll use objects as data sources. Unfortunately our interns will have to forgo the use of the designers because they don't support this at design time. Hey, doesn't whidbey have an object datasource?
We'd like to:
- validate against XHTML. Not going to happen with VS2003.
- pre-compile the huge number of pages / ascx's this project may have to catch compilation errors before the page or code-path is hit. Wish I could do this
Yikes- I want Whidbey! Now!. I can get lots of this now from different or home-grown solutions, but in 9 months or a year when this application is re-visited, I'll be using Whidbey. Wouldn't it be great if I didn't have to
- Spend time now hacking together what whidbey already has in the alpha?
- Not have to rewrite the code later to use whidbey features? (or support both?)
So here I am, reimplementing things that Microsoft has already built, grumbling because I can't use it. This doesn't even touch the other things I want (generics, refactoring, stencils, other “neat“ features)
I don't understand why people would want to consult a psychic - It sucks to know the future when you're stuck in the present.