Web 2.0, Meet .Net 3.0

An anonymous reader writes to mention an eWeek article about Microsoft's move to rename WinFX to .Net Framework 3.0. Microsoft has also announced the availability of the beta version of the MSDN Wiki, the company's first step toward allowing customers to contribute to Microsoft's developer documentation. From the article: "It is purely a branding change, company officials said. The gist of the issue is that Microsoft has two successful developer brands in WinFX and .Net, and the company has seen 320,000 downloads of WinFX -- and 700 signed GoLive licenses -- since the December Community Technology Preview, and more than 35 million downloads of the .Net Framework since the November launch. "

Comments

Re:Microsoft just seems to be kind of flailing.

[SpryGuy]

Totally off topic (and I'll probably get modded down) but this annoys me so much I have to bitch to someone: Windows XP groups taskbar buttons for you automagically when you have a lot of windows open... but there is no way to right-click and say "ungroup these buttons" when you close some other windows and make more room. Never a day goes by that I don't wish for an "ungroup" ability. I don't turn off the 'grouping' function completely because I do like it... i just hate that I can't undo it when I want. Why implement only HALF a feature? Ugh.

Now, back on topic... possibly one of the issues of confusion with .Net 3.0 is that one wonders if the existing 2.0 stuff is obsoleted in favor of the new things added? Or is existing stuff upgraded? Or what? Is something a "new version" of an API if it includes a 100% new set of APIs, but also includes the "old" ones just for backwards compatibility? Is WinForms being abandoned in favor of the new stuf? Is there some more detail (I haven't been following) on exactly what is going on?