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

Authentication using Social Networking portals(Facebook, Gmail, and Yahoo)

There are tons of sites, which offer sign on using the social networking site credentials (Facebook, gtalk, twitter and the list continues).It can be termed a “SINGLE SIGNON” and offers a lot of benefits compared to traditional database authentication approach. However, not storing user credentials in the DB imposes an additional risk. How to track who all logged into the system. Now the question is, which approach to follow. The best approach is to use inbuilt asp.net users for storing the logging info about user activities and using single signon technique for authentication. This article will explore the approach and provide the details of implementation using some third party libraries and customizing it to the requirements. The Authentication will be done using the following networking portals Yahoo  Gmail Facebook    Special thanks to my friend Sumit Khandelwal, for implementation of Facebook part (in fact he did it all!!) Except Facebook, all other ca...
2 comments
Read more

WPF Overview-Part-II

This post is in continuation to the last post. In this Post I’ll be exploring the Dependency Properties Dependency properties are similar to CLR properties with more advanced and complex features. The main difference between the CLR properties and dependency properties is, that the value of a normal .NET property is read directly from a private member in your class, whereas the value of a DependencyProperty is resolved dynamically when calling the GetValue() method that is inherited from DependencyObject . In case this description did not make sense, no need to worry, It will become clear by the time you reach end of this article. How the Value is Resolved in Dependency properties Every time a dependency property is accessed, it internally resolves the value by following the precedence from high to low. It checks if a local value is available, if not, check if a custom style trigger is active and I the similar manner continues until it finds a value. At last the default value is alwa...
Post a Comment
Read more

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