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:

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

WCF-REST Services-Part-II

HOW REST is implemented in WCF Part-I of the series explored the REST conceptually and this post will explore how REST is implemented in WCF. For REST implementation in WCF, 2 new attributes namely WebGetAttribute and WebInvokeAttribute are introduced in WCF along with a URI template mechanism that enables you to declare the URI and verb to which each method is going to respond. The infrastructure comes in the form of a binding ( WebHttpBinding ) and a behavior ( WebHttpBehavior ) that provide the correct networking stack for using REST. Also, there is some hosting infrastructure help from a custom Service¬Host ( WebServiceHost ) and a ServiceHostFactory ( WebServiceHostFactory ). How WCF Routes messages WCF routes network messages to methods on instances of the classes defined as implementations of the service. Default behavior ( Dispatching ) for WCF is to do this routing based on the concept of action. For this dispatching to work, an action needs to be present in ev
Post a Comment
Read more

SOLID principles -Code Samples and Free Ebook

I planned to write code samples for SOLID principle implementations, however I am a firm believer of " NOT RE-INVENTING THE WHEEL ", when all you need is use the wheels and make a new CAR. Going by the ideology, I have found an excellent  SOLID principles FREE -Ebook ( covering all aspects of SOLID design principles, with Code sample). This book is an excellent visual aid to remember these principles, as it uses Motivational posters for explaining SOLID design principles. One additional advantage to the above mentioned book is the Code-Refactoring ebook . Both of these books can be downloaded from this EBOOK download Link Both of these books can be downloaded form here. Hope this book proves useful... Till next we connect.... Happy Learning..
Post a Comment
Read more