The DOT NET Framework with the version 4 comes with several improvements in key areas. Microsoft Visual Web Developer Express and Visual Studio 2010 also feature many new features and enhancements for enhanced web design and development.
ASP.NET key services
ASP.NET 4 version several new exciting features which help in improving the core services of ASP.NET, like session state storage and output caching.
Web.config File Refactor- The Web.config documents containing the configuration details for a website application indeed has grown significantly in the recent past releases. Several new features are added to the DOT NET Framework. In the version 4 of the DOT NET Framework, the key elements of a configuration are transferred to a machine, config document. The applications here now have the same settings. This enables Web. Config file located in ASP. NET version 4 apps to remain empty or specify which of the versions of this framework is targeted by the application.
Extensible Output Caching
Ever since ASP DOT NET 1 version was launched, output caching had allowed the developers for storing the developed output of HTTP responses, controls and pages in the memory. On further Web requests, ASP DOT NET is also capable of serving content in a fast way since it retrieves the created output directly from memory rather than redeveloping the output all from scratch. However, there are few limitations to this approach. The developed content is always required to be stocked in the memory. On those servers experiencing heavy traffic, particularly memory requirements asked for output caching are enabled to contend with memory needs of other parts of any web application.
ASP.NET version 4 renders extensibility to the task of output caching, which allows the user to easily configure one or even more than one customized output-cache providers. These providers are able to make use of any of the available storage mechanisms for persisting HTML content.
The available storage options may include remote or local disks, distributed cache engines and even cloud storage. Extensibility of output-cache provider, as seen in ASP DOT NET 4 version enables one to design an intelligent and more aggressive strategy for output-caching in a bid to create great web sites, and at the same time, caching those pages receiving low traffic on the disk. As an alternative, one can even cache all vary-by combinations for any rendered web page, but make use of distributing cache to ensure memory utilization gets divested from the web servers functioning at the front-end. One also gets to create customized output-cache provider in a form of class that is obtained from the type of OutputCacheProvider. The user can then start configuring provider seen in Web. config file by making use of the subsection of new providers for outputCache element.
As a default, the version 4 of ASP DOT NET has all rendered pages, HTTP responses as well as controls using output cache from in-memory. The default Provider trait for ASP DOT NET is the ASPNetInternalProvider. One can alter default output-cache provider which is used for website application by identifying a unique provider name for the defaultProvider element or attribute.