Another reason why .Net 3.0 should be called .Net 2.5 (or something similar)

Check out Kirk Allen Evan's blog entry ( . All through it, his reasons given point to calling it something less than .Net 3.0 IMHO.
Again, note that .NET Framework 3.0 is an additive release to .NET Framework 2.0. With .NET Framework 3.0, the languages still use the 2.0 compilers, and leverage the 2.0.50727 Framework.
It is based on 2.0 for everything so why not keep with that!!! The version number really doesn't make anything clear!

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

Related Wikipedia Documents
, , , , , , ,

My Related Documents
, , ,

Related Amazon Books
CLR Via C#: Applied .NET Framework 2.0 Programming: / Beginning Visual C# 2005: / NET 2.0 Wrox Box: Professional ASP.NET 2.0, Professional C# 2005, Professional .NET 2.0 Generics, and Professional .NET Framework 2.0: / 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: / MCTS Self Paced Training Kit: Microsoft.NET Framework 2.0 Foundation: /

Related Images From Flickr