. Topicala Page Index Token

A Journal about the experiences I have developing little applications in C#, Perl, Html and Javascript and talking about things new things that I use. Always Geeky; Always Nerdy; Always poor Grammer!

I am a Software Analyst Developer working in Southport, England but living in Liverpool. I develop mainly in C# and ASP.Net. I have been developing comercial software for several years now. I maintain this site (hosted at SwitchMedia UK) as a way of exploring new technologies (such as AJAX) and just generally talking about techie geek issues. This site is developed through a host of Perl scripts and a liberal use of Javascript. I enjoy experimenting with new technologies and anything that I make I host here.

Quick Search

Web www.kinlan.co.uk

Friday, June 09, 2006

.NET Framework 3.0

I have just seen the following over at Somasegar's blog (http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx)

With this in mind we have decided to rename WinFX to the .NET Framework 3.0. .NET Framework 3.0 aptly identifies the technology for exactly what it is – the next version of our developer framework.

The change is in name only and will not affect the technologies being delivered as part of the product. The .NET Framework 3.0 is still comprised of the existing .NET Framework 2.0 components, including ASP.NET, WinForms, ADO.NET, additional base class libraries and the CLR, as well as new developer-focused innovative technologies in WPF, WCF, WF and WCS:

I don't see any mention of c# 3.0 in this package. I think this name change is pointless and confusing! Really, the reasons they give are not that convincing!

Related Tags
[feed], [feed], [feed], [feed], [feed], [feed], [feed], [feed], [feed], [feed], [feed], [feed], [feed], [feed]

Related Wikipedia Documents
, , , , , , ,

My Related Documents
, , ,

Related Amazon Books
Naked Conversations : How Blogs are Changing the Way Businesses Talk with Customers: / CLR Via C#: Applied .NET Framework 2.0 Programming: / NET 2.0 Wrox Box: Professional ASP.NET 2.0, Professional C# 2005, Professional .NET 2.0 Generics, and Professional .NET Framework 2.0: / Beginning Visual C# 2005: / Windows Forms 2005 Programming in C#: / Pro .Net 2.0 Windows Forms and Custom Controls in C#: From Professional to Expert: / Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries: /

Related Images From Flickr

Comments: [Add New]

I disagree. I like the name change. It brings consistency to the product. On the flip side I always felt WinFX was WAY more confusing.

By Anonymous, at Friday, June 09, 2006 11:15:00 PM

I think it should have been a minor version like 1.0 -> 1.1. It should have been called 2.1 or something. But definatly not 3! IMHO.

By Paul Kinlan, at Saturday, June 10, 2006 8:37:00 AM

It's a misnomer, and it jams the .NET Framework. They're going to be in a real bind when they try to come up with numbers for the next versions -- i mean right now they're considering a "3.5", and that's already ridiculous enough. The Compact Framework isn't going to have WinFX, so the "3" isn't going to make any sense at all.


By rei, at Thursday, August 10, 2006 7:44:00 AM