I've seen this in several threads now, but I haven't found a solution yet.  Does anyone know if the control adapter designers are working on this problem?  When using the CreateUserWizard with CSS Control Adapters, it attempts to create the user twice.  Some new information that they may not have is that this happens with IE, but not with Firefox.  I've verified this with IE7 and Firefox 2.0.  Another person verified it in IE6.  Here are some of the other threads reporting this problem:

http://forums.asp.net/thread/1499422.aspx

http://forums.asp.net/thread/1618075.aspx

http://forums.asp.net/thread/1633367.aspx

http://forums.asp.net/thread/1484654.aspx

I too would be very interested to know if there has been any movement on this. There are a few threads discussing  the problem, as the post upthread shows but nothing in the way of real solution.

I am experiencing the same problem with CSS Controls adapters when used with the CreateUserWizard. Converting the control to templated breaks the adapter rendering, but doesn't solve the broken functionality. The only solution so far has been to remove the CreateUserWizard from the browser definition file (CSSFriendlyAdapters.browser).

Many thanks.

**BUMP**

I spent the last 5 hours chasing down this exact same problem... and i just now came across this post.

When using the control I kept getting the "Please enter a different user name." error message, and upon looking in my user management tool I could see that the user had in fact been created. So I threw a few breakpoints in my code (where I had attached handlers to the wizard's CreatingUser and CreatedUser events) and noticed that they were being fired twice.

Upon a little more inspection it looks like the entire page life-cycle is firing twice as I was also seeing the page's OnInit fire two times. And to confirm what others have said, this issue does not seem to effect my app when running in FF (2.0), but does happen when running in IE7.

This issue really needs to be addressed as it breaks all but the most basic use-cases - (read: the it works for drag-and-drop demos, but not for use in the real world).

Does anyone from the Control Adapters team have any info on this? Any updates would be much appreciated.

Thanks!
 

I'm seeing a similar issue with the PasswordRecovery adapter - the password is being reset twice and Fiddler show two requests for the page.

Is anyone from the CSS Adapters teams looking into this?
 

Hey Steve,

 I've just posted an solution for this at http://forums.asp.net/1676119/ShowThread.aspx#1676119 which should serve as an in the interim fix until the CSS Adapters team releases a new version.

Enjoy,

Tana
 

Didn't fix the problem for me.  Submting the wizard form results in the form reloading, and a login control that is placed in the side column menu has it's user name and password fields marked like their validation was submited and errored.  I checked my database to verify that new new records were created.  No error shows up for the CreateUserWizard control.  It's as if it was never actually submitted.

I'm going to have to remove the CSS Friendly adapter for this control.  After a month of working with these Adapters, I'm growing to strongly dislike them. While I appreciate the effort put into them, and appreciate their goal, it's not worth it to throw these adapters into an environment and then spend countless hours debugging the numerous issues they've caused.  At least a few of the adapters seem to work ok so far.

Hi there,

If you haven't already given up on using the adapter for the CreateUserWizard then would you like to give the following a go?

Replace the WebControlAdapterExtender.MakeNameFromId method with the following: 

static public string MakeNameFromId(string id)
{
    string name = "";
    for (int i=0; ichar thisChar = id[i];
        char prevChar = ((i - 1) > -1) ? id[i - 1] : ' ';
        char nextChar = ((i + 1) < id.Length) ? id[i + 1] : ' ';
        if (thisChar == '_' && prevChar != '_' && i > 0)
        {
            // Transforms '_grandParentControl__parentControl_childControl' to:
            // '_grandParentControl$_parentControl$childControl'.
            name += "$";
        }
        else
        {
            name += thisChar;
        }
    }
    return name;
}

It fixes a problem that I found with child input elements of adapted controls being rendered with incorrent names when they are nested within other server-side controls.

Cheers,

Tana

Tana,

If you're comfortable with the fix (I don't have a test page for CreateUserWizard to test against), post it to CodePlex.