- •Contents
- •Introduction
- •Acknowledgments
- •The Goals of ASP.NET 2.0
- •Developer productivity
- •Administration and management
- •Performance and scalability
- •Device-specific code generation
- •Additional New Features of ASP.NET 2.0
- •New developer infrastructures
- •New compilation system
- •Additions to the page framework
- •New objects for accessing data
- •New server controls
- •A New IDE for Building ASP.NET 2.0 Pages
- •The Document Window
- •Views in the Document Window
- •The tag navigator
- •Page tabs
- •Code change status notifications
- •Error notifications and assistance
- •The Toolbox
- •The Solution Explorer
- •Lost Windows
- •Other Common Visual Studio Activities
- •Creating new projects
- •Making references to other objects
- •Using smart tags
- •Saving and importing Visual Studio settings
- •Application Location Options
- •Built-in Web server
- •Web site requiring FrontPage Extensions
- •The ASP.NET Page Structure Options
- •Inline coding
- •New code-behind model
- •New Page Directives
- •New attributes
- •New directives
- •New Page Events
- •Cross-Page Posting
- •New Application Folders
- •\Code folder
- •\Themes folder
- •\Resources folder
- •Compilation
- •The New Data Source Controls
- •The SqlDataSource and GridView Controls
- •Reading data
- •Applying paging in the GridView
- •Sorting rows in the GridView control
- •Defining bound columns in the GridView control
- •Enabling the editing of rows in the GridView control
- •Deleting data from the GridView
- •Dealing with other column types in the GridView
- •Selecting which fields to display in the DetailsView control
- •Using the GridView and DetailsView together
- •Updating, inserting, and deleting rows
- •XmlDataSource Control
- •ObjectDataSource Control
- •SiteMapDataSource Control
- •DataSetDataSource Control
- •Visual Studio 2005
- •Connection Strings
- •Site Maps
- •The PathSeparator property
- •The PathDirection property
- •The ParentLevelsDisplayed property
- •The ShowToolTips property
- •Examining the parts of the TreeView control
- •Binding the TreeView control to an XML file
- •Selecting multiple options in a TreeView
- •Specifying custom icons in the TreeView control
- •Specifying lines used to connect nodes
- •Working with the TreeView control programmatically
- •Applying different styles to the Menu control
- •Menu Events
- •Binding the Menu control to an XML file
- •SiteMap Data Provider
- •SiteMapViewType
- •StartingNodeType
- •SiteMap API
- •Why Do You Need Master Pages?
- •The Basics of Master Pages
- •Coding a Master Page
- •Coding a Content Page
- •Mixing page types and languages
- •Specifying which master page to use
- •Working with the page title
- •Working with controls and properties from the master page
- •Nesting Master Pages
- •Container-Specific Master Pages
- •Event Ordering
- •Caching with Master Pages
- •Using ASP.NET 2.0 Packaged Themes
- •Applying a theme to a single ASP.NET page
- •Applying a theme to an entire application
- •Applying a theme to all applications on a server
- •Removing themes from server controls
- •Removing themes from Web pages
- •Removing themes from applications
- •Creating Your Own Themes
- •Creating the proper folder structure
- •Creating a skin
- •Including CSS files in your themes
- •Having your themes include images
- •Defining Multiple Skin Options
- •Programmatically Working with Themes
- •Themes and Custom Controls
- •Authentication
- •Authorization
- •ASP.NET 2.0 Authentication
- •Setting up your Web site for membership
- •Adding users
- •Asking for credentials
- •Working with authenticated users
- •Showing the number of users online
- •Dealing with passwords
- •ASP.NET 2.0 Authorization
- •Using the LoginView server control
- •Setting up your Web site for role management
- •Adding and retrieving application roles
- •Deleting roles
- •Adding users to roles
- •Getting all the users of a particular role
- •Getting all the roles of a particular user
- •Removing users from roles
- •Checking users in roles
- •Using the Web Site Administration Tool
- •The Personalization Model
- •Adding a simple personalization property
- •Using personalization properties
- •Adding a group of personalization properties
- •Using grouped personalization properties
- •Defining types for personalization properties
- •Using custom types
- •Providing default values
- •Making personalization properties read-only
- •Anonymous Personalization
- •Enabling anonymous identification of the end user
- •Working with anonymous identification events
- •Anonymous options for personalization properties
- •Migrating Anonymous Users
- •Personalization Providers
- •Working with the Access personalization provider
- •Working with the SQL Server personalization provider
- •Using multiple providers
- •Building Dynamic and Modular Web Sites
- •Introducing the WebPartManager control
- •Working with zone layouts
- •Understanding the WebPartZone control
- •Explaining the WebPartPageMenu control
- •Modifying zones
- •Caching in ASP.NET 1.0/1.1
- •Output caching
- •Partial page caching
- •Data caching using the Cache object
- •Cache dependencies
- •ASP.NET 2.0 unseals the CacheDependency class
- •Enabling databases for SQL Server cache invalidation
- •Enabling tables for SQL Server cache invalidation
- •Looking at SQL Server
- •Looking at the tables that are enabled
- •Disabling a table for SQL Server cache invalidation
- •Disabling a database for SQL Server cache invalidation
- •Configuring your ASP.NET Application
- •Adding more than one table to a page
- •Attaching SQL Server cache dependencies to the Request object
- •Attaching SQL Server cache dependencies to the Cache object
- •Customizing the side navigation
- •Examining the AllowReturn attribute
- •Working with the StepType attribute
- •Adding a header to the Wizard control
- •Utilizing Wizard control events
- •Working with images from disk
- •Resizing images
- •Displaying images from streams
- •The MMC ASP.NET Snap-In
- •General
- •Custom Errors
- •Authorization
- •Authentication
- •Application
- •State Management
- •Advanced
- •ASP.NET Web Site Administration Tool
- •Home
- •Security
- •Profile
- •Application
- •Provider
- •Managing the Site Counter System
- •Generics
- •Iterators
- •Anonymous Methods
- •Operator Overloading
- •Visual Basic XML Documentation
- •New Visual Basic Keywords
- •Continue
- •Using
- •Global
- •Index
Personalization
the AnonymousID property is changed within the AnonymousIdentification_OnCreate event to
Bubbles 6/10/2004 2:07:33 PM
The AnonymousIdentification_OnRemove event also employs an event delegate of type Anonymous IdentificationEventArgs that is used immediately prior to migrating anonymous users to registered users. Note that the AnonymousId property of the Request object is still accessible at this point.
Anonymous options for personalization properties
Now that the capability to work with anonymous users is in place, you have to specify which personalization properties you want to enable for anonymous users. This is also done through the web.config file by adding the allowAnonymous attribute to the <add> element (see Listing 9-14).
Listing 9-14: Turning on anonymous capabilities personalization properties
<properties>
<add name=”FirstName” type=”System.String” /> <add name=”LastName” type=”System.String” />
<add name=”LastVisited” type=”System.DateTime” allowAnonymous=”true” /> <add name=”Age” type=”System.Integer” />
<add name=”Member” type=”System.Boolean” />
</properties>
In this example, the LastVisited property is set to allow anonymous users by setting the allow Anonymous attribute to True. Because this is the only property that works with anonymous users, the rest of the defined properties do not store information for these types of users.
Migrating Anonymous Users
When working with anonymous users, you must be able to migrate anonymous users to registered users. For instance, after an end user fills a shopping cart, she can then register on the site to purchase the items. At this moment, she switches from an anonymous user to a registered user.
For this reason, ASP.NET 2.0 provides a Profile_MigrateAnonymous event enabling you to migrate anonymous users to registered users. The Profile_MigrateAnonymous event requires an event delegate of type ProfileMigrateEventArgs. It is placed either in the page that deals with the migration or within the Global.asax file (if it can be used from anywhere within the application). The use of this event is illustrated in Listing 9-15.
Listing 9-15: Migrating anonymous users for particular personalization properties
VB
Public Sub Profile_MigrateAnonymous(ByVal sender As Object, _
ByVal e As ProfileMigrateEventArgs)
(continued)
279
Chapter 9
Listing 9-15: (continued)
Profile.LastVisited = Profile.GetPropertyValue(e.AnonymousId).LastVisited
End Sub
C#
public void Profile_MigrateAnonymous(object sender, ProfileMigrateEventArgs e)
{
Profile.LastVisited = Profile.GetPropertyValue(e.AnonymousId).LastVisited;
}
From this example, you populate the new Profile property with the old property. You get at the old property of the anonymous user by using the GetPropertyValue property, which takes a parameter of the ID of the anonymous user. From the Profile_MigrateAnonymous event, you still have access to the AnonymousId property, which you can retrieve from the event delegate — ProfileMigrateEventArgs.
Listing 9-15 shows how to migrate a single personalization property from an anonymous user to the new registered user. In addition to migrating single properties, you also must migrate properties that come from personalization groups. This is shown in Listing 9-16.
Listing 9-16: Migrating anonymous users for items in personalization groups
VB
Public Sub Profile_MigrateAnonymous(ByVal sender As Object, _
ByVal e As ProfileMigrateEventArgs)
Dim au As HttpProfile = Profile.GetProfile(e.AnonymousId)
If au.MemberDetails.DateJoined <> “” Then Profile.MemberDetails.DateJoined = DateTime.Now().ToString() Profile.FamilyDetails.MarriedStatus = au.FamilyDetails.MarriedStatus
End If
End Sub
C#
public void Profile_MigrateAnonymous(object sender, ProfileMigrateEventArgs e)
{
HttpProfile au = Profile.GetProfile(e.AnonymousId);
if (au.MemberDetails.DateJoined != String.Empty) { Profile.MemberDetails.DateJoined = DateTime.Now.ToString(); Profile.FamilyDetails.MarriedStatus = au.FamilyDetails.MarriedStatus;
}
}
Using this event either in the page or in the Global.asax file enables you to logically migrate anonymous users as they register themselves with your applications. The migration process also allows you to pick and choose which items you migrate and to change the values as you wish.
280
