Now we are just starting an ASP. NET 1.1 project, because one of the customer's requirements is that some user authentication information needs to be integrated with the customer's current ad authentication, the first thing that comes to mind is ASP. NET 2.0 is a very convenient feature, membership, because the Provider Model patterns is used, it is very convenient to insert a Custom User Authentication Mechanism in the system. Why not implement it in ASP. NET 1.1? Then I thought that since membership was implemented, it would be better to implement roles and personalization together and take full advantage of 2.0.
At the beginning, there were plans to use the existing authorization and profile Application Block in the roles and personalization blocks, but after carefully studying its built-in Quickstart, I feel that the East and East are too heavy and inflexible. Very strange. I personally think the design of ASP. NET 2.0 is much better than that of the PAG group for Application Block...
Finally, we recommend a very cool MS release site, werock247.net, to learn the site that cannot be missed in smartclient development!