Asp.net Tutorials
21. Introduction to the AWS SDK for .NET
By: Emiley J : 2023-05-03
Description: The AWS .NET SDK is a single, downloadable package that includes Visual Studio project templates, the AWS .NET library, C# code samples, and documentation. The AWS .NET SDK makes it easier for Windows developers to build .NET applications that tap into the cost-effective, scalable, and reliable AWS infrastructure services such as Amazon S3, EC2, and SimpleDB.
22. Enabling IIS 7.0 with ASP.NET
By: Emiley J : 2010-08-13
Description: The following instructions enable IIS 7.0 with ASP.NET.
23. IsPostBack in ASP.net
By: Dan Hurwitz and Jesse Liberty : 2009-02-27
Description: The page exposes the IsPostBack property. This is a read-only Boolean property that indicates if the page or control is being loaded for the first time, or if it is being loaded in response to a client postback. Many expensive operations (such as getting data from a database or populating ListItems) must be performed only the first time the page or control is loaded. If the page is posted to the server and then reloaded, there is no need to repeat the operation. By testing the value of IsPostBack, you can skip the expensive operation, as in the code snippets in Example 1 and Example 2.
24. ASP Versus ASP.NET Events
By: Dan Hurwitz and Jesse Liberty : 2009-02-27
Description: ASP was primarily a linear programming model. It had six events, of which only four were commonly used. ASP.NET, on the other hand, is primarily an event-driven programming model. The application has events, each session has events, and the page and most of the server controls can also raise events. All ASP.NET events are handled on the server. Some events cause an immediate posting to the server, while other events are simply stored until the next time the page is posted back to the server.
25. What is Code-Behind in ASP.net
By: Dan Hurwitz and Jesse Liberty : 2009-02-27
Description: In traditional ASP, the interweaving of script with HTML can produce source control nightmares and difficult-to-maintain ASP pages. ASP.NET addresses this problem by giving programmers the ability to separate the executable code from the presentation code. You write the HTML in a page file (with a .aspx extension), and you write the C# or VB.NET code in he code-behind file (with a .cs or .vb extension, depending on its language), which is another way of saying the "code file behind the form."
26. Lifecycle of a web form in ASP.net
By: Dan Hurwitz and Jesse Liberty : 2009-02-27
Description: A user sits at her browser and types in a URL. A web page appears, with text and images and buttons and so forth. She fills in a text box and clicks on a button. What is going on behind the scenes?
27. Directives in ASP.net
By: Dan Hurwitz and Jesse Liberty : 2009-02-27
Description: Directives are typically located at the top of the appropriate file, although that is not a strict requirement. For example, Application directives are at the top of the global.asax file, and Page directives are at the top of the .aspx files.
28. DataGrid Control in ASP.net
By: Dan Hurwitz and Jesse Liberty : 2009-02-27
Description: The problem with predesigned user controls is typically that they are either simple and therefore too limited to do what you want, or they are powerful and therefore so complex that they are very difficult to learn. The DataGrid control attempts to overcome both of these constraints. Creating a simple DataGrid control couldn't be much easier, yet there is enough power and complexity to keep you quite busy tweaking and modifying the control to do exactly what you want.
29. Advantages of Stored Procedures
By: John Kauffman : 2008-12-01
Description: This article discusses what gives stored procedures their important role in serious database-driven applications. These are the many advantages that stored procedures provide
30. Event Driven Programming in ASP.net
By: Emiley J. : 2008-11-27
Description: Event-driven programming responds to events. An event is generated (or raised) when "something happens," such as the user pressing a button. Often, events are generated by user action, but events can also be generated by the system starting or finishing work. For example, the system might raise an event when a file that you open for reading has been read into memory or when your battery's power is running low.