What’s your opinion: Quickstarts in the SDK?

Should Quickstarts be in the SDK or just hosted online by the ASP.NET Team?  The ASP.NET QuickStart is a series of ASP.NET samples and tutorials supporting commentary designed to quickly acquaint developers with the syntax, architecture, and power of the ASP.NET Web programming framework.   Quickstarts were included in the .NET Framework 2.0 SDK.  For future SDK releases, I am thinking about an exclusive Web-hosted model for the Quickstarts and would like your input for these popular samples.


Some Quickstarts depend upon a few simple SQL databases being installed, SQL Express databases being available, IIS and ASP.NET being installed and configured, and vroots setup for individual samples.  In the NET Framework SDK v2.0 most of this is handled by a couple of SDK-developed tools, which get run by the user after the .NET Framework SDK v2.0 is installed. 


The Quickstarts are hosted online, where they are updated frequently and no additional client-side installation or configuration is necessary when the Quickstarts are accessed from the Web.  A few of the samples that shipped in Quickstart format in the .NET Framework 2.0 SDK weren’t ASP.NET focused.  These would be reformatted and shipped with the rest of the .NET samples in the SDK documentation going forward.


How important is it for us to ship the ASP.NET Quickstarts in the SDK when they are being maintained online by the ASP.NET Team?


Karin Meier

Samples Content PM, Windows SDK Team

Comments (4)

  1. brandontyler says:

    I don’t mind these being online.  Just make it easy to find them and document this in the help that is installed with MSDN documentation.

  2. fsuarez2005 says:

    Windows SDK is the best thing about Windows, but I would like to see server mirrors for it.

  3. bazile says:

    There is no need to include ASP.NET quickstarts into Windows SDK. It would be enough to clearly mention the url and that’s all.

  4. BrentRockwood says:

    I’m just as happy to see the samples web-only for two reasons.  First off, they are applicable to only a small subset of developers (new ASP.Net devs).  Second, for anything that changes often, I’d prefer to access it via the web.