Why LoginView is designed wrong
...or if it's not designed wrong, it addresses the wrong business problem.
Every ASP.NET developer has been there before. Some sections of a form should be shown to some people or anon users. You probably tucked the portions of UI into Panel controls and set their visibility properties based on the login status of the user.
So along comes LoginView, presumably to address this problem, only the controls within each template can't be accessed. As someone mentioned in my previous entry on the subject, this is by design. The controls are created after the PreRender event.
That's a pretty stupid design.
At that point, I can't do anything with the content inside of them. Postback events have long since fired. Honestly, how is this useful? Some might argue that it's like the controls you create in a grid or repeater, but this isn't like that at all because you'll never have the same template rendered more than once in a LoginView.
I sure hope they change this before the next beta.