Have Geek Brain

What design pattern should I adhere to in order to develop an asp.net application?

There are many design patterns for developing an asp.net website. Each design template has its own pros and cons. I want to develop a high performance application using asp.net. Which scheme should I follow?

+1


a source to share


5 answers


The best practice I've seen today is to decouple all business logic from the presentation tier. Classic ASP.NET Webforms tend to make this a little more difficult and encourage lazy programming because you can use all events outside of the page rather than enforcing good code separation and single responsibility.

If you want to use the ASP.NET MVC framework, you will most likely have a framework that facilitates better coding practice. However, you can still find ways to revert to webforms coding style.



If you focus on the Single Responsibility Principle and ASP.NET MVC , you're about to get off to a great start. Domain Driven Design is also worth a look.

+2


a source


I would go with ASP.NET MVC.



+1


a source


This may depend on the goals and objectives of the applications. Will it be user-centric? Pretty / Ajaxy? SOAP service?

Design templates can help make life easier. If you are wrong, then it can make life more difficult. Architectural patterns, behavioral patterns, structural patterns, and data semantics can only be resolved in the context of an application of functionality that is ultimately inferior.

+1


a source


Model-view-controller (MVC) is the popular one used for developing this kind of thing

0


a source


There's a really good, free architecture guide available on patterns and methods. It goes into detail on many of the different patterns and where they can be used when developing an ASP.NET application (and many other types).

0


a source






More articles:


All Articles