PeterKellner.net » Membership

Speaking Wednesday May 20th, 6:30PM, Microsoft Office San Francisco on ExtJS and ASP.NET Membership!

Peter Kellner — Tue, 21 Apr 2009 04:59:38 +0000

Come hear about how to see ExtJS integrated with ASP.NET for awesome Membership and Profile Management! I will speaking at the Microsoft Office at a meeting of Bay.Net Users Group.

http://www.baynetug.org/DesktopModules/DetailXEvents.aspx?ItemID=378&mid=49

ASP.NET: Membership with Profile and High Performance ExtJS JavaScript Interface

When:

Wednesday, 5/20/2009 at 6:30 PM

Where:

Microsoft Office, 835 Market Street, Suite 700, San Francisco

Event Description

In this session, we will demonstrate building a super rich JavaScript interface to the standard ASP.NET Membership and Profile services. That is, built into ASP.NET are wonderful providers that allow you to validate and store user credentials typically to a database. It also lets you store other information such as pictures, first and last names, as well as anything else you may want to store. In this session we will build a highly performing, 100% JavaScript UI to maintain hundreds of thousands of users. As part of this solution, techniques for using REST based services to access this information will be presented. Once you see this, it will be hard to ever use web forms again.

How to Set the Default Value of a DropDownList in an ASP.NET Page

Peter Kellner — Wed, 17 Oct 2007 17:44:13 +0000

(Using Membership ObjectDataSource From MSDN Article)

I’m doing a project where I have lots of DropDownList’s on a page and want a simple way to set the initial values based on some known value. The DropDownLists are retrieved using ObjectDataSource but I don’t want the first value displayed. I wrestled some with how to do this using page_load or page_prerender but didn’t come up with good solutions. I did finally
decide that programming the databound event of the dropdownlist was probably the best way to go.

The solution is pasted below. The MembershipUtilities.MembershipODS c# code can be downloaded from MSDN or on my web site at the following location.

http://peterkellner.net/2006/01/09/microsoft-aspnet-20-memberrole-management-with-iis/.

<%@ Page Language=”C#” %>
DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN”

  “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>

<script runat=”server”>
    protected void DropDownListUser_DataBound(object sender, EventArgs e)

    {
        DropDownListUser.SelectedIndex =
          DropDownListUser.Items.IndexOf
          (DropDownListUser.Items.FindByValue(Context.User.Identity.Name));
    }
script>
 
<html xmlns=”http://www.w3.org/1999/xhtml” >
<head runat=”server”>
    <title>DropDownList Initializetitle>
head>
<body>
    <form id=”form1″ runat=”server”>
    <div>
        <asp:DropDownList ID=”DropDownListUser” runat=”server”
          DataSourceID=”ObjectDataSourceUser”
          DataTextField=”UserName” DataValueField=”UserName”
          OnDataBound=”DropDownListUser_DataBound”>
        asp:DropDownList>
        <asp:ObjectDataSource ID=”ObjectDataSourceUser” runat=”server”
          SelectMethod=”GetMembers”
          TypeName=”MembershipUtilities.MembershipUserODS”>
            <SelectParameters>
                <asp:Parameter Name=”sortData” Type=”String” />
            SelectParameters>
        asp:ObjectDataSource>
    div>
    form>
body>
html>

Resetting Password with ASP.NET 2.0 Membership and Multiple Providers

Peter Kellner — Thu, 15 Feb 2007 15:39:16 +0000

If you ever have wanted to be able to programmatically change (reset) a users password while at the same time continuing to be able to use the question and answer feature, this post is for you. The problem is that if you use code like this:

 string username = "user";
 string password = "pass@word";
 MembershipUser mu = Membership.GetUser(username);
 mu.ChangePassword(mu.ResetPassword(), password);

You will find that if you have in your web.config requiresQuestionAnswer="true", you will get an error when you try and reset the password. The elegant solution to this is to create an additional membeship tag in your web.config and reference it when you change passwords. That is, add another provider like this:

<membership defaultProvider="SqlMembershipProvider" userIsOnlineTimeWindow="15">
<providers>
    <clear/>
    <add name="SqlMembershipProviderOther" type="SqlProviderOneShot.SqlMembershipProvider"
    requiresQuestionAndAnswer="false"
     connectionStringName="EmailEmailConnectionString" applicationName="EmailEmail"
    enablePasswordRetrieval="false" enablePasswordReset="true"
    requiresUniqueEmail="true" passwordFormat="Hashed"
    minRequiredNonalphanumericCharacters="0" writeExceptionsToEventLog="false"
    minRequiredPasswordLength="1" passwordStrengthRegularExpression=""
    passwordAttemptWindow="10" maxInvalidPasswordAttempts="8"/>
providers>
membership>

Then, when you change your password, reference it as follows:

string username = "user";
string password = "pass@word";
MembershipUser mu = Membership.Providers["SqlMembershipProviderOther"].GetUser(username);
mu.ChangePassword(mu.ResetPassword(), password);

Hope this helps! At some point, I will integrate this functionality into my ObjectDataSource article that lets you display your membership information with a gridview or detailsview.

Have GridView Highlight Last Inserted Record in ASP.NET 2.0

Peter Kellner — Thu, 07 Dec 2006 23:41:04 +0000

Introduction

A question that frequently comes up in the asp.net forums is how to have a gridview show the the last record added highlighted. This articles gives a technique for doing this. It only works with SqlServer but could could be modified for other databases.

What It Looks Like Running

After pressing the insert button on the screen shot below, the bottom line was actually added and it is automatically highlighted. This is in a nutshell, what the code listed below and this article discusses.

The Code

In order to run the code below, you must first set up Membership. The simplest way to do this is to simply add to your web.config a very small section enabling RoleManager. This will automatically create the membership database in sqlexpress. You should probably add a couple users just so your gridview is not empty from the start. The code you need to add to an empty asp.net 2.0 web site project is as follows (put it in the section).

<roleManager enabled="true">roleManager> 

Once you have done that, you can copy the code below to a new web page and simply run it.

Briefly, the way the code works is that when a row is inserted into the database the sqldatasource’s Inserted event is called. In this event, we take a look at the return parameter which comes from the sql:

InsertCommand="INSERT INTO [Names] ([name]) VALUES (@name);SELECT @NewID = Scope_Identity()"

NewId is actually a return parameter, so we can get that back in the inserted event. Once we get the value back, we store it in viewstate so that on the upcoming page_prerender, we can check and see which row has that id in it, and then highlight that row. The reason we do it in prerender and not load is because the inserted event is processed after load and it would not work if we put it there.

So, here is the code! Good luck.

<%@ Page Language=”C#” %>

DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>

<script runat=”server”>

    // simple table named: Names. Two columns:  id int, name varchar(64)

    protected void ButtonInsert_Click(object sender, EventArgs e)
    {      
        SqlDataSource1.InsertParameters["name"].DefaultValue = DateTime.Now.ToString();
        int numInserted = SqlDataSource1.Insert();
        GridView1.DataBind();
    }

    protected void SqlDataSource1_Inserted(object sender, SqlDataSourceStatusEventArgs e)
    {
        object newId = e.Command.Parameters["@NewId"].Value;
        ViewState["NewId"] = Convert.ToInt32(newId);
    }

    protected void Page_PreRender(object sender, EventArgs e)
    {
        string newIdLast = string.Empty;
        if (ViewState["NewId"] != null)
        {
            int newId = (int)ViewState["NewId"];
            newIdLast = newId.ToString();
            int rowCnt = 0;
            foreach (GridViewRow row in GridView1.Rows)
            {
               string newIdText = row.Cells[1].Text;
                if (newIdText.Equals(newIdLast))
                {
                    //GridView1.EditIndex = rowCnt;
                    //GridView1.SelectedIndex = rowCnt;
                    row.Attributes.Add(“bgcolor”, “Gray”);
                    break;
                }
                rowCnt++;
            }
        }
    }
script>

<html xmlns=”http://www.w3.org/1999/xhtml” >
<head id=”Head1? runat=”server”>
    <title>Untitled Pagetitle>
head>
<body>
    <form id=”form1? runat=”server”>
    <div>
    <h2>Example of GridView that shows highlighted last inserted rowh2>
        <br />
        <asp:GridView ID=”GridView1? runat=”server” AutoGenerateColumns=”False” DataKeyNames=”id” DataSourceID=”SqlDataSource1? >
            <Columns>
                <asp:CommandField ShowEditButton=”True” ShowDeleteButton=”True” />
                <asp:BoundField DataField=”id” HeaderText=”id” InsertVisible=”False” ReadOnly=”True”
                    SortExpression=”id” />
                <asp:BoundField DataField=”name” HeaderText=”name” SortExpression=”name” />
            Columns>
        asp:GridView>
        <asp:SqlDataSource ID=”SqlDataSource1? runat=”server” ConnectionString=”&lt;%$ ConnectionStrings:ConnectionString %&gt;“
          DeleteCommand=”DELETE FROM [Names] WHERE [id] = @id”
          InsertCommand=”INSERT INTO [Names] ([name]) VALUES (@name);SELECT @NewID = Scope_Identity()”

          SelectCommand=”SELECT [id], [name] FROM [Names]“ UpdateCommand=”UPDATE [Names] SET [name] = @name WHERE [id] = @id” OnInserted=”SqlDataSource1_Inserted”>
            <DeleteParameters>
                <asp:Parameter Name=”id” Type=”Int32? />
            DeleteParameters>
            <UpdateParameters>
                <asp:Parameter Name=”name” Type=”String” />
                <asp:Parameter Name=”id” Type=”Int32? />
            UpdateParameters>
            <InsertParameters>
                <asp:Parameter Name=”name” Type=”String” />
               <asp:Parameter Direction=Output Name=”NewId” Size=4 Type=Int16 />
            InsertParameters>
        asp:SqlDataSource>
        <br />
        <br />
         <asp:Button ID=”ButtonInsert” runat=”server” OnClick=”ButtonInsert_Click” Text=”Insert Record” />div>
    form>
body>
html>

About the Author

Peter Kellner currently works as an asp.net enterprise consultant at http://www.73rdstreet.com. During the past year, Peter Kellner has authored four MSDN articles dealing with Membership and Profiles. He maintains a blog with more articles at http://peterkellner.net.

Moving From Casini to IIS, Login Fails. How come?

Peter Kellner — Fri, 20 Oct 2006 17:33:09 +0000

ASP.NET 2.0 Membership

A very common question that comes up while using ASP.NET 2.0 Membership is that when moving a web application from the local developer environment with Visual Studio 2005 (VS2005) to IIS is that login no longer works. Almost everytime this happens, it comes down to the application name in the Membership Profile of Web.Config is set to / instead of the actual application name. That is, if you you were to look at your web.config, this is what you would see.

<roleManager enabled=“true“/>

     <membership>

          <providers>

          <remove name=“AspNetSqlMembershipProvider“/>

          <add name=“AspNetSqlMembershipProvider“

               type=“…“

               connectionStringName=“LocalSqlServer“

               enablePasswordRetrieval=“false“

               enablePasswordReset=“true“

               requiresQuestionAndAnswer=“true“

               applicationName=“/“

               requiresUniqueEmail=“false“

               minRequiredPasswordLength=“1“

               minRequiredNonalphanumericCharacters=“0“

               passwordFormat=“Hashed“

               maxInvalidPasswordAttempts=“5“

               passwordAttemptWindow=“10“ p=“”

               asswordStrengthRegularExpression=“”/>

     providers>

membership>

Notice that the applicationName is set to just a "/". To make the application work with IIS, you really need to set that to the name of your application. That is, the correct way to specify applicationName is something more like this:

<roleManager enabled=“true“/>

    <membership>

        <providers>

            <remove name=“AspNetSqlMembershipProvider“/>

            <add name=“AspNetSqlMembershipProvider“

                type=“…“

                connectionStringName=“LocalSqlServer“

                enablePasswordRetrieval=“false“

                enablePasswordReset=“true“

                requiresQuestionAndAnswer=“true“

                applicationName=“/MyCoolApp1“

                requiresUniqueEmail=“false“

                minRequiredPasswordLength=“1“

                minRequiredNonalphanumericCharacters=“0“

                passwordFormat=“Hashed“

                maxInvalidPasswordAttempts=“5“

                passwordAttemptWindow=“10“ p=“”

                asswordStrengthRegularExpression=“”/>

        providers>

    membership>

This also makes it so that you can share the same membership database across multiple applications.

Fourth MSDN Article Published! "Adding Personalization with Profiles to the ObjectDataSource"

Peter Kellner — Mon, 04 Sep 2006 18:55:33 +0000

Microsoft just published my fourth article. This one is titled: "Microsoft ASP.NET 2.0 Member/Role Management with IIS, Part 4: Adding Personalization with Profiles to the ObjectDataSource".

You can find it on MSDN here, or on my blog here.

Here is the introduction.

Introduction

This article extends one of the web pages developed in Part II of this series using Microsoft’s Profile feature. In Part II, the Membership API was encapsulated in an ObjectDataSource. This allowed the developer to have a drop in web page for the web site administrator to use in an web site project for editing membership. This tools allowed for similar capability to the the web site manager tool included in Visual Studio 2005 (VS2005). It is necessary because using that web configuration tool included with VS2005 is problematic and should not be used in a production web site.

This article explains how the encapsulation of Membership can be extended to include Profile (personalization) information for users. The designers of Membership included a very basic set of attributes to associate with Members (logged in users). The Profile API provided by Microsoft allows for additional information to be attached to each member. Typically, this information would include things like: first name, last name, home address, favorite color schemes or anything else the developer may want to associate with a logged in member. By personalizing the site to the member logged in, it likely increases the chance the user will return and be more comfortable while visiting.

Third Article Published on MSDN! ASP.NET 2.0, Membership Meets Atlas

Peter Kellner — Wed, 02 Aug 2006 22:30:55 +0000

Microsoft just published my third article. This one is titled: "Member/Role Management with IIS, Part 3: AJAX Enhancements with Microsoft’s Atlas".

You can find it on MSDN here, or on my blog here.

Here is the introduction.

Introduction

This article extends one of the web pages developed in Part II of this series using Microsoft’s implementation of AJAX called Atlas. It utilized two techniques for reducing web server traffic to the browser to enhance the users web experience. The first technique uses the UpdatePanel tags to limit the refreshed area of the web page to limited areas and the second has to do with implementing some javascript using Atlas techniques so that the web page is updated on every key stroke in a textbox. A user list is displayed based on what is actively typed into this textbox. After reading this article the developer will be able to implement AJAX (Microsoft’s implementation Atlas) in their own application.

Inserting Programmatically with ObjectDataSource in ASP.NET 2.0

Peter Kellner — Wed, 07 Jun 2006 20:21:02 +0000

( ObjectDataSource1.Insert(); )

ObjectDataSource’s are great for building your own middle tier between your aspx web page and your database (or any other datastore for that matter). By binding the datasource to a databound server control like detailsview, you auto-magically get the insert behavior you are looking for. If however, you just just want to insert to the ObjectDataSource you have included on your aspx page without using a databound control, you don’t have a lot of fancy footwork to do. All you have to do is reference the insert parameter by name (or index offset) and assign it directly.

Below is an example of how to insert a Role into Membership using the ObjectDataSource developed in a my previous MSDN article Microsoft ASP.NET 2.0 Member/Role Management with IIS
Part 2: Implementation.

< %@ Page Language="C#" %>
< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 
<script runat="server">
protected void Button1_Click(object sender, EventArgs e)
{
  ObjectDataSource1.InsertParameters["roleName"].DefaultValue =
    TextBoxRole.Text;
  ObjectDataSource1.Insert();
}
script>
 
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
    <title>AddRoleWithODS.aspxtitle>
head>
<body>
<form id="form1" runat="server">
  <asp :ObjectDataSource ID="ObjectDataSource1" runat="server"
    InsertMethod="Insert"
    SelectMethod="GetRoles"
    TypeName="MembershipUtilities.RoleDataObject">
    <insertparameters>
      <asp   arameter Name="roleName" Type="String" />
    insertparameters>
  asp>
  <asp :Button ID="Button1" runat="server" Text="Add Role"
    OnClick="Button1_Click" />
  <asp :TextBox ID="TextBoxRole" runat="server">
    asp>
form>
body>
html>

If you do not want to declaratively define the ObjectDataSource and just want to use it directly, you can do that also. You simply reference the ObjectDataSource by Type and call its insert method. An example of that is below.

using System;
using System.Web.UI;
using MembershipUtilities;
 
public partial class Default3 : Page
{
  protected void Button1_Click(object sender, EventArgs e)
  {
    RoleDataObject.Insert(TextBox1.Text);
  }
}

Adding Personalization via Profiles to the ObjectDataSource in ASP.NET 2.0

Peter Kellner — Tue, 14 Mar 2006 00:33:03 +0000

Also published on Microsoft’s MSDN Network at Microsoft ASP.NET 2.0 Member/Role Management with IIS, Part 4: Adding Personalization with Profiles to the ObjectDataSource

Applies to:

Microsoft ASP.NET 2.0
Microsoft Visual Studio 2005
Microsoft Internet Information Services

Run Live Demonstration Of Personalization in Membership Technology

Go to the Web Site to Create Your Own ObjectDataSource From Your Own Web.Config

Click Here for Source Code Associated With This Article

Microsoft ASP.NET 2.0 Member/Role Management with IIS, Part 2: Implementation

Introduction
Background
Why Do We Need This?
Adding Profile Information to the ObjectDataSource
Using the Profile Generating Website
Build A Simple Web Page
Conclusions

Introduction

Background

ASP.NET has done an outstanding job of making the profile information associated with a logged in user very easy to access programmatically. They have done this by using their Provider technology to create a typed class that the developer can access with intellisense property values. What does this mean? This means that the profile information is declaratively defined as XML in the web.config file. The example below shows the lines that have been added to the section of the web.config.

 <system .web>
  <profile defaultProvider="SqlProfileProvider">
    <providers>
      <remove name="AspNetSqlProfileProvider"/>
      <add name="SqlProfileProvider"
       type="System.Web.Profile.SqlProfileProvider"
       connectionStringName="LocalSqlServer"/>
    providers>
    <properties>
      <add name="FirstName" type="string"/>
      <add name="LastName" type="string"/>
      <add name="AdvancedMode" type="bool"/>
      <group name="Address">
        <add name="Street" type="string"/>
        <add name="City" type="string"/>
        <add name="State" type="string"/>
        <add name="Zip" type="string"/>
      group>    properties>  profile>
system>

These new properties defined by Microsoft can be accessed in C# at run time very simply. Below are a few lines of code showing how this can be done in a typical codebehind page. These lines of code are taken from the button update event on the page UpdateProfileSimple.aspx included in the download associated with this article.

 protected void ButtonUpdate_Click(object sender,
    EventArgs e)
{
  Profile.FirstName = TextBoxFirstName.Text;
  Profile.LastName = TextBoxLastName.Text;
  Profile.Save();
}

Profile is available everywhere because it is a static class generated from the Web.Config section shown above. Because it is an actual class, the properties FirstName and LastName are available from VS2005’s intellisense and are type safe. No incorrectly typing them and getting syntax errors.

In the simple example below (UpdateProfileSimple.aspx), it is necessary to first pre load the textboxes when the user logs in. This can be done in the pageload event as follows.

 protected void Page_Load(object sender, EventArgs e)
{
  // Only allow for profile update when a user is logged in
  MembershipUser mu = Membership.GetUser();
  if (mu == null)
  {
    ButtonUpdate.Enabled = false;
  }
  else
  {
    if (!IsPostBack)
    {
      TextBoxFirstName.Text = Profile.FirstName;
      TextBoxLastName.Text = Profile.LastName;
    }
  }
}

There are a couple things to notice in the above page_load event. First, if no user is logged in, the update button is disabled. This is because it would be meaningless to press the update button if there was no current user to update. It is important to mention that this article does not address dealing with anonymous users. That is a whole different topic. Very interesting, but beyond the scope of this article. Also notice that the first and last names are only loaded when the page is not a postback. That means that only the first time this page is loaded will the data will be loaded from the Profile datastore. After the first time, the data is stored in the page’s viewstate and no longer will have to be retrieved from the static Profile class. This is important to note because each time a profile property is accessed, a round trip to the membership database occurs. This is the reason using the Profile classes are often referred to as chatty with the database. Something to think about, and keep in mind when designing your application.

There are several good articles that go into more detail on using the profile provider. Scott Gu posts in his blog an excellent how to guide that steps you through creating basic Membership in a web application including customized Profile information. A good one in MSDN is Personalization and User Profiles in ASP.NET 2.0 by Dino Esposito. Another one of my favorites is Profiles in ASP.NET 2.0 by Scott Allen.

Why Do We Need This?

The questions comes up, why do we need an ObjectDataSource that encapsulates our Profile information? The answer is this. Even though ASP.NET does a wonderful job of giving us programmatic access to the Profile class it does not gives a simple way to view or update this data by binding it directly to any controls like gridview or detailsview. Joshua Flanagan wrote a very nice tool called ProfileView that you can see on his blog. Basically, he wrote an ASP.NET 2.0 server control that enables users to view and/or edit the Profile data. It does this using reflection at runtime to figure out what the profile information is, then it shows it.

The ObjectDataSource allows you at design time to make the presentation layer look exactly as you like. It also allows for viewing multiple members profiles at the same time. Take a look at the screen shot below to see what a gridview looks like using on ObjectDataSource generated using this technology. Also, you can play with it live right here.

At first glance, this is identical the screen developed in Part 2 of this series. If you look closer however (or at the picture to the right of the first one), you’ll notice that there are two new columns. First Name and Last Name. Both of these columns have data retrieved from the Membership Profile data provider we have been discussing. In the next section the details of what changes to the ObjectDataSource in the previous article have been made to allow this to happen. Something very important to note however, is that since the ObjectDataSource is basically a static class, the profile information in that ObjectDataSource will not automatically change when the web.config is changed (unlike Joshua Flanagan’s solution which will change).

Adding Profile Information to the ObjectDataSource

As was mentioned earlier, the ObjectDataSource developed here is 100% based on the one developed in Part II of this MSDN series, Implementation. The discussion here assumes all the previous code is understood and only explains the additions to support the Profile feature. All the code described here is what gets generated by the ObjectDataSource generator on Peter Kellner’s Blog (this tool is discussed in greater detail in the next major section of this article). In this section we go through the details of what gets added. In the next section it is shown how the steps to generating the source described here from an existing web.config file.

Changing Class Names

Since it’s possible the ObjectDataSource geneated here may be used in the same project as the one provided with Part 2 of this series, all the public names have been changed to avoid naming conflicts. For example, the class name MembershipUserODS has been renamed to MembershipUserAndProfileODS. The RoleData class has been renamed RoleDataForMP and the MemberhipUserWrapper class has been renamed MembershipUserWrapperForMP (MP standing for MembershipProfile).

The Insert Method

The method signature of Insert now contains all the names of the Profile properties. In addition to Membership.CreateUser being called, the Profile properties must be saves also with the Profile.Save() method. Below is the complete Insert method for an example set of profile properties (profile properties are stored in the web.config file and will likely be different for each asp.net web application).

[DataObjectMethod(DataObjectMethodType.Insert, true)]
public void Insert(string userName, bool isApproved,
    string comment, DateTime lastLockoutDate,
    DateTime creationDate,string email,
    DateTime lastActivityDate, string providerName,
    bool isLockedOut,DateTime lastLoginDate,
    bool isOnline, string passwordQuestion,
    DateTime lastPasswordChangedDate, string password,
    string passwordAnswer, string firstName,
    string lastName, bool advancedMode,
    string address_Street, string address_City,
    string address_State, string address_Zip
    )
{

    MembershipCreateStatus status;
    Membership.CreateUser(userName, password, email,
        passwordQuestion, passwordAnswer,
        isApproved, out status);

    if (status != MembershipCreateStatus.Success)
    {
     throw new ApplicationException(status.ToString());
    }

    MembershipUser mu = Membership.GetUser(userName);
    mu.Comment = comment;
    Membership.UpdateUser(mu);
    ProfileCommon pc =
     (ProfileCommon)ProfileBase.Create
        (mu.UserName, true);
    pc.FirstName = firstName;
    pc.LastName = lastName;
    pc.AdvancedMode = advancedMode;
    pc.Address.Street = address_Street;
    pc.Address.City = address_City;
    pc.Address.State = address_State;
    pc.Address.Zip = address_Zip;
    pc.Save();
}

Something also to take note of is the the variable names are constructed with an underscore because variable names with periods would not work. Notice in particular the properties that are nested such as address_state. This refers to the Profile property pc.Address.State.

The Delete Method

The delete method has no changes. This is because the membership class takes care of removing all profile information when Membership.DeleteUser() is invoked.

The Update Method

The Update method is changed. To the parameter list is added all the parameters representing properties. Then, in the update method itself the profile information is update after the Membership is updated. below is a portion of the code for this using the example properties.

ProfileCommon pc = (ProfileCommon)ProfileBase.
      Create(mu.UserName, true);
    pc.FirstName = firstName;
    pc.LastName = lastName;
    pc.AdvancedMode = advancedMode;
    pc.Address.Street = address_Street;
    pc.Address.City = address_City;
    pc.Address.State = address_State;
    pc.Address.Zip = address_Zip;
    pc.Save();

The Get (Select) Methods

Just like in Part 2 of this series, there are several Get Methods provided. No additional get methods are added, however now, because of the addition of the Profile properties, the Get Method’s return profile properties include Membership Properties as well as Profile properties. This is handled by first retrieving the Membership data with GetUser or GetUsers methods, then adding the additional properties from the profile to the Generic list which will get returned. The critical section of code that does this is next.

MembershipUserCollection muc = Membership.GetAllUsers();
foreach (MembershipUser mu in muc)
{
 if ((returnAllApprovedUsers==true && mu.IsApproved==true) ||
 (returnAllNotApprovedUsers==true && mu.IsApproved==false))
 {
    MembershipUserWrapperForMP md =
      new MembershipUserWrapperForMP(mu);
    ProfileCommon pc = (ProfileCommon)ProfileBase.Create
      (mu.UserName, true);
    md.FirstName = pc.FirstName;
    md.LastName = pc.LastName;
    md.AdvancedMode = pc.AdvancedMode;
    md.Address_Street = pc.Address.Street;
    md.Address_City = pc.Address.City;
    md.Address_State = pc.Address.State;
    md.Address_Zip = pc.Address.Zip;
    memberList.Add(md);
 }
}

Sorting Support

Sorting the ObjectDataSource’s columns is also supported. Just as in Membership Part 2, this is supported using anonymous delegates. Basically, a comparater method is created with an anonymous delegate that takes two parameters. The left and right hand side of a sort operation. Then, using this comparater, the generic List is sorted before being returned to the caller. This very clever construct was inspired by Ted Neward at a Code Camp in Portland.

Just like the MembershipUser properties, Profile properties are handled the same way so that those values can be sorted in a GridView by clicking on the column headers. Below is the creation of one comparater method.

switch (sortDataBase)
{
  case "FirstName":
    comparison = new
      Comparison(
       delegate(MembershipUserWrapperForMP lhs,
            MembershipUserWrapperForMP rhs)
       {
           return lhs.FirstName.CompareTo(
              rhs.FirstName);
       }
     );
    break;

The Class associated with the Generic List

The final piece of code that has to be extended is the Class that is returned from the Get methods. That is the generic list which is declared as follows.

 protected void Page_Load(object sender, EventArgs e)
{
  // Only allow for profile update when a user is logged in
  MembershipUser mu = Membership.GetUser();
  if (mu == null)
  {
    ButtonUpdate.Enabled = false;
  }
  else
  {
    if (!IsPostBack)
    {
      TextBoxFirstName.Text = Profile.FirstName;
      TextBoxLastName.Text = Profile.LastName;
    }
  }
}

One Final Trick on Using the ObjectDataSource

ObjectDataSource’s are great for using with databound ASP.NET’s controls such as GridView and DetailsView. They are wired such that the get methods, update, delete and insert line up perfectly with what those controls are looking for. However, the ODS’s can be used directly without having a presentation style control associated with them. For example, the Insert method associated with adding a new member in the included code from the asp.net page MembershipWithProfile.aspx uses the ObjectDataSource to insert even though it is not bound to any control on the page. The data it is entering is coming from TextBox’s in a table. Below is the Insert code used. Notice how straight forward it is to use compared do creating an inserter and doing all the ADO without this class.

protected void ButtonNewUser_Click(object sender, EventArgs e)
{

    MembershipUtilities.MembershipUserAndProfileODS
      membershipUserAndProfileODS =
        new MembershipUserAndProfileODS();

    membershipUserAndProfileODS.Insert(
        TextBoxUserName.Text,
        CheckboxApproval.Checked,
        string.Empty,
        DateTime.Now,
        DateTime.Now,
        TextBoxEmail.Text,
        DateTime.Now,
        string.Empty,
        false,
        DateTime.Now,
        false,
        TextBoxPasswordQuestion.Text,
        DateTime.Now,
        TextBoxPassword.Text,
        TextBoxPasswordAnswer.Text,
        TextBoxFirstName.Text,
        TextBoxLastName.Text,
        false,
        string.Empty,
        string.Empty,
        string.Empty,
        string.Empty);

    GridViewMemberUser.DataBind();
    TextBoxUserName.Text = string.Empty;
    TextBoxFirstName.Text = string.Empty;
    TextBoxLastName.Text = string.Empty;
    TextBoxPassword.Text = string.Empty;
    TextBoxEmail.Text = string.Empty;
    TextBoxPasswordAnswer.Text = string.Empty;
    TextBoxPasswordQuestion.Text = string.Empty;
    CheckboxApproval.Checked = false;
}

Because this is an actual class with properties, using the ObjectDataSource class is type safe. For example, in the code below, the user may want to count how many zipcodes in the membership database that begin with 9. Here is the code to do it. Notice how Address_Zip is used in a type safe way.

protected void ButtonZipCount_Click
    (object sender, EventArgs e)
{
    MembershipUtilities.MembershipUserAndProfileODS
        membershipUserAndProfileODS =
        new MembershipUserAndProfileODS();

    List li =
        membershipUserAndProfileODS.GetMembers
        (string.Empty);

    int count = 0;
    foreach (MembershipUserWrapperForMP mu in li)
    {
        if (mu.Address_Zip.StartsWith("9"))
        {
            count++;
        }
    }
}

Using the Profile Generating Website

All the changes listed in the previous section could be done by hand, however this would be very tedious. To make this process much easier, a code generator has been developed which takes as input the applications web.config file’s section. The idea is to cut this out of the web.config file and paste it into the web page which will generate the code for you. Below is a screen show of what the web page looks like. When you get to this page, you must first click on the button in the right column labeled "Click Here to Begin".

Here is the URL: http://painfreeods.peterkellner.net/

The XML which is pasted into the multi line orange textbox is as follows (you should paste your own in here).

<system  .web>
  <profile defaultprovider="SqlProfileProvider">
    <providers>
      <remove name="AspNetSqlProfileProvider" />
      <add name="SqlProfileProvider" connectionstringname="LocalSqlServer" type="System.Web.Profile.SqlProfileProvider" />
    providers>
    <properties>
      <add name="FirstName" type="string" />
      <add name="LastName" type="string" />
      <add name="AdvancedMode" type="bool" />
      <group name="Address">
        <add name="Street" type="string" />
        <add name="City" type="string" />
        <add name="State" type="string" />
        <add name="Zip" type="string" />
      group>    properties>  profile>
system>

Now, if the "Show Generated C#" button is pressed, the complete ObjectDataSource will be created. This code can then be cut and pasted into the App_Code directory of the web project. Here is what the screen looks like.

There are some limitations to this code generation technology. First is that there can only be one level of nesting. That is, there can be no groups of groups. Just one level of grouping is allowed as is shown here. It is OK to have multiple groups, just not nested. Another limitation is the type associated with the name must be a C# type. That is, string, bool,DateTime,etc. The final limitation (known about) is that it can not handle Array or Collection type properties. All properties must be single valued.

At this point, error checking is minimal so if the limitations are exceeded, something will likely come out but it may not be what was desired.

Build A Simple Web Page

Now that the C# class has been generated, the next steps are very straight forward. For those who have not built a GridView based on an ObjectDataSource, here is a pictorial step by step of the 9 things needed to do to have a very simple gridview control in under 5 minutes.

Building a Web Page From Scratch
1. Add a New Web Page to the Project	2. Choose Web Page and Name it
3. Add a GridView and an ObjectDataSource. Associate them	4. Configure the ObjectDataSource by Assigning the Class
5. Choose the Get Method (Use Default)	6. Choose the Update Method (Use Default)
7. Choose the Insert Method (Choose Default)	8. Choose the Delete Method (Choose Default)
9. Run it! (OK, had to enable edit and delete on Gridview. No more boxes left)

The code in the associated source to this article has a web apge ( MembershipWithProfile.aspx) which is very similar to what is done here.

Conclusions

Profiles are a very powerful way to store information about Membership. It’s powerful in that with very little coding, lots of additional information about logged in users is available. With this tool, there is now a better way to organize this information and maintain it. Briefly mentioned earlier were the performance implications of using Profile information. It is important to understand what his happening under the covers when this technology is used. As long there is an understanding of what is happening and it is acceptable in the web application being developed, this is a wonderful technology.

Finally, as a plug to the technology that was used in this free ObjectDataSource creator, the Pain Free ObjectDataSource Creator, available through subscription on this blog, lets the developer generate very flexible ObjectDataSource’s to access database information in SqlServer, MySql and Oracle. Unlike the Profile ODS generator in this article, the ODS generator for databases gives you a large amount of flexibility. An infinite number of getter methods, updaters and inserters can be defined. It works with views, and also stored procedures. Any questions on the Pain Free ODS Generator, click here.

Thanks for reading, and best of luck with your coding projects.

AJAX Meets ASP.NET 2.0 Membership Management For IIS

Peter Kellner — Thu, 02 Mar 2006 19:34:44 +0000

Microsoft ASP.NET 2.0 Member/Role Management with IIS, Part 3: AJAX Enhancements with Microsoft’s Atlas

Peter Kellner

http://PeterKellner.net

March 2006

Applies to:

Microsoft ASP.NET 2.0

Microsoft Visual Studio 2005

Microsoft Internet Information Services

Run Live Demonstration Of AJAX Technology

Click Here for Source Code Associated With This Article

Introduction
What is AJAX and Atlas
Background
The AJAX Enhanced Version
Technologies Used in AJAX Enhanced Version
Steps Involved in Building (or upgrading) to AJAX using Atlas
Using UpdatePanel ASP.NET Tag
What is Really Happening
Enhancing the TextBox for User Search
Conclusions

Introduction

What is AJAX and Atlas

AJAX is an acronym for Asynchronous JavaScript And XML. It is a technique for making interactive web applications more responsive. It does this by exchanging small amounts of information between the web server and the web client, thereby reducing the amount of traffic to the web client and making the application more responsive. Without AJAX, each time a page is refreshed (or a postback in generated) the complete page must be retransmitted to the users web browser. This is somewhat mitigated by the local cache on the web browser, but still overkill since most of the information on a postback to a web page does not change.

Atlas is Microsoft’s implantation of AJAX. It is designed to make it relatively easy for software engineer, already skilled in ASP.NET 2.0 to take advantage of AJAX. Though Atlas has huge capabilities (which, by the way come with a huge learning curve), it is very easy to implement the basics of AJAX and significantly improve the user experience of a web site designed with ASP.NET 2.0 as well be shown in this article.

Background

Managing membership and roles for ASP.NET 2.0 using ObjectDataSource technology was developed in a previous article published by this author in MSDN ( http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/ASP2memroleman.asp ). This article stepped through the inner workings of an ObjectDataSource that allowed for the easy creation of gridviews, dataviews, or any other databound control. It also presented a best practices solution in the form of a ASP.NET 2.0 web page (aspx file). The solution allowed for adding, modifying and deleting members, adding and deleting roles, as well as assigning users to roles. The solution is functionally similar to what comes with Visual Studio 2005 under the menu item "Website / ASP.NET Configuration". The major benefit is that this solution works 100% with IIS 5.1 and 6.0 and gives the software engineer complete customization control of what is presented to the user. It would normally be set to administrator access only. Below is a screen shot of this application previously developed.

This application shown above has no AJAX technology in it. This means that every interaction you have with the web form requires a full page refresh of html from the web server. In this case, a picture is not worth very many words, but a URL will certainly make the point. Go to the URL: http://livedemos.peterkellner.net/AJAXDemo/Default.aspx and play with the web site. Feel completely free to search on this data, add new users, add roles, assign and unassign roles as you please noticing at the time how the page reacts to changes. In particular, note the Search button on top for finding users. This search is a little different than you would normally expect. Instead of looking for exact matches, it effectively finds usernames that begin with what you have typed in the textbox when you press the search button. In the next section, the AJAX enhanced version, the search button is gone and as the username is typed into the textbox, the list of usernames will be automatically updated. This could have been done here also, however it would have caused a complete refresh of the page on every keystroke. Not only would the performance have been unacceptable, it would also have been unusable with all the flashing while typing. This is why in non-AJAX applications, there is almost always a button to press when data is finished being entered.

While you are running the demonstration program, notice at the top of the page there is a link that takes you to the same application without AJAX. Notice that in this application, there is a button for search. Notice also when you check and uncheck the checkboxes to display Manage Roles or Create New Users, those sections turn on and off with a lot of screen refreshing. Also notice the difference when you edit users and assign or unassign roles.

The AJAX Enhanced Version

Without actually running the web application, the only visual change the user can see in the AJAX enhanced version of this application is that there is no search button above the user list. This is because with AJAX, as the user types in the search criteria, the list of users is automatically restricted to the search criteria defined by users that begin with what is typed. Notice in the screen shot below, ch is entered into the username textbox and just the usernames beginning with ch automatically appear.

Technologies Used in AJAX Enhanced Version

Obviously, Microsoft’s Atlas is the primary technology used to implement AJAX. Atlas has lots of functionality and capability, however in this article (and the code associated with the AJAX enhanced Membership Editor), there is just a small part of Atlas being used. Actually, there are only two technologies going on. One has to do with the updates on the screen not requiring complete html refreshes between postbacks, and the other has to do with extending the functionality of the TextBox control the user enters the name for search. Because the default TextBox has no event associated with characters changing (it only has an event which generates a postback for TextChanged) the TextBox has to be enhanced to deal with the javascript function OnTextChanged.

Steps Involved in Building (or upgrading) to AJAX using Atlas

In order to Atlas enable an application you need to make several changes to your project. I won’t go through all the details, however, the basics are you need to copy in the Atlas script library, modify your web.config, add the atlas dll to your project and finally, add some initializing tags in your aspx pages. The other way to begin working with Atlas (and is it was done to convert the project associated with this article) is first download the new Atlas template from Microsoft’s Atlas web site. Then, create a new web project using the newly installed Atlas template. Next, rename the default.aspx file in case you have your own, then copy in all your existing libraries and pages. Finally, add your sections to the Atlas enabled web.config file and make sure everything works as before with no Atlas functionality. The final step is to look at the original default.aspx file and copy the Atlas constructs into the headers of an existing page you want to add AJAX capabilities.

It is recommended not to put Atlas in your master page because there are undoubtedly pages that do not need AJAX capability. It is better to put that capability in only the pages you need to keep things simple.

Using UpdatePanel ASP.NET Tag

Below is the actual UpdatePanel asp.net control surrounding the checkboxes that let you turn on and off the Role Management, and the Create of New User section. It’s the two checkboxes half way down the web screen.

<atlas :UpdatePanel ID="UpdatePanelCheckBoxes" runat="server">
 <contenttemplate>
  <table>
   <tr>
    <td align="left">
        <asp :CheckBox ID="CheckBoxManageRoles" Text="Manage Roles"
          runat="server" AutoPostBack="True" Checked="True" />
    td>
    <td align="right">
        <asp :CheckBox ID="CheckBoxAddUser" Text="Create New Users"
         runat="server" AutoPostBack="True" Checked="True" />
    td>
   tr>
  table>
 contenttemplate>
atlas>

The UpdatePanel control is the control that will most likely be used the most. By surrounding parts of the web page that will change on the postback, this causes the affect of letting this section update with out actually a screen refresh. Essentially, what Atlas does on a page that is Atlas enabled, is it lets all the normal asp.net page lifecycle events process normally (including the Page_Init method) but instead of redisplaying all the HTML in the Page_Render method, it knows to only update code inside the UpdatePanels defined on the web page. In reality what is happening is Atlas is simulating a postback instead of doing a real one.

Something that must be set also is in the ScriptManager tag, for this to actually work, the EnablePartialRendering must be set to true as shown below. If it is not set, then the page behaves as if the UpdatePanel tags are not there.

<atlas :ScriptManager ID="ScripManager" runat="server"
   EnablePartialRendering="true">
atlas>

The final thing to do is to surround all the areas on the aspx page with these UpdatePanel tags. Once this is done, VS2005 does a nice job of showing the UpdatePanel areas. The screen shot below shows the actual screen shot of the page used to manage members. Notice all the UpdatePanel tags displayed above the regions. Clicking on the image will display a large one which is much easier to see the details.

Trigger tags go hand in hand with the UpdatePanel control. Essentially, you can nest trigger controls in the UpdatePanel control and that will specify when the UpdatePanel will actually be posted back. You can specify triggers in two ways. The first way is on some control event such as the EventName "Click" on the button control. The other way is on some control value changing. with that, you would specify the controlID and the property name. There are no examples of triggers in the article download. The code below is just an example of typical code.

<atlas :UpdatePanel ID="Panel1" runat="server">
 <contenttemplate>
  <asp :TextBox ID="TextBox1" runat="server">asp>
  <asp :Button ID="Button1" runat="server">asp>
 contenttemplate>
 <triggers>
  <atlas :ControlEventTrigger ControlID="Button1" EventName="Click" />
  <atlas :ControlValueTrigger ControlID="TextBox1" PropertyName="Text"   />
 triggers>
atlas>

What is Really Happening

To understand what is really happening with these UpdatePanel tags, it is helpful to look at the source generated for the web page. Essentially what is happening is that for every control on your web page that is surrounded by the UpdatePanel tags, javascript is created which forces a postback on every click. For example, just looking at the checkboxAddUser control, the following is what is generated.

<td align="right">
 <label for="CheckBoxAddUser">Create New Userslabel>
   <input id="CheckBoxAddUser"
   type="checkbox" name="CheckBoxAddUser"
   checked="checked" onclick=
   "javascript:setTimeout
   ('__doPostBack(\'CheckBoxAddUser\',\'\')', 0)" />
td>

This is in addition to all the javascript references that include lots of other javascripts. The bottom line here is that if you include Atlas in your web pages, the actual payload size delivered to your web page in bytes will be significantly larger on the first download then it would be without Atlas. Subsequent requests are of course much smaller because, depending on how you design your page, only small amounts of data need to be returned on each future postback.

Enhancing the TextBox for User Search

The textbox search functionality is a little more tricky. It involves adding javascript which reacts to keystrokes changes. The reason this is necessary is because there is not event in the TextBox control that responds to keyboard clicks. There is only an event that reacts to text changes which is not good enough for our needs. In this application, I am using javascript from The Atlas Notes Blog by Garbin

The steps necessary to make this work are as follows:

Add the TextChangedBehavior.js to the ScriptLibrary folder

Add just below the

tag of your aspx page a line that includes the new javascript

<atlas :ScriptManager ID="sm" runat="server"
     EnablePartialRendering="true">
 <scripts>
  <atlas :ScriptReference
     Path="ScriptLibrary/TextChangedBehavior.js" />
 scripts>
atlas>

Add a small javascript code piece to your web page that your TextBox control will reference

<script type="text/javascript">
  function onTextChange() {
    __doPostBack('GridViewMemberUser','') ;
        }
script>

And, finally add another xml-script to the bottom of your web page that declaratively tells the Atlas processor to add this new javascript capability to the TextBoxSearchUser Control. This essentially maps the onclick event of the TextBoxSearchUser to the onTextChange javascript. The timeout is very nice because it allows for typing without causing postbacks until the typer stops typing for that many milliseconds.

<script type="text/xml-script">
 
  
   "TextBoxSearchUser">
    
     "100"
        changed="onTextChange" />
    
   
  
 
script>

Conclusions

AJAX, though in concept is not new, is one of the most exciting new technologies to hit the Web for quite some time. The tool kits now available, such as Microsoft’s Atlas which is described here and included with the demonstration download, makes adding AJAX functionality to existing ASP.NET 2.0 applications very straight forward. In this article, I’ve discussed the mechanics of adding AJAX functionality but have not addressed the impact to web servers, cross browser functionality or web design. Those things must all be considered before including AJAX technology in an existing web application. Overall however, AJAX, and Microsoft’s implementation ATLAS, are wonderful things.

Membership Management Newly Styled GridView

Peter Kellner — Fri, 27 Jan 2006 17:46:09 +0000

Mikhail Lukyanau has been kind enough to provide a redesigned version of the membership.aspx page. The source file for this can be downloaded at (Download New File). Below is a screen shot of this new look.

Figure 1 – Updated Design for Membership.aspx By Mikhail Lukyanau

Using Membeship ObjectDataSource For Returning ProviderUserKey (ForeignKey Use)

Peter Kellner — Tue, 10 Jan 2006 16:54:53 +0000

I was recently asked how to use the Membership Data Object to return the unique ProviderKey generated by the Membership object. This may be necessary if want to associate the membership data with an existing table. That is, add a foreign key "ProviderUserKey" to another table so you can track an existing user to your current database without getting involved in extending the base provider. You can of course extend the existing provider to include other fields, but in general, you probably are better off maintaining your own tables rather than extending the provider model. Peter Dawson does an excellent job of explaining and showing how to extend the Membership Provider in his article Creating a Custom ASP.NET Provider. (published on theserverside.net)

So, back to what needs to be done to use my Membership ObjectDataClass (Part 2: Implementation" href="http://peterkellner.net/archives/2006/01/09/24/" rel=bookmark>Microsoft ASP.NET 2.0 Member/Role Management with IIS

Part 2: Implementation

). First thing is you need to add another insert method to the class. This method takes just a few parameters and returns as out parameters both the status of the insert as well as the providerUserKey as a string.

[DataObjectMethod(DataObjectMethodType.Insert, false)]
static public void Insert(string userName,
    bool isApproved,
    string email,
    string passwordQuestion,
    string password,
    string passwordAnswer,
    out MembershipCreateStatus membershipCreateStatus,
    out string providerIdKeyString)
{
    MembershipUser muNew = Membership.CreateUser(userName,
        password, email, passwordQuestion, passwordAnswer,
        isApproved,out membershipCreateStatus);
    if (membershipCreateStatus ==
        MembershipCreateStatus.Success)
    {
        providerIdKeyString = muNew.ProviderUserKey.ToString();
    }
    else
    {
        providerIdKeyString = string.Empty;  // failed
    }
    return;
}

Figure 1 – The New Insert Method to be added to MembershipUserODS.cs

If you want to turn the Guid passed back into a native Guid type do the following. (this could be useful if you want to retrieve the current username as shown below.

Guid myNewGuild = new Guid(providerIdKeyString);
MembershipUser myCurrentMembershipUser = Membership.GetUser(myNewGuild);
string memberName = myCurrentMembershipUser.UserName;

Figure 2 – Example of converting created ProviderUseKey to Guid and retreiving username

Now that we have the new Insert Method defined the easiest thing to do is use it directly. Below is a complete aspx page that references the new method as well as a screen shot of what it looks like to add a new member. Notice that the status label is returning the providerUserKey.

Figure 3 – Examples of adding a new user with a valid password, and one without a valid password

< %@ Page Language="C#" %>
< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 
<script runat="server">
 
    protected void ButtonNewUser_Click(object sender, EventArgs e)
    {
        MembershipCreateStatus membershipCreateStatus;
        string providerIdKeyString = string.Empty;
        MembershipUtilities.MembershipUserODS.Insert(TextBoxUserName.Text,
            CheckboxApproval.Checked,
            TextBoxEmail.Text,
            TextBoxPasswordQuestion.Text,
            TextBoxPassword.Text,
            TextBoxPasswordAnswer.Text,
            out membershipCreateStatus,
            out providerIdKeyString
        );
        if (membershipCreateStatus == MembershipCreateStatus.Success)
        {
            LabelInsertMessage.Text = "New User Create Successfully.  Key: " + providerIdKeyString;
        }
        else
        {
            LabelInsertMessage.Text = membershipCreateStatus.ToString();
        }
 
        return;
    }
script>
 
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
    <title>Untitled Pagetitle>
head>
<body>
    <form id="form1" runat="server">
        <div>
            <asp    anel ID="PanelCreateUser" runat="server" BorderColor="Black" BorderWidth="1px"
                Height="50px" Width="125px">
                <table cellpadding="3" cellspacing="3">
                    <tr>
                        <td style="height: 32px">
                            <asp :Label ID="Label3" runat="server" Text="UserName">asp>
                        td>
                        <td style="height: 32px">
                            <asp :TextBox ID="TextBoxUserName" runat="server">asp>
                        td>
                        <td style="height: 32px">
                            <asp :Label ID="Label4" runat="server" Text="Password">asp>
                        td>
                        <td style="height: 32px">
                            <asp :TextBox ID="TextBoxPassword" runat="server">asp>
                        td>
                    tr>
                    <tr>
                        <td>
                            <asp :Label ID="Label5" runat="server" Text="PasswordQuestion">asp>
                        td>
                        <td>
                            <asp :TextBox ID="TextBoxPasswordQuestion" runat="server">asp>
                        td>
                        <td>
                            <asp :Label ID="Label6" runat="server" Text="PasswordAnswer">asp>
                        td>
                        <td>
                            <asp :TextBox ID="TextBoxPasswordAnswer" runat="server">asp>
                        td>
                    tr>
                    <tr>
                        <td>
                            <asp :Label ID="Label2" runat="server" Text="Email">asp>
                        td>
                        <td>
                            <asp :TextBox ID="TextBoxEmail" runat="server">asp>
                        td>
                        <td>
                            <asp :Label ID="Label9" runat="server" Text="Approved">asp>
                        td>
                        <td>
                            <asp :CheckBox ID="CheckboxApproval" runat="server" />
                        td>
                    tr>
                    <tr>
                        <td>
                            <asp :Button ID="ButtonNewUser" runat="server" OnClick="ButtonNewUser_Click" Text="Create New User" />
                        td>
                    tr>
                table>
                asp><asp :Label ID="LabelInsertMessage" runat="server">asp>
        div>
    form>
body>
html>

Figure 4 – complete aspx page excercising new insert method

PeterKellner.net » Membership

Speaking Wednesday May 20th, 6:30PM, Microsoft Office San Francisco on ExtJS and ASP.NET Membership!

When:

Where:

Event Description

How to Set the Default Value of a DropDownList in an ASP.NET Page

(Using Membership ObjectDataSource From MSDN Article)

Resetting Password with ASP.NET 2.0 Membership and Multiple Providers

Have GridView Highlight Last Inserted Record in ASP.NET 2.0

Introduction

What It Looks Like Running

The Code

About the Author

Moving From Casini to IIS, Login Fails. How come?

ASP.NET 2.0 Membership

Fourth MSDN Article Published! "Adding Personalization with Profiles to the ObjectDataSource"

Introduction

Third Article Published on MSDN! ASP.NET 2.0, Membership Meets Atlas

Introduction

Inserting Programmatically with ObjectDataSource in ASP.NET 2.0

( ObjectDataSource1.Insert(); )

Adding Personalization via Profiles to the ObjectDataSource in ASP.NET 2.0

Contents

Introduction

Background

Why Do We Need This?

Adding Profile Information to the ObjectDataSource

Changing Class Names

The Insert Method

The Delete Method

The Update Method

The Get (Select) Methods

Sorting Support

The Class associated with the Generic List

One Final Trick on Using the ObjectDataSource

Using the Profile Generating Website

Build A Simple Web Page

Conclusions

AJAX Meets ASP.NET 2.0 Membership Management For IIS

Contents

Introduction

What is AJAX and Atlas

Background

The AJAX Enhanced Version

Technologies Used in AJAX Enhanced Version

Steps Involved in Building (or upgrading) to AJAX using Atlas

Using UpdatePanel ASP.NET Tag

What is Really Happening

Enhancing the TextBox for User Search

Conclusions

Membership Management Newly Styled GridView

Using Membeship ObjectDataSource For Returning ProviderUserKey (ForeignKey Use)