There are a couple of issues though that you should probably address in future articles on this or other ASP.NET sample applications that would avoid reader confusion.

1. Keep Assumptions to a minimum. Where you must use assumptions inform the reader that you are using an assumption. for example not every developers environment is going to include SQL Express, so it might be a good idea to tell the user that you are assuming that a local version of SQL Express Database is assumed for connectivity purposes




2. If a particular methodology or technology is expected in order to complete the sample application e.g. only works with IE6 and not with Firefox tell the user this up front so that they can ensure they have the necessary tools on hand to complete the sample application for themselves. No one likes a sample application that fails to compile or that errors out due to differences in environment.


3. Specifically when dealing with ASP.NET 2.0 and Visual Studio 2005 to develop web applications that use personalization let the user know that he will either have to define his own Provider and data store or if she uses the default aspnetdb that she will need to use the aspnet_regsql.exe tool prior to building the application and running it for the first time

Just my $0.02