.Net 3.0 = .Net 2.0 + WinFx or is it another f*** marketing stunt??

It seems that the naming department in Microsoft has gone crazy in a matter of months. Or maybe nobody is really in charge anymore!

After the W naming mess (WPF instead of Avalon, WCF instead of Indigo, etc...) now they're coming with some silly idea to rename WinFX as .Net FX 3.0 (and even 3.5).

Lol, this must be a joke. I just started to think about migrating my projects from 1.1 to 2.0, then now I already have to think about 2007 to see .Net 3.0. No wait .Net 3.0 is not a new framework, it's .Net 2.0 + WinFX :-)

What a mess! Microsoft deserve an entry in the WTF blog. Check Brad Adams post for more madness.