Singleton

We’re now on the eighth installment of Extreme ASP.NET Makeover. In part 7, we examined the singleton pattern and refactored away the AuthChecker singleton. AuthorizationServices, which previously used the AuthChecker singleton, now depends on the IAuthorizationChecker interface and simply…

A Topsy-Turvy World The constructor signature for AuthorizationChecker now looks like this: public AuthorizationChecker( ISettingsStorageProviderV30 settingsProvider, IAuthTools authTools, IAclEvaluator aclEvaluator) { ... } We can clearly see that AuthorizationChecker depends…

Extreme ASP.NET Makeover: Death of a Singleton-Testability He’s Liked, But He’s Not Well Liked If the current code works, why do we need to get rid of the singleton? What harm is it doing? After all, there’s a reason the pattern has a name. It must be useful. We have a few issues with…

Extreme ASP.NET Makeover: Death of a Singleton-AuthChecker Class I’ve Got Some Seeds, Right Away So where should we start?  How about the AuthChecker class, since that’s what we’ve discussed through the first part of this article.  Earlier, we decided that there was no reason for it to…

Extreme ASP.NET Makeover: Death of a Singleton-Refactoring Now that we have a new class, complete with functionality, we can start to refactor other parts of the application to use it instead of the AuthChecker singleton.  Like all the other refactorings we’ve done thus far in this article,…

Extreme ASP.NET Makeover: Death of a Singleton-Overview Let’s review one of the changes we made to the code in part 6. In that discussion, we refactored the authorization checking into a separate class, AuthorizationServices. To do that, we moved a lot of code from the Page_Load method of our…