Skip to main content

Asp.Net 4.0: An Overview-Part-I

Asp.net 4.0 introduces a lot of new features and controls that can be broadly categorized as depicted below.
1. Server Side enhancements
2. New Controls
3. ASP.Net MVC enhancements
4. Dynamic Data

This post covers only the First part i.e. Server Side enhancements.
Server Side Enhancements
A) Caching Enhancements
B) Shrinking Session State
C) Performance Monitoring Improvements 
D) Shrinking Web.config
E) Shrinking session state
F) View state on individual controls
 
Caching Enhancements
Prior to Asp.net 4.0, page output is stored in memory in a private area of the ASP.NET cache. If the Caching is done for large number of pages, the output cache puts additional pressure on the web server by consuming memory and generating frequent updates to the cache object. ASP.NET 4.0 introduces new concept of  storing page responses outside the ASP.NET worker process. The new Cache API enables the usage of any of the storages that includes storing cache data in disk, storing cache data using custom cache providers, storing cache data on a separate server and storing cache data on a cloud database
 Creating custom output-cache provider is as simple as deriving a new class from the newly introduced System.Web.Caching.OutputCacheProvider type.
This provider needs to be registered in the web.config, by using the new providers subsection of the outputCache element, as shown in the following example
<caching>
   <outputCache defaultProvider="AspNetInternalProvider">
   <providers>
     <add name="DiskCache" type="MyCProvider.MyCacheProvider.DiskOutputCacheProvider, DiskCacheProvider"/>
   </providers>
    </outputCache>
    </caching>

DefaultProvider in ASP.net is AspNetInternalProvider that can be altered by changing the default output-cache provider used for a Web application by specifying a different provider name.

If the above description is exciting, here is another perk.
different output-cache providers per control and per request can be selected by choosing a different output-cache provider for different Web user controls declaratively by using the new providerName attribute in a control directive, as shown below.
<%@ OutputCache Duration="60" VaryByParam="None" providerName="DiskCache" %>
Specifying a different output cache provider for an HTTP request adds a twist. Instead of declaratively specifying the provider, new GetOutputCacheProviderName method is overridden the in the Global.asax file
public override string GetOutputCacheProviderName(HttpContext context)
{
if (context.Request.Path.EndsWith("Advanced.aspx"))
return "DiskCache";
else
return base.GetOutputCacheProviderName(context);
}
There is one additional enhancement called Output Cache Substitution, which can be used to cache the output of web pages that contain dynamic data:
<asp: Substitution ID= "cacheSubstitution" runat="server" MethodName="Test" />      
 
Hurry spoils the Curry..let’s not cover the other details in this post and take some time to digest the new knowledge described here.
The next post will explore the remaining features.
Till Next we connect……….
Happy learning

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...
Post a Comment
Read more

Covariance and Contravariance-General Discussion

If you have just started the exploration of .Net Framework 4.0, two terms namely Covariance and Contravariance might have been heard. The concept that these terms encapsulate are used by most developer almost daily, however there has never been any botheration about the terminologies. Now, what actually these terms mean and how are these going to affect us as a developer, if we dive in to the details. The simple answer is it’s always good to know your tools before actually using them. Enough philosophy, let’s get to the business. Starting the discussion let me reiterate that in addition to Covariance and Contravariance, there is another terminology, Invariance. I’ll by start here by diving into the details of Invariance and then proceed further. Invariance: Invariance can be better understood by considering the types in .Net.>net has basically two type, value-types and reference-types. Value types (int, double etc) are invariant i.e. the types can’t be interchanged either ...
1 comment
Read more

WCF-REST Services-Part-I

What is REST? REST stands for Representational State Transfer. REST as described in MSDN, “is an architectural style that can be used to build software in which clients (user agents) can make requests of services (endpoints)”. REST is one way to implement a client-server architectural style. A service that uses the architectural style of REST is generally referred to as a RESTful service or endpoint. RESTful endpoint Building Blocks 1. Resources(What resources would the service Serve/Offer) 2. URI(Identifiers used to represent the resources) 3. HTTP Verbs (What parts of the uniform interface (HTTP verbs) are each URI going to support, like Get/Post etc.) I’ll develop a hypothetical system that will make use of these blocks in the next article, let us consider the theoretical aspects of the REST in this post. Why REST? As explained above, REST internally implements a Client/Server model that can be easily achieved by using SOAP with ASMX or WCF. Just for the discussion sake ...
Post a Comment
Read more