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. "
Please, educate yourself before trolling utter rubbish like the one in your comment. Some people might believe it.
.NET technology that is used for web browsers is ASP.NET. ASP.NET produces standards compliant xhtml and JavaScript that is sent to your browser. The only place where you will need to upgrade to .NET 3.0 is in the web server. Server side browser technologies never leave the server. They translate its content to something that your browser will understand. When you click "view source" you are not viewing .NET, you are viewing its output.
.NET 3.0 to run .NET 3.0 browser apps in the same way that you don't need to download PHP, Python, Ruby or Perl to your computer to use Slashdot or Digg or Google, etc.
The
You don't need to download
I think you mean version 1.1 of the .NET Framework, not 1.3. Also, we published a very detailed list of breaking changes from 1.1 to 2.0 on MSDN. We never take a breaking change lightly, every single one of these would have been reviewed with a great deal of scrutiny to ensure that we really were doing the right thing under the circumstances.
With regard to .NET 3.0 (no longer WinFX 3.0), it's the next version of the .NET Framework. As a result, it includes new features, like WPF (Avalon), WCF (Indigo), and a ton of other cool, new things. This is merely a marketing change, no more.
No, but I used to work for Microsoft.
The rebranded WinFX (now .NET Framework 3.0) contains the RTM release of .NET Framework 2.0 (the runtime) as well as WPF (Avalon), WWF, and WCF (Indigo). It represents a superset of the 2.0 runtime.
Yes, I work there too.
You should have to change almost nothing to get a .NET 2.0 app working in .NET 3.0. The new version is essentially .NET 2.0 plus WinFx.