| |
| Net Framework is a collection of tools which facilitates rapid software development. It has a library of pre-coded solutions to common program requirements and controls the execution of programs written specifically for the framework. |
| |
| The reason for popularity of ASP.Net is that, it is objective in nature and the web applications which are developed are in interface with database. Another main advantage of using ASP.Net is that web developers can set up pages or particular area of pages that are commonly reused to be cached for a set period of time, this helps in improving the web applications. The ASP.Net is faster as compare to J2EE, the ASP.Net allows caching of data from database due to which doest slows down the website. The ASP.Net also offers instant solutions for memory leak and crash protection. It recovers by design from errors and facilitates constant availability of the website to the visitors. The web developer also prefer .Net framework because it allows the exchange of instances of types between programs written in any of the .NET languages. This gives a comfort level to the webmaster. |
| |
| An veteran web user makes optimum use of these advantages to create SEO friendly pages to generate maximum web traffic.The Webmaster uses ASP.net to build CMS (content Management System) driven website with no nonsense URL. Such websites are search engine friendly websites. |
| |
| Master Pages is a set of features offered by ASP.Net which gives a common structure. The interface elements such as page header, footer or navigation bar are on a standard spot called “Master page” which can be shared by many pages on the website. This allows effortless maintenance and unnecessary duplication of code due to shared structure is also avoided. A Master page is a normal webpage saved under .master file extension. It has special type of control called a Content Place Holder control. The Content Place Holder defines a region of the master page that can be substituted with content from a page linked to the master. The Content Place Holder contains default content. |
| |
| A page associated with Master page is called content page, the ASP.Net while depicting the page will combine Master page and content page and serve the visitor. The code of a content page appears as follows: |
| |
<%@ Page Language="C#" MasterPageFile="~/InnerPage.master" AutoEventWireup="true" CodeFile="Default2.aspx.cs" Inherits="Default2" Title="Untitled Page" %>
<asp:Content ID="ContentLeft" ContentPlaceHolderID="Left" Runat="Server">
</asp:Content>
<asp:Content ID="ContentMiddle" ContentPlaceHolderID="Middle" Runat="Server">
<div class="breadCrumb"><asp:SiteMapPath ID="BreadCrumb" runat="server">
</asp:SiteMapPath></div><div class="Content" runat="server"></div>
<asp:SiteMapDataSource ID="CrumbSource" runat="server" StartingNodeUrl="~/Default.aspx" />
</asp:Content> |
| |
| The Content elements on the content pages control only relevant pages. |
| |
| Now the next step is to attract search engines by setting Page title, Meta Tags vibrantly to become visible. This can be done either centralizing i.e. to position everything on Master Pages with default values. Or the webmaster can add meta tags to every content page. If the webmaster opt for latter, then in order to revise meta tags, the directives are required to access elements on master page. This can be done by Master.ElementName. In a layman terms the Optimizer has set a value for meta tag. Each meta tag has an ID and marked as runat = server. The Meta tag and title are based on content requested. |
| |
| Usually the websites have URLs which are cluttered, and search engines have general tendency to avoid them. In order to create a Search engine friendly URL, the webmaster will give each content page URL and link each URL to an actual URL in a XML file. This will help in gaining more performance. |
| |
| The next step is to write a HTTP Module to manage all content page URL’s and to deliver the content from the real URL. This is done by creating separate project of type of class library. (Class library is collection of subprograms used for developing software). The optimizer inserts a class in the library which compiles HTTP Module. |
| |
namespace URLHooking
{
public class PageSource : IHttpModule
{
public PageSource(){
}
public void Init(System.Web.HttpApplication application)
{
//IHTTPModules Init Function where we declare the delegate for the PostResolveRequestCache event.
application.PostResolveRequestCache += (new EventHandler(this.Application_OnAfterProcess));
}
private void Application_OnAfterProcess(Object source, EventArgs e)
{
HttpApplication application = (HttpApplication)source;
HttpContext context = application.Context;
if (!System.IO.File.Exists(application.Request.PhysicalPath)) {
tmpRealURL = GetRealPathFromXML(application.Request.PathInfo); // Parses the XML File and Get the Real URL
context.RewritePath(tmpRealURL);
}
}
}
} |
| |
| This project is saved as DLL (Dynamically Linked Library), the webmaster constitutes this as HTTP Module in the website. The webmaster places following configuration in the Configuration/ System.web and complies the project. |
| |
httpModules>
<add name="PageSource" type="URLHooking.PageSource, URLHooking"/>
<!-- name=”Class Name” type=”NameSpace.Classname, AssemblyName” -->
</httpModules |
| |
| As all the redirections are processed in the server the browser remains unaware of the same while requesting a webpage. |
| |
| A skilled webmaster aim is not to create a website to give a visibility to the clients but also to make it felt by developing a search engine friendly website. To promote a website with static HTML content is not a tough job. But developing and promoting a website with .NET framework is a real test of Optimizer’s potential. |
| |
