This post originated from an RSS feed registered with .NET Buzz by Peter van Ooijen. Original Post: .NET 3.0, formerly known as... Feed Title: Peter's Gekko Feed URL: /error.htm?aspxerrorpath=/blogs/peter.van.ooijen/rss.aspx Feed Description: My weblog cotains tips tricks and opinions on ASP.NET, tablet PC's and tech in general. Latest .NET Buzz Posts Latest .NET Buzz Posts by Peter van Ooijen Latest Posts From Peter's Gekko

Almost everybody wanted to say something on the .NET 3 moniker. From FUD like the return of DLL-hell. To the notion that whatever poetic or dull name a piece of software had to live under, it's all just another target for your C#/VB.NET/<your favorite language here> code.  The only one thing which really worries me is the documentation. Take this snippet which comes with the current WinFX sdk:

What's Next
You now have a number of techniques to handle input in Windows Presentation Foundation (formerly code-named "Avalon"). You should also have an improved understanding of the various types of input events and the routed event mechanisms used by Windows Presentation Foundation (formerly code-named "Avalon").

Additional resources are available that explain Windows Presentation Foundation (formerly code-named "Avalon") framework elements and event routing in more detail. See the following overviews for more information, Base Elements Overviews, Element Tree overview, Events Overview, and the Routed Events Overview.

Looks like a brain dead macro put it's mark on an original document. Making it almost unreadable. What will the .net 3 version of this doc look like? Wouldn't this be the moment to just drop all of this "formerly known as" name-fetishisms. It's up to Sam what to do with his blog title.