ASP.NET provides extensive tracing and debugging capabilities, an area that has been neglected for web developers in the past. With its new compilation model, debugging a page becomes as natural as debugging any other application.
ASP.NET provides three primary forms of caching: page level output caching, user control level output caching (or fragment caching), and the Cache API. Output caching and fragment caching have the advantage of being incredibly simple to implement, and are sufficient in many cases. The cache API provides additional flexibility (quite a lot, in fact), and can be used to take advantage of caching throughout every application.
The ASP.NET Web Matrix Project Guided Tour is a series of walkthroughs and supporting commentary designed to quickly acquaint developers with the syntax, architecture, and power of the ASP.NET Web Matrix Project development environment. The walkthrough samples are designed to be short, easy-to-understand illustrations of ASP.NET Web Matrix Project features.
Programmers familiar with JSP's Model II/struts architecture and others generally familiar with Model View Controller (MVC) architectures, immediately wonder how the MVC pattern can be applied in an ASP.NET world. This article demonstrates how the MVC pattern can be applied to an ASP.NET web application without breaking the basic Microsoft supplied architecture.
The objective of this lab is to convert a simple JSP application into an ASP.NET application using the Java Language Conversion Assistant (JLCA). The JSP application is a simplified e-commerce scenario, consisting of two JSP pages, a Servlet, a tag library consisting of a single tag, and the SQL Server Pubs database.