Hosting ASP.NET sites on IIS 7.0
IIS 7.0 provides the ASP.NET Integration by default, It supports both the new and old integration modes that can be used side by side on the same server. On IIS 7.0 you can run multiple ASP.NET version applications using integration and classic modes .
AJAX Client –Side templating in ASP.NET 4.0
The AJAX in ASP.NET 4.0 introducing new client data rendering features to page and component developers. It allows the developers to render JSON data from server as HTML in a highly efficient way. This post discuss about one of the AJAX features in ASP.NET 4.0.
You need to download the AJAX scripts from following location to test the sample
Session State in ASP.NET 4.0
This post explains about Shrinking session state in ASP.NET 4.0
ASP.NET Provides two options for storing session state for web applications.
1. Out of process session state
2. MS SQL server session state
Permanently Redirecting a Page in ASP.NET 4.0
Web applications commonly move the pages and content around the servers. This results to accumulation of old links in search engines.
Traditionally this was handled in ASP.NET using the Response.Redirect method to forward the request to the new URL. However Redirect method issues an HTTP 302 found (temporary redirect) response. Redirect method results in extra round trip when user accessing the old URLs.
No comments
Auto Start Web Applications in ASP.NET 4.0
Some web applications require large amount of initialization processing time before serving the first request. In some cases web applications may also need to load the large amount of data in first request.
In earlier versions we used write the custom code in Application_Load method in Global.asax file to handle above scenarios.
ASP.NET Error Handling
This article explains about adding error handling capabilities to the ASP.NET Web application. It also explores the possible ways to handle and log the errors that occur in the application.
There are two types of exceptions that can occur in web application.
No commentsDocumenting C# code with XML Comments
This article explains an easy and effective way of documenting your C# code. XML comments are the solution for generating a clean documentation for your code. Visual Studio environment allows you to generate a documentation file for your project. It helps your teammates and other people who using your code.
This post will explain how to use XML comments in code and how to generate XML help documents from those comments.
XML Comment Basics
XML comments can be used to all types except namespaces. The types can be Class,Module,Interface, Enum, properties, events and methods.
XML comments are inserted inline, directly in your source code. To insert an XML comment type three single “///” immediately above definition.
No commentsGAC in .NET Framework
The Global Assembly Cache known as the GAC is to enable sharing of assemblies across several managed applications installed on a machine. All managed developers can install assemblies to the GAC and share them across applications.
When to Use the GAC
When should an assembly be installed in the GAC as opposed to assembly in application base? If you have any assembly that must be shared across multiple applications and hence centrally serviced. Shared frameworks and components typically fall under this category.
It is a machinewide repository of managed assemblies.
When shouldn’t an assembly be placed in the GAC? If you need the application to be xcopy deployable on different machines, placing the assembly in the GAC is probably not best idea. In this case the assemblies in the GAC will also need to be moved across machines.
Binder follows the “GAC always wins” policy.
GACUtil is a tool used to install, uninstall the assemblies to and from the GAC.
This tool ship with .NET Framework SDK. In .NET Framework 4.0, the GAC went through a few changes. The GAC was split into two, one for each CLR.
The CLR version used for both .NET Framework 2.0 and .NET Framework 3.5 is CLR 2.0. There was no need in the previous two framework releases to split GAC. The problem of breaking older applications in Net Framework 4.0.
To avoid issues between CLR 2.0 and CLR 4.0 , the GAC is now split into private GAC’s for each runtime.The main change is that CLR v2.0 applications now cannot see CLR v4.0 assemblies in the GAC.
No comments
