Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
MVC (Model-View-Controller) is a software architecture pattern that enforces separation of concerns.
3
votes
Accepted
Slower Ajax Response
"Design patterns, such as MVC and others are NOT a religion, they are there to serve as pointers on how things have worked well in the past, and how you might want to apply them in the future." …
2
votes
Accepted
Choosing between the view and the controller for my code
If your using MVC, and I assume (Judging by your description) the Model Binding syntax, where your forms are generated using Razor and the HTML Helpers, then your already half way towards letting MVC do … There are 2 main strategies when it comes to ASP.NET MVC.
Strategy Number 1 - Use ONLY the flattened models and properties you need to use. …
9
votes
Accepted
Entirely separate business logic layer from MVC
Even if your NOT using MVC, adopting this strategy is win/win , even for WPF, Webforms, Winforms and much more. … If you do it correctly then the MVC portion essentially becomes a brain dead display of what the business layer is doing, and the ease with which you can remove your MVC app and put another UI on in it's …