Get a jump on the growing need to create and edit Office documents (mostly Word and Excel documents) programmatically from .NET applications. Dino Esposito demonstrates two approaches.

ADO.NET 2.0 introduces enhancements to the .NET provider model and SQL Server managed provider, which go a long way towards getting better support for specific database features within the boundaries of a common object model.

ASP.NET 2.0 abstracts the Web developer from the creation of server requests and the logic needed to parse the server's responses. Script callbacks offer a ready-to-use mechanism that greatly simplifies the procedure.

To move the session state from the local memory (the ASP.NET cache) to a SQL Server table, all you do is modify an attribute in the web.config file. You don't need to recompile or even touch the code. Learn about the magic behind this behavior, which the ASP.NET 2.0 provider model provides.

With the first alpha of ASP.NET 2.0 just around the corner, the debate about the effective goodness of code-behind seems to be close to its end.

It's known that the .NET Framework version 1.1 is a minor upgrade with a relatively limited set of changes and updates. Get a gist of the changes with this list of five programming related differences between ASP.NET 1.0 and ASP.NET 1.1.