Having logged a suggestion a few days ago I've had answers to some of my questions about the ASP.NET 2 support, which I'll try to summarise without garbling too much:
- LoweredApplicationName (or something like that) - The purpose of this is to enable an indexed value to be used in queries, since you lose the ability to take advantage of an index on the column when applying a Lower() function to it. Sounds fair enough to me - admittedly sites that don't have a lot of members/registered users/whatever won't get a lot of benefit from using the index anyway, but the benefits for those who do would outweigh that.
- Website Administration Tool support for adding Windows users to roles - may be seen in future, there are reasons for omitting it relating to customer perception (e.g. some people would be nervous at the thought of this sort of tool having access to their user list).Plus the tool wasn't intended for large scale purposes (that sentence is amazingly clumsy, but I'm tired so my language skills are dropping off). In addition, Windows users can be added to roles programmatically (I started looking at the docs on this just this morning, I hope to have a nice code sample soon - I know how to do it the old ASP.NET 1.x way, but this is so much cooler), so it's really up to us to handle it how we want
- Associating roles with a specific application name - you have to set it up in your web.config file. Once again, fair enough.
Neil Cowburn has some nice coverage of the new Class Designer on his blog, with good screenshots.
If you check the “Screenshots” gallery on this page there's also a small example that I perpetrated this morning