个性化定制 ASP.NET Whidbey外文翻译.docVIP

Get Personal with ASP.NET Whidbey Configure the Provider With both personalization and membership, the first step is configuring the provider that you will use to store the personalization or membership data. Though you can create the Microsoft Access or Microsoft SQL Server? database and add the necessary configuration elements manually, the easier way is to use the ASP.NET Web Site Administration tool, Note that to configure an application successfully, you must be logged in using an account with administrator rights (you also can launch Microsoft Visual Studio? .NET with an administrator-level account using Run As... and launch the Web Site Administration tool from the button in Solution Explorer). The ASP.NET Web Site Administration tool provides the means to configure personalization and membership features (the Membership data store is configured using the Security tab), as well as reports and data-access features. To create an Access .mdb file for storing personalization data, you need to open the Web Site Administration tool; the file, named AspNetDB.mdb, will be created automatically in a folder named DATA. Although not enabled in the build of Visual Studio against which this article was written, the Web Site Administration tool contains an entire section devoted to configuring personalization settings. In a later section, Ill walk you through adding the necessary configuration sections by hand. You configure the provider to use for membership services using the Security tab of the Web Site Administration tool. The easiest way to configure the membership provider is to select the Security Setup Wizard. Ill walk you through this process momentarily. At this point, the membership database will be created, and the necessary configuration elements will be added to the web.config file. All you need to do from here is add users to the database (which you can do using the Web Site Administration tool, or the membership APIs), set authorization restrictions on page