CODEWITHSUNDEEP
asp.netdesign-patternsc#-4.0n-tier-architecture
xplat
xplat

Reputation: 8636

Preferred presentation pattern for ASP.NET with option to build other UI technologies later?

I came with this mind problem lately when I discussed about a project involves various technologies such as WCF, EF 4 etc. So the idea is to keep a basic architerctural model, practises and layering, separation concerns and other stuff that should mind when you want to build something maintainable and testable.

So I came with this, what should I choose to implement when it comes to the presentation pattern? Maybe later I will need to use some of the layers to create a Windows Phone app to show some data from the service layer, or create a Silverlight client, a winforms client etc...

MVVM is presented better for Windows Phone, Silverlight the best option. MVP as the winforms suitable presentation pattern. MVC is best for ASP.NET Webforms? (seen some net examples using MVP for webforms).

[EDIT] Seems like a solution could be implement different approach for every UI and use tha same business logic and validation layer!

I guess you could use whatever you want...but is there anyone out there faced such a dillema? and what was he done about to solve it?

Thank you?

Upvotes: 1

Views: 97

Answers (1)

Davide Piras
Davide Piras

Reputation: 44605

See my answer here: MVC3 and Entity Framework

in fact depending on which UI technology or platform you would use details at the top are different but the rest of the layering will most likely stay the same...

Just a way to start with and get inspiration, ask more if you need other details.

Upvotes: 1

Related Questions