ASP.NET C# | ASP.NET C# TUTORIAL | ASP.NET using C# | C# TUTORIALS

Frameworks

It is not essential to use the standard webforms development model when developing with ASP.NET. Noteworthy frameworks designed for the platform include:

• Base One Foundation Component Library (BFC) is a RAD framework for building .NET database and distributed computing applications.
• DotNetNuke is an open-source solution which comprises both a web application framework and a content management system which allows for advanced extensibility through modules, skins, and providers.
• Castle Monorail, an open-source MVC framework with an execution model similar to Ruby on Rails. The framework is commonly used with Castle ActiveRecord, an ORM layer built on NHibernate.
• Spring.NET, a port of the Spring framework for Java.
• Skaffold.NET, A simple framework for .NET applications, used in enterprise applications.

Versions

The ASP.NET releases history tightly correlates with the .NET Framework releases:

Date	Version	Remarks	New ASP.NET related features
January 16, 2002	1.0	First version released together with Visual Studio .NET	Object-oriented web application development supporting inheritance, polymorphism and other standard OOP features Developers are no longer forced to use Server.CreateObject(...), so early-binding and type safety are possible. Based on Windows programming; the developer can make use of DLL class libraries and other features of the web server to build more robust applications that do more than simply rendering HTML (e.g. exception handling)
April 24, 2003	1.1	released together with Windows Server 2003 released together with Visual Studio .NET 2003	Mobile controls Automatic input validation
November 7, 2005	2.0	codename Whidbey released together with Visual Studio 2005and Visual Web Developer Express and SQL Server 2005	New data controls (GridView, FormView, DetailsView) New technique for declarative data access (SqlDataSource, ObjectDataSource, XmlDataSource controls) Navigation controls Master pages Login controls Themes Skins Web parts Personalization services Full pre-compilation New localization technique Support for 64-bit processors Provider class model
November 21, 2006	3.0		Windows Presentation Foundation (WPF) Windows Workflow Foundation (WF) Windows Communication Foundation which can use ASP.NET to host services. Windows CardSpace which uses ASP.NET for login roles.
November 19, 2007	3.5	Released with Visual Studio 2008 andWindows Server 2008	New data controls (ListView, DataPager) ASP.NET AJAX included as part of the framework Support for HTTP pipelining and syndication feeds. WCF Support for RSS, JSON, POX and Partial Trust All the .NET Framework 3.5 changes, like LINQ etc.
August 11, 2008	3.5 Service Pack 1	Released with Visual Studio 2008 Service Pack 1	Incorporation of ASP.NET Dynamic Data Support for controlling browser history in an ASP.NET AJAX application Ability to combine multiple JavaScript files into one file for more efficient downloading New namespaces System.Web.Abstractions and System.Web.Routing
April 12, 2010	4.0	Parallel extensions and other .NET Framework 4 features

CONTENT FROM WIKIPEDIA OFFERED UNDER GNU FREE DOCUMENTATION LICENSE

ASP.NET C# | ASP.NET C# TUTORIAL | ASP.NET using C# | C# TUTORIALS

Criticism

On IIS 6.0 and lower, pages written using different versions of the ASP framework cannot share Session State without the use of third-party libraries. This criticism does not apply to ASP.NET and ASP applications running side by side on IIS 7. With IIS 7, modules may be run in an integrated pipeline that allows modules written in any language to be executed for any request.

Development tools

Several available software packages exist for developing ASP.NET applications:

Product	Developer	Licensing
ASP.NET Intellisense Generator	BlueVision LLC	Free
Microsoft Visual Studio	Microsoft	Free and commercial
CodeGear Delphi	Embarcadero Technologies	Commercial
Macromedia HomeSite	Adobe Systems	Commercial
Microsoft Expression Web	Microsoft	Commercial
Microsoft SharePoint Designer	Microsoft	Free
MonoDevelop	Novell and the Mono community	Free open source
SharpDevelop	ICSharpCode Team	Free open source
Eiffel for ASP.NET	Eiffel Software	Free open source and commercial
Adobe Dreamweaver	Adobe Systems	Commercial

CONTENT FROM WIKIPEDIA OFFERED UNDER GNU FREE DOCUMENTATION LICENSE

ASP.NET C# | ASP.NET C# TUTORIAL | ASP.NET using C# | C# TUTORIALS

ASP.NET compared with ASP classic

ASP.NET simplifies developers' transition from Windows application development to web development by offering the ability to build pages composed of controls similar to a Windows user interface. A web control, such as a button or label, functions in very much the same way as its Windows counterpart: code can assign its properties and respond to its events. Controls know how to render themselves: whereas Windows controls draw themselves to the screen, web controls produce segments of HTML and JavaScript which form parts of the resulting page sent to the end-user's browser.

ASP.NET encourages the programmer to develop applications using an event-driven GUI model, rather than in conventional web-scripting environments like ASP and PHP. The framework combines existing technologies such as JavaScript with internal components like "ViewState" to bring persistent (inter-request) state to the inherently stateless web environment.

Other differences compared to ASP classic are:

• Compiled code means applications run faster with more design-time errors trapped at the development stage.
• Significantly improved run-time error handling, making use of exception handling using try-catch blocks.
• Similar metaphors to Microsoft Windows applications such as controls and events.
• An extensive set of controls and class libraries allows the rapid building of applications, plus user-defined controls allow commonly-used web template, such as menus. Layout of these controls on a page is easier because most of it can be done visually in most editors.
• ASP.NET uses the multi-language abilities of the .NET Common Language Runtime, allowing web pages to be coded in VB.NET, C#, J#, Delphi.NET, Chrome, etc.
• Ability to cache the whole page or just parts of it to improve performance.
• Ability to use the code-behind development model to separate business logic from presentation.
• Ability to use true object-oriented design for programming pages and controls
• If an ASP.NET application leaks memory, the ASP.NET runtime unloads the AppDomain hosting the erring application and reloads the application in a new AppDomain.
• Session state in ASP.NET can be saved in a Microsoft SQL Server database or in a separate process running on the same machine as the web server or on a different machine. That way session values are not lost when the web server is reset or the ASP.NET worker process is recycled.
• Versions of ASP.NET prior to 2.0 were criticized for their lack of standards compliance. The generated HTML and JavaScript sent to the client browser would not always validate against W3C/ECMA standards. In addition, the framework's browser detection feature sometimes incorrectly identified web browsers other than Microsoft's own Internet Explorer as "downlevel" and returned HTML/JavaScript to these clients with some of the features removed, or sometimes crippled or broken. However, in version 2.0, all controls generate valid HTML 4.0, XHTML 1.0 (the default) or XHTML 1.1 output, depending on the site configuration. Detection of standards-compliant web browsers is more robust and support for Cascading Style Sheets is more extensive.
• Web Server Controls: these are controls introduced by ASP.NET for providing the UI for the web form. These controls are state managed controls and are WYSIWYG controls.

• CONTENT FROM WIKIPEDIA OFFERED UNDER GNU FREE DOCUMENTATION LICENSE

ASP.NET C# | ASP.NET C# TUTORIAL | ASP.NET using C# | C# TUTORIALS

Extension

Microsoft has released some extension frameworks that plug into ASP.NET and extend its functionality. Some of them are:

ASP.NET AJAX

An extension with both client-side as well as server-side components for writing ASP.NET pages that incorporate AJAX functionality.

ASP.NET MVC Framework

An extension to author ASP.NET pages using the MVC architecture.

CONTENT FROM WIKIPEDIA OFFERED UNDER GNU FREE DOCUMENTATION LICENSE

ASP.NET C# | ASP.NET C# TUTORIAL | ASP.NET using C# | C# TUTORIALS

Performance

ASP.NET aims for performance benefits over other script-based technologies (including Classic ASP) by compiling the server-side code to one or more DLL files on the web server.^[18] This compilation happens automatically the first time a page is requested (which means the developer need not perform a separate compilation step for pages). This feature provides the ease of development offered by scripting languages with the performance benefits of a compiled binary. However, the compilation might cause a noticeable but short delay to the web user when the newly-edited page is first requested from the web server, but won't again unless the page requested is updated further.

The ASPX and other resource files are placed in a virtual host on an Internet Information Services server (or other compatible ASP.NET servers; see Other implementations, below). The first time a client requests a page, the .NET Framework parses and compiles the file(s) into a .NET assembly and sends the response; subsequent requests are served from the DLL files. By default ASP.NET will compile the entire site in batches of 1000 files upon first request. If the compilation delay is causing problems, the batch size or the compilation strategy may be tweaked.

Developers can also choose to pre-compile their "codebehind" files before deployment, using MS Visual Studio, eliminating the need for just-in-time compilation in a production environment. This also eliminates the need of having the source code on the web server.

Content from Wikipedia offered under GNU Free Documentation License