Alex Homer has written a 3-part article series on Design Patterns in ASP.NET 2.0.
I don’t agree with everything in the article. For example, I (et al.) don’t consider the code-behind model a valid implementation of the Model View Presenter pattern. Just because some presenter and view code is physically separated into different files does not change the fact that logically they are the same class and generally tightly coupled to each other.
Another point I disagree on is Alex’s implementation of the Singleton pattern, which does not look thread safe to me, especially when you can get the safety for free in .NET using a static readonly property and a static constructor.
What I did find helpful in the article is the plain language explanation of the patterns concerned and the areas where they can be applied to .NET.