Geeks With Blogs
Geekette Mai Blog July 2006 Entries
Display Record's Description Through AJAX
Description: This customization utilizes the power of AJAX to make asynchronous calls to server-side methods. The server-side methods then call back a JavaScript function to display data in a popup window. The code customization for .NET Framework 2.0 uses the Microsoft Atlas library. For .NET Framework 1.1, the AJAXPro (available free) third-party DLL is used. Procedure: Step 1: Call JavaScript function on MouseOver Define an area that the user can mouse over to see the popup data. When the user ......

Posted On Friday, July 21, 2006 2:48 PM

Application Security
Built-in security features critical for today's enterprise applications Although most corporations take security precautions at the network level, the majority of application security must be built into the application itself. Several important application security features including role-based access control, automatic sign-out, and database-resident password storage. Role-based access control You can automatically add end-user authentication (sign-in) and role-based access control as a standard ......

Posted On Thursday, July 20, 2006 9:10 PM

Application Customization and Integration
Extensible C# and Visual Basic .NET classes Code generated by Iron Speed Designer is designed to be customized and then regenerated repeatedly without reapplying your code customizations. This is accomplished by a class hierarchy designed for code customization that is not affected when rebuilding your application. Easy to Customize Code Simply subclass the appropriate page, control or database class. Your code extensions are preserved when code files are regenerated, allowing you a high degree of ......

Posted On Thursday, July 20, 2006 8:48 PM

Referencing Data Access Functions in Code
Creates two classes for each table in your database. The Record classes represent a record from the database. Some of the record classes specify an actual physical record in the database while others correspond to a virtual record – the result of a join between tables. A “Record” suffix is added to the name of the table to get the name of the class. For example, if you have a Customers table in your database, the class will be called CustomersRecord. The record class is different from the record ......

Posted On Thursday, July 20, 2006 8:43 PM

Saving Data to the Database
In the above sections we have discussed the lifecycle of retrieving and displaying data on a web page. There is an analogous life cycle the page goes through to retrieve the data from the user interface controls into memory and subsequently save this data in the database. The data is retrieved into memory from each of the user interface controls and validated. The retrieved data is stored in an instance of the data access layer’s Record class. The data from the page is retrieved within the record ......

Posted On Thursday, July 20, 2006 8:41 PM

Table Control and Record Control Lifecycle
The Table Control and Record Control are user interface controls and have a lifecycle of their own, just like the lifecycle of each of the controls on a page. It is important to understand the lifecycle of the table and record control classes since the page delegates the responsibility of reading the data from the database and retrieving and validating the data from the user interface prior to saving it in the database. The query used to read data from the database is a composite query that is formed ......

Posted On Thursday, July 20, 2006 8:40 PM

Page Code Customization Model
There are four types of classes that are generated. Page code-behind class The page’s code-behind class is derived from the Microsoft .NET Framework’s page class. This class contains event handlers and methods that load the data from the database, display the data in user interface controls and save the updated data back into the database. The page class event handlers and methods call on some of the other classes to actually perform the specific task. Most of the code customization should be performed ......

Posted On Thursday, July 20, 2006 8:38 PM

Page Control Hierarchy
All web pages in Microsoft .NET Framework contain a number of user interface controls that are initialized at the server side and are called server controls. Since server controls can have children, and each of their children may have children, and so on, a control and its descendents form a tree of controls. This tree of controls is called the control hierarchy. The root of the control hierarchy for a .NET web page is the Page-derived class. Iron Speed Designer generates a hierarchy of controls ......

Posted On Thursday, July 20, 2006 8:34 PM

The Page Lifecycle
Creates standard web pages that are derived from the ASP.NET Page class. When an ASP.NET web page is requested from the web server, the code-behind class for the page goes through a sequence of steps to initialize and load the user interface controls, read the data from the database and display the page. This sequence of steps is called the page lifecycle as shown below: Initialization: During this stage the page and all of the controls within the page (control hierarchy) are instantiated. This includes ......

Posted On Thursday, July 20, 2006 8:32 PM

What is Atlas?
What is Atlas? The Atlas features of ASP.NET are not just another AJAX script library for writing client-centric Web applications. Atlas builds on the .NET Framework 2.0 and adds support for better utilizing the capabilities of client-side JavaScript and the XMLHttpRequest object. It includes server-based features that make it easy to enrich existing ASP.NET applications, as well as a client script library that is used by the Atlas controls and services. The architecture diagram in Figure 1 shows ......

Posted On Friday, July 14, 2006 10:15 AM

Copyright © Mai Nguyen | Powered by: GeeksWithBlogs.net