Some programmers access their IoC containers with static class methods. Is it just a preference, or is it a requirement?
If my custom membership provider needs DataContext, how can I inject my DataContext into it without a static class?
My approach is to access my container via a static class inside of custom membership provider. Is it right solution?
If the static way is preferred, do I have to keep my base container in singleton scope and initialize it in Global.asax and always access my container via a static class?
A static Service Locator is just never a good idea. The ASP.NET Provider model suffers from the Constrained Construction anti-pattern, as well as a host of other issues. It’s better to avoid if at all possible (it usually is).