Patterns

In this geekSpeak, Microsoft Most Valuable Professional (MVP) David Kelley discusses composite application development in Microsoft Silverlight and Windows Presentation Foundation (WPF). He covers the Silverlight Designer/Developer workflow, tooling, design patterns, anti-practices, and working…

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…

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…

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-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-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-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…

Extreme ASP.NET Makeover: Separation of Concerns – The Big Picture   Let’s summarize what we’ve done. We removed code from Page_Load using cut and paste, and we created two new classes. It doesn’t seem like much as far as refactoring is concerned. But that’s because we aren’t actually…

Extreme ASP.NET Makeover: Separation of Concerns – Principles to Practice   When looking at the code, the first thing that our attention was drawn to was the repetitive nature of the authorization code.  As you can see in the code in Figure 1, there are a large number of calls to…

Extreme ASP.NET Makeover: Separation of Concerns - Overview   Separation of concerns is a concept that, when applied to software development, deals with creating distance between dissimilar aspects of your code. This may seem like a complicated statement, but we all have dealt with it in…