Master Pages

Master pages are reusable page templates. For example, they can be used to provide the same header, footer, and navigation controls within each page in a web application.

Themes

Themes allow you to define a standard set of appearance characteristics for Web controls. Once defined, you can apply them to the website, giving it a consistent look and feel.

Navigation

The ASP.NET navigation platform includes a mechanism for defining sitemaps that describe the logical organization of pages on a Web site. In addition, there is also a set of navigation controls that use this information to allow users to navigate the site.

Security and Membership

ASP.NET 2.0 added several security-related features, including automatic support for storing user credentials, a role-based authorization system, and out-of-the-box controls for typical security tasks such as logging in, registering, and recovering a forgotten password.

Data source controls

The Data Source Controls model allows you to define how a page interacts with a data source in a declarative way in the markup, rather than by manually writing data access code. Best of all, this tool doesn’t force you to abandon a convenient component-based design solution: linking to a dedicated data component is as easy as linking directly to a database.

Web Parts

One of the most common types of web applications is the portal, which provides centralized placement of various information using individual panels on a single web page. Web Parts provide a ready-made platform for creating a portal with a floating layout, configurable views and even drag-and-drop support.

Profiles

Profiles allow you to store user-relevant information in a database without writing special code. Instead, ASP.NET takes care of all the time-consuming work of retrieving profile data when needed and saving it in case of any changes.

The post ASP.NET 2.0 appeared first on Host4ASP.

When a browser requests a particular page, ASP.NET first creates an object for the page itself, and then for all the other ASP NET controls that are present within it. The page and its controls then go through a series of lifecycle events, after which – when the page processing is complete – they render the final HTML and are deleted from memory. For the most part, ASP.NET programming is responsible for everything that happens in between.

The post ASP.NET 1.0 and 1.1 appeared first on Host4ASP.

This resulted in a number of amazingly advanced technologies for doing everything from building Windows applications to querying databases, and a specifically focused web development tool called ASP.NET.

Today ASP.NET enjoys unprecedented popularity, but is no longer a particularly revolutionary technology. And although the basic functionality underlying ASP.NET, surprisingly, looks exactly the same as ten years ago, the developers from Microsoft have added to them some more additional tools and abstractions of higher-level coding.

There is also at least one new direction, which is in competition with traditional ASP.NET programming, called ASP.NET MVC.

When ASP.NET was first released, there were seven key facts that set it apart from previous Microsoft products and competing platforms. For those who have switched to ASP.NET from some other web application development platform, or who have never yet programmed in .NET web applications, the material in the following sections will provide a quick overview of ASP.NET.

ASP.NET integrates with the .NET Framework
The .NET Framework is divided into an almost unrepeatable series of functional parts with tens of thousands of types (in .NET this is what classes, structures, interfaces, and other key programming elements are called). Before attempting to program any .NET application, you must first get at least a basic understanding of these parts and why they are organized in this way and not in any other way.

The way that the extensive collection of functionality offered in the .NET Framework is organized will undoubtedly seem like a remarkable improvement to programmers of traditional Windows applications. Each of the thousands of classes available in the .NET Framework is housed in a logical hierarchical container called a namespace.

Different namespaces provide different functionality, but together they offer functionality for virtually every aspect of distributed development, from message queuing to security. The whole of this vast set of tools is called a class library.

Interestingly, the way in which the .NET Framework classes can be used in ASP.NET is no different from the way they are used in any other type of .NET application (including standalone Windows applications, Windows services, command line utilities, etc.).

Although in .NET offers specifically for Windows- and Web-oriented classes to build user interfaces, most features of the .NET Framework (starting with accessing databases and uploading multi-threaded processing) is allowed to use in applications of any type. In other words, .NET offers the same tools to web application developers as it does to developers of feature-rich client applications.

ASP.NET code is compiled, not interpreted
Like all .NET applications, ASP.NET applications are always compiled. In fact, executing C# or Visual Basic code without precompilation is simply not possible.

ASP.NET applications actually go through two stages of compilation.

In the first stage, code written in C# is compiled into code in an intermediate language called MSIL (Microsoft Intermediate Language), or simply IL. This first step is precisely one of the main reasons why a wide variety of languages can be used in .NET.

The fact is that all .NET languages (including C#, Visual Basic and many others) are essentially compiled into virtually identical IL code. This first compilation step can either happen automatically when the page is first requested, or it can be done beforehand (this is called precompilation). The compiled IL code file is an assembly.

The second stage of compilation takes place just before the actual execution of the page. In this stage, the IL code is compiled into low-level machine language code. This stage is called Just-In-Time (JIT) compilation and looks the same for all .NET applications (including, for example, Windows applications).

The post Features of ASP.NET appeared first on Host4ASP.