How can we add a lockout notification?

I was wondering if anyone had a simple solution on how to add a lockout notification to a sign-in form based on this solution. This should be displayed once the user tries to login incorrectly after the number of max unsuccessful attempt set in the
web config file. Any ideas, samples, links would be appreciated.

Thanks for the code sample. Would you mind adding your sign-in page to the solution or sending it to me direct. I've created one in a separate solution and the I'm interested in how you integrated yours with the FBA Pack.

I can't give you the full login page, as it is custom for a client and has lots of extra logic specifically for the client. I also don't actually use the FBA Pack with it, but code very similar. Here it is, with some items removed or renamed, so it
may not compile as is, but it is very close to the actual page so it shouldn't take many changes to get it working:

Instead of Utils.GetUser() I'm using Membership.GetUser() now. But I'm getting "Object reference not set to an instance of an object." error in base.OnLoad(e); where base is Microsoft.SharePoint.IdentityModel.Pages.FormsSignInPage. Any idea why will it be?

The reason for the protection level error is because the Utils class in the FBA Pack is not declared public. As I mentioned earlier, the sample code was not actually against the FBA pack, so it may require some slight modifications. In fact, GetUser doesn't
even exist in the current version of the Utils class.

I'd take a look at UserEdit.aspx.cs. I call the membership provider's GetUser method in there. So to get it to work, you could either change the FBA Pack's accessibility level on the Utils class and recompile, and add the code from UserEdit.aspx.cs.
Or you could just copy the required code from the FBA Pack and paste it into your project.

I'm not sure why you're getting an object reference not set' - the only reason I can think of is that the membership provider isn't set up on the Web Application you've deployed to. Either way, I don't think it will work, because I don't believe SharePoint's
membership provider has implemented the method.