Total Confusion Over ASP.NET 2.0

Does anybody get a headache from seeing contradictory statements coming from all possible directions, "experts", "insiders", etc, about ASP.NET 2.0? Or is it just me?

I write for the .NET Framework each and every day, and often times including week-ends. I'm a technology addict. Nevertheless, I find it hard to understand what is going on at the Microsoft beehive.

Avalon? Indigo? Longhorn? Whitehorse? Whidbey? Wtf? No, wait, the last one doesn't count. Having read Dino Esposito's ADO.NET 2.0 broke up in pieces? post I realized I was officially totally confused. Maybe I need to stare into the screen reading Dino's post and try to see a Magic Eye picture with the .NET 2.0 roadmap. Don't get me wrong—I have a ton of respect for Dino. He's one of the brightest people in the "developer community".

Also, as a suggestion, I would recommend to stay away from books on ASP.NET 2.0 for now, at least until there's a solid delivery date and clear knowledge of what's in and what's not. I went to a .NET training class back in Atlanta 3 years ago, and our instructor was kind enough to tell us how WROX was throwing people and sloppy content together to write their A Preview of Active Server Pages+. Unforgettable.

Hey, I have the right to bitch about it because I bank my career on this. I take my work very seriously. People, quit jerking us around.

Have to admit. .NET 2.0 is not looking good. Dare recently announced the end of XSLT and XPath 2.0 in .NET 2.0.
http://blogs.msdn.com/dareobasanjo/archive/2004/05/13/131166.aspx

Sounds like the M$FT gang has spent too much time evangelizing and not enough time writing code.