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.

[Vancorps]

You're definitely new to the .Net world and appear to have completely missed the whole existence of Mono which works with Apache on Linux. I believe other platforms are getting it soon as well but your statement is already out of date. A lot of apps will work in mono without much if any trouble. So where's the vendor lock-in exactly?

Of course with us we were running a web server with the 1.1 framework on a 32bit server when we ran into performance issues because we were more than 1000 times the traffic we regularly get. Fortunately this was an Opteron box so we popped on 64bit Windows and the 2.0 framework since 1.1 isn't available. Everything worked without having to make a single change to any of our code.

That is not to say their aren't some funky things that won't transfer over but you speak out of just plain ignorance or prefer to focus on minor details that affect but a few people. With that said I've never had a Windows update break any .Net app unless you chose to code around bugs which were later fixed. That should be easy to determine since every update tells you what is changed and in the case of a framework update which occur rarely you are told exactly what it will break so it should be easy. Your code is documented right?

Of course this is all moot considering updates in any corporate setting don't occur automatically but after happen after approval and testing so you'll know if it'll break your app assuming you have a proper testing environment which I definitely know a few don't. Of course I don't know any development houses which don't since staging on a production server is well, you know, not wise ;)

Don't mean to be harsh but realistic here. You're gripes are completely inaccurate so if you really want to gripe go ahead and find valid gripes. I'm not sure what they would be with the framework but I'm sure there are some out there.