Posted by: Ken Getz
Since preparing the presentations for VSLive! Orlando on Membership and Profile, I've learned a few things (it's early beta software—there's always something new to learn!).
Three important issues:
1. This one is pretty obvious, but I didn't state it explicitly in my slide deck: If you create a custom provider for ASP.NET 2.0, that provider must be thread safe. My simple demonstration provider makes no effort to be thread safe, and is probably a menace to real Web sites.
2. Again, pretty obvious: Providers are, by their nature, stateless. You need to make sure that you don't count on preserving state between calls to the provider.
3. Not so obvious: The default providers (AspNetSqlProvider, for example) come "pre-configured." If you don't like the default settings, you can use the <remove /> element in an ASP.NET web.config file, and then use the <add /> element to add it back using the settings you want. I spent a long time trying to figure out how to modify the default configuration (and even submitted a bug against it) before figuring this out.
More to come, I have a feeling...
--
0
comments:
- Post your own comment
