An interview with Krzysztof on the Framework Design Guidelines

Krzysztof was recently interviewed about framework design in general and the Framework Design Guidelines in particular.   

Inside framework design with author Krzysztof Cwalina


Here is my favorite part, we get this question all the time..   

SVB: How do design patterns often discussed in object-oriented circles relate to framework design?

KC: The Design Patterns community has concentrated on internal implementations, while the .NET Framework design guidelines originators have focused on the public surface of framework APIs. But there are similarities.
Both traditional design patterns and our framework design guidelines contribute to establish a common design language. Now, people have a common language. I think our guidelines continue [the work of design patterns] in the API space. For example, if I hear or read "Async Pattern," I know how it works, because there is a common language and consistency to the framework.


Comments (1)

  1. PiersH says:

    I’m not sure how one can say "Async Pattern" and "consistency" in the same breath. Take System.IO.Stream for example. In v1.1 BeginRead uses callback.Invoke() and BeginWrite uses callback.BeginInvok(), hardly consistent. And in v2.0 the model has changed completely to execute these operations in the ThreadPool drastically reducing the efficiency of methods such as MemoryStream.BeginRead.

Skip to main content