"Longhorn" SDK Usage

Hari posted about some of the features in the next version of the SDK, currently known as the “Longhorn” SDK. One feature is the ability to “target” the SDK based on the type of work you are doing or the type of information you want. We are currently debating how the “Longhorn” SDK will be used in this fashion. Some ideas being tossed around:

• Different disciplines such as “ASP.NET Developer, DirectX Developer, Data Developer”
• Based along current SDK lines such as “Platform SDK, .NET Framework SDK, DirectX SDK”

The idea being that if you indicate that you are a ASP.NET Developer, the SDK client would aggregate and present the topics that would be of interest to you or help you do your job better. Such topics may include reference documentation of ASP.NET, perhaps the ADO.NET reference documentation, all ASP.NET samples, all technical articles and blogs that relate to ASP.NET.

Part of this also implies that you can “componentize“ the SDK this way, so that you are only downloading and/or synchronizing the content you care about.

So the question is, do you like this idea? What level of granularity would you like? Do you just want to download the entire SDK, then filter on your own? Let us know!