As well as the switch to a unified control architecture, there are other changes to the range of controls provided with version 2.0 of ASP.NET. There are changes to many of the existing controls, which we'll examine later in this chapter, plus a whole range of new controls. We don't have room in this book to fully detail every control, and it's possible that the interfaces may change as ASP.NET moves from the current Technology Preview to a release version. However, we will discuss and demonstrate the important features of each controlstarting with a summary of all the new controls. This section summarizes all the controls that are either completely new or substantially updated. We've divided them into six groups:
Standard Form- and Page-Based ControlsSeveral new controls are "standard" elements for use in a Web page, including some that generate elements for use in a <form> section.
We look at these controls in more detail later in this chapter. For the Technology Preview release of ASP.NET this won't be the final story because more controls will be added during the beta phasebut these haven't been written, so we can't cover them yet! Rich ControlsASP.NET 1.x contained several rich controls, and these proved to be a big hit with developers. We define a rich control as one that generates multiple different elements, and often client-side code as well, so as to create whole sections of UI or to provide features not supported by ordinary single HTML (or other) elements. A good example is the Calendar control, which generates a whole month of clickable dates and has navigation built in to scroll to other months. In ASP.NET 2.0, there are a few new rich controls included in the Technology Preview of the Framework, and several others are planned for beta releases and the final release. The controls that are implemented now are listed below.
The Wizard control was covered in Chapter 9. The other controls listed above will be covered later in this chapter. Login and Authentication ControlsASP.NET introduced built-in authentication and access control features as part of the Framework. In ASP.NET 2.0, the way that you interact with the classes exposed by the Framework when creating secured pages or folders is much simpler. Instead of writing code, you can use the new login controls.
The login controls were covered in detail in Chapter 6. Navigation Controls and CountersOne area where there is no real support for developers in ASP.NET 1.x is when building effective navigation systems for a Web site or application. In ASP.NET 2.0, several new controls make it easier to build menus and other types of site navigation UI, as well as adding support for recording the number of times that users click on specific links or visit specific pages. The new or updated controls are listed below.
The SiteMapPath and TreeView controls were covered in detail in Chapter 5. The other controls listed above will be covered later in this chapter. Data ControlsOne of the major changes in the way pages that use separate sources of data are created in ASP.NET 2.0 is the provision of data source controls . This concept was originally pioneered in Web Matrix, which contained a simple data source control that makes server-side data binding much easier to achieve. Web Matrix also included a new type of grid control, designed to make it easier to display the data exposed by a data source control. There are several data source controls included in the Technology Preview version of ASP.NET 2.0, with more on the way for the final release version, plus a great new "grid" control. The controls provided with the Technology Preview version are listed below.
The data controls were covered in detail in Chapters 3 and 4. Mobile Device ControlsSupport for different types of client devices is now integrated into the Page framework and all the controls from the System.Web.UI.WebControls namespace. However, some new controls are primarily aimed at particular types of devices, such as cellular phones.
The mobile device controls were covered in Chapter 10. You'll see that some features of the controls we describe in this chapter are also particularly useful when the client is a small-screen device such as a cellular phone. |