Which design pattern in ASP.NET is more preferable and why?

Pranam Bhat

5y710Learn iOS Programming

Which "Design Pattern" in C#/.NET is preferrred more? and Why???

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Rajanikant Hawaldar5y ago
@Pranam Bhat, are you asking about Architectuaral Design Pattern or Design Patterns?

MVC, MVP, MVVM are architectural patterns which we need to decide before start project. After we start the project with or without architectuaral design patterns we use below patterns as per requirement to design. We use MVC with ASP.Net, WPF/winform with MVVM/MVP, MVC with WPF/winform etc and depends on need.

Creational Design Pattern :
Factory Method
Abstract Factory
Builder
Prototype
Singleton

Structural Design Patterns :
Adapter
Bridge
Composite
Decorator
Façade
Flyweight
Proxy

Behavioral Design Patterns :
Chain of Responsibility
Command
Interpreter
Iterator
Mediator
Memento
Observer
State
Strategy
Visitor
Template Method
0
Sachin Singh5y ago
This question doesn't make sense, design pattern is not something that you can decide before start working on the project.
I have seen, many developers, sometimes developers with many years of experience also ask this question, perhaps they don't know what is design pattern and what are their purposes.
Design patterns are well-tested methods that solve certain types of programming problems, specially oops problems.
For example, if you have a code where you are using multiple if-else, then this directly means that you are not utilizing the power of polymorphism better, so you can apply the RIP (Replace if with polymorphism pattern) there to solve the issue. Similarly, if you don't know which concrete object would replace the interface then you can apply factory pattern or DI.
So, design patterns are natural and they should come on demand.

also, don't mix design patterns with architectural patterns like n-tier. but, yes UOW and Repository is of course a design pattern.
+3