This post originated from an RSS feed registered with .NET Buzz by Eric Gunnerson. Original Post: How do you organize .NET? Feed Title: Eric Gunnerson's C# Compendium Feed URL: /msdnerror.htm?aspxerrorpath=/ericgu/Rss.aspx Feed Description: Eric comments on C#, programming and dotnet in general, and the aerodynamic characteristics of the red-nosed flying squirrel of the Lesser Antilles Latest .NET Buzz Posts Latest .NET Buzz Posts by Eric Gunnerson Latest Posts From Eric Gunnerson's C# Compendium

Shaykat and I have been having a discussion about how we organize information that we present to customers. Specifically, we're trying to figure out how to present “What's new/what's changed” information. There are two options we've been considering.

The first option considers the language attribute to be the high-order bit. It would look something like:

What's new in C#
* C# Language
* C# IDE
* Debugger
* XML
* Data
* ASP.NET
* Windows Forms
* Smart Client
* CLR
* BCL

What's new in VB
* VB Language
* VB IDE
* Debugger
* XML
* Data
* ASP.NET
* Windows Forms
* Smart Client
* CLR
* BCL

The second option is to consider language one of the organizational attributes, but not the only attribute. It would look something like:

What's new in C#
* C# Language
* C# IDE

What's new in VB
* VB Language
* VB IDE

Application Types
* What's new in ASP.NET
* What's new in Windows Forms
* What's new in Smart Client applications

Technologies
* What's new in the CLR
* What's new in the BCL
* What's new in Data
* What's new in XML

Which one of these organizations do you prefer? Please add a comment with “Language” if you prefer the first one, and “Attribute” if you prefer the second one. Or, if you think there's another organization that's better, feel free to explain.

Thanks

Eric