ASP.NET is Microsoft's next new "Version" of ASP - it is basically ASP utilizing the .NET factors described in the last two parts of this article. That means that ASP.NET pages must to be made with .NET-compatible languages, which include VB.NET, C#, and JScript.NET.

When an ASP.NET page is visited through an internet browser, the ASP.NET engine first checks to observe if there previously exists an advanced version of the IL code for the ASP.NET page. If there does this IL is spurted to the CLR and the HTML output made by the ASP.NET page is then send to the customer's browser that ask for the ASP.NET Web page. If though, the IL does not exist at all the ASP.NET page's source code has changed while the last IL was created, the ASP.NET page have to be recompiled. Depending on what language the ASP.NET page was written within the proper compiler is instantiated and the IL created. This IL is saved at disk so to for future requests, this recompilation, an expensive process, does not need to recur.

If you've created ASP.NET pages, you most likely aware of the concept of Web control. These are controls that can be used in an ASP.NET Web page to generate HTML elements like labels, list boxes, text boxes, etc. For example to create a textbox using a Web control.

In fact, an ASP.NET Web page can hold a mix of server-side code in server-side SCRIPT blocks along with in-line HTML.

So how does that HTML or server-side code get interpreted into something to the VB.NET compiler can understand. One of the ASP.NET engine's mainly important tasks is translating the HTML or server-side code keen on a class that the VB.NET compiler can understand. This procedure is a difficult one, and further than the scope of this article, however do be conscious that your pages are moved into a class that inherit from the Page class one of the classes within the .NET Framework.

In fact, all of the Web controls to you can use in your ASP.NET Web pages are stand for as classes in the .NET Framework. As well, any ad hoc HTML code in your ASP.NET Web page is detain and represented like an instance of the LiteralText class. As a result of these translations, it is no irony to say that ASP.NET Web pages are, certainly, real running programs. No longer is a dynamic Web page now some simple script.

I can explain that ASP.NET is:

• Way easy
• Way interesting
• Way powerful and user friendly language

You can do several impressive tasks easily with the help of ASP.NET, tasks that required few hundreds of lines of untidy code in classic ASP.