Useful software design patterns in .NET

Question

Can you share your most frequently applied (or favorite) software design patterns in .NET development? And why?

Please bear with me by asking such a generic question. I am not trying solve any problem specifically. Simply want to know what patterns are used more frequently to help solving problems we face daily.

Thanks for sharing your two cents.

Answer 1

What design pattern do you use the most? : All of them can be applied in the world of .NET.

Answer 2

• Composite pattern

Each object have 1 parent and may have n children.

• Controler pattern

On one side you have classe (DataClass) that represents the data, and on the other 1 classe that contains a list of DataClass (ControlerClass). Only this ControlerClass instanciate/modify/delete any object of DataClass.

• Singleton Pattern

Allo a class to instanciate only 1 object, by designing the constructors as private, and design a static getter that return either a new object, or the existing object

Many of pattern are used, but these one are really common.

Answer 3

There's a saying I once heard:

"The trouble with getting a new hammer is, everything starts to look like a nail"

This question appears to be asking for solutions, with little concern to what the problems actually are. Far too frequently people adopt favourite patterns, and apply them religously whether or not they are the best tool for the job.

If you want to start on design patterns though, I'd suggest by reading one of the many books on the subject such as the classic Gang Of Four book "Design Patterns" by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, ISBN-13 978-0201633610 or for a more C# flavour, try "C# 3.0 Design Patterns" by Judith Bishop, ISBN-13 978-0596527730.

Answer 4

Well if you include the built in ones, it'd have to be Iterator (Enumeration) and Observer (Events) :)

Answer 5

Besides the obvious Iterator and Observer, I would say:

• Strategy