Hi,
Situation:
Recently I've had to implement MembershipProvider for our company's legacy Security Platform and because. Because I wanted to make it so that no legacy code become broken, I needed to add old classes too, but I decided to let those old classes consume settings from Membership provider section in config file instead of a different section for those settings (e.g. ConnectionString, etc.).
Problem:
The problem is that if you don't access provider prior to legacy security classes, and because it has not been yet instantiated, there is no settings available to the provider!
Might-be-solutions:
A- It maybe possible instantiating the providers at application startup, so that Initializing happens and everyone become happy (maybe except system memory ;) )
B- I even can check for static resources I'm going to use for being correctly initialized prior to use (which means I need a way to instantiate the provider manually)
Knowledge Background:
I kn ...
Go to the complete details ...