Yes I would like to save this file!  If you're gonna ask, at least let me say "Yes".

A few weeks ago, I posted a solution I came up with a way to utilize a remember me checkbox in .NET 2.0 that, when selected, pre-populated just the username in the username textbox during subsequent visits.  The problem I found was that signing out of FormsAuthentication wiped out any and all cookies I had set during or prior to logging a user in.  So, the simple act of looking at the cookie to see if the user wanted to be remembered became quite an ordeal.  My solution was to set/get the cookie using JavaScript.  This worked and I was happy.

This is a shot of the cookie collection when the user signs out and returns to the login page:



Notice that the count of the cookie collection is 0.

There are some skeptics out there though.  So, for them, I've created a very simple website solution that tries to set and get the remember me cookie as explained above.  Now, the solution DOES NOT work.  Once a user logs out, the remember me cookie is gone, along with the saved username, and there is no way to tell if the user had selected to have his username saved. 

The challenge is to modify the solution so that it DOES work.

Post updates in the comments.  When and if a solution is found and posted in the comments, I'll add to the solution and re-post so that we can finally get around this issue.

Note: The solution is NOT using the Login control on purpose.  The goal is to have the username pre-populated but still make them login.  From my limited usage of the Login control, it appears to actually keep the user logged in.  If you can get this solution to work with the Login control, I say go for it... and more kudos to you for doing so.

The winner receives bragging rights.

Download the solution: FormsAuthenticationRememberMeChallenge.zip (5.01 KB)

(the username and password to login into the form is "test"/"1111")

UPDATE: That was fast!  Adi has come up with a winning solution.  Congrats. 

Download it here: FormsAuthenticationRememberMeSolution.zip (5.55 KB)

Her name is Iki Bana Kamakazi

While writing an email to a colleague today, Outlook 2003 underlined a passage and offered a correction.  The correction it offered didn't sound right but I clicked on it anyway to see if it looked better corrected.  It didn't.  But what I noticed next is that it again underlined the same passage and offered a correction, this time back to what it was originally.  Thinking it knows best (yeah, right), I clicked on it again and guess what?  It corrected back to the original passage and offered a "suggestion".

Original passage that "needed" correcting:



Corrected passage that also "needed" correcting:



The passage corrected back to the original:



And so I found the anomaly: The correction that corrected itself with a correction that needed to be corrected back to the original correction.