How to develop asp web applications
•Download as PPT, PDF•
2 likes•3,098 views
The document provides an overview of developing an ASP.NET web application, including an overview of the .NET framework, ASP.NET, creating ASP.NET web forms, adding event procedures, and validating user input. Key points covered include the architecture and components of .NET and ASP.NET, using server controls and maintaining their state, implementing code behind pages, handling events on the client and server side, and using ASP.NET validation controls.
![Developing an ASP.NET Web Application ,[object Object]](https://image.slidesharecdn.com/howtodevelopaspwebapplications-120224042145-phpapp02/85/How-to-develop-asp-web-applications-1-320.jpg)
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Similar to How to develop asp web applications
Similar to How to develop asp web applications (20)
Recently uploaded
Recently uploaded (20)
How to develop asp web applications
- 4. What is the .NET Framework? Developer Tools Clients User Experiences ASP.NET Web Applications XML Web Services Databases .NET Framework
- 6. The .NET Framework Components Win32 Common Language Runtime .NET Framework Class Library ADO.NET and XML XML Web Services User Interface Visual Basic C++ C# ASP.NET Perl Python … Message Queuing COM+ (Transactions, Partitions, Object Pooling) IIS WMI
- 12. ASP Web Application Architecture Presentation Tier Business Logic Tier Data Tier UI Pages (.htm) Graphic Files COM Objects Data Source ADO COM+ Services ASP Page (.asp)
- 13. ASP.NET Web Application Architecture Presentation Tier Business Logic Tier Data Tier Graphic Files UI Pages (.htm) XML Web Services (.asmx) User Controls (.ascx) Code-Behind File (.aspx.vb or .aspx.cs) Proxy ADO.NET .NET Objects Data Source COM+ Services COM Objects RCW Web Form (.aspx)
- 15. ASP.NET Runtime Compilation and Execution Native code C# Visual Basic .NET default.aspx Common Language Runtime HTML Which language? Visual Basic .NET compiler C# compiler MSIL JIT compiler
- 16. Multimedia: ASP.NET Execution Model
- 17. Creating an ASP.NET Web Form
- 24. Selecting the Appropriate Control You need specific functionality such as a calendar or ad rotator The control will interact with client and server script You are writing a page that might be used by a variety of browsers You are working with existing HTML pages and want to quickly add ASP.NET Web page functionality You prefer a Visual Basic-like programming model You prefer an HTML-like object model Use Web Server Controls if: Use HTML Server Controls if: Bandwidth is not a problem Bandwidth is limited
- 34. Multimedia
- 35. Demonstration: Handling Postback Events
- 39. ASP.NET Validation Controls Control Name Purpose RequiredFieldValidator Require user input CompareValidator Compare to another control, a value, or a data type RangeValidator Compare to a range CustomValidator Compare to a custom formula RegularExpressionValidator Compare to a regular expression pattern ValidationSummary Summarize the state of the validation controls on a page
- 43. Thanks!
Editor's Notes
- RCW is the runtime callable wrapper, handles the interface between ASP.NET code and the unmanaged COM object
- <<may get rid of this one>>
- Derived from the Page class: Every .aspx page derives from the Page class and inherits all of the methods and properties that the Page class exposes. The @ Page directive defines the page-specific attributed that is used by the ASP.NET page parser and compiler when you build a page. When Visual Studio .NET creates the .aspx page file and the code-behind file for a Web Form, it generates a new class that inherits from the Page class. For example, if you create a new Web Forms page and name it WebForm1 , a new class named WebForm1 is derived from the Page class, as shown in the following code example: public class WebForm1 : System.Web.UI.Page Inheriting from the Page class not only makes all of the members of the Page class available to the code-behind file; it also allows ASP.NET to combine the code in the .aspx page file with the code in the code-behind file into a single compiled class at compile time. This single compiled class contains all of the methods and properties that are exposed by the Page class, as well as the methods and properties that are implemented by your code.