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
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
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
Results tagged with Search options answers only user 1204

MVC (Model-View-Controller) is a software architecture pattern that enforces separation of concerns.

3
votes
Having a Model and a ViewModel promotes separation of concerns by allowing your Model to work independently from the rest of your system. Have a look at the following architecture: {Database} --> {D …
answered Mar 24 by Robert Harvey
2
votes
The Model-View-Controller pattern is a UI pattern that follows a few basic principles: The View is a User Interface, a thin veneer in front of the Controller. The only logic that should be in the V …
answered Nov 22 '18 by Robert Harvey
3
votes
In MVC, the Model is anything that is not part of the View or the Controller. In MVVM, the Model is anything that is not part of the View or the ViewModel. That should be easy enough to remember. If … part of a UI abstraction, which is all MVC and MVVM really is. In other words, MVC and MVVM really have nothing to say about the Model, from an architectural perspective. The structure and …
answered Aug 4 '18 by Robert Harvey
1
vote
NotifyControllerChanges() should be an event, to which any controller in your system can subscribe. It would be part of the public API of your model, not an implementation detail. The model does not …
answered Oct 12 '17 by Robert Harvey
5
votes
Because business logic is not one of the responsibilities of controllers, and MVC is all about separation of concerns. You're not looking at this right. The whole point of MVC is to provide a … mechanism for managing your UI separately from your Model. By deferring all other concerns to the model, MVC is allowing you the freedom to architect your model any way you wish. …
answered Aug 4 '17 by Robert Harvey
2
votes
Because C# (and Java) uses references, the code private List<Role> roles; is perfectly valid. roles is a list of Role references; you're not storing copies of the original Role objects, or even …
answered May 1 '17 by Robert Harvey
1
vote
One way your {{ csrftoken() }} example can be implemented is by parsing the braces, reflecting over the underlying class to find the correct method to call, and replacing the braces and enclosing text …
answered Dec 27 '16 by Robert Harvey
1
vote
If you're calling the controller from the User screen, use the UserController. If you're calling the controller from the Contracts screen, use the Contracts controller. And if you're displaying a li …
answered Nov 3 '16 by Robert Harvey
2
votes
Your fundamental problem here is that you are storing formatted values in the database as strings. Don't do this. Always store the actual numbers as first-class values in the database instead. If …
answered Oct 25 '16 by Robert Harvey
1
vote
Model-View-Controller is primarily a User-Interface paradigm. It doesn't have much to say about your business logic. Rather, MVC provides separation of concerns between your business logic and the …
answered Sep 22 '16 by Robert Harvey
6
votes
You're going to have to embrace ASP.NET MVC in its own right. There is no server code-behind. There are no drag-and-drop widgets, no plugins, and no leaky page life-cycle. There is no almost … -wysiwyg: instead there is total, actual, complete wysiwyg. There is no SESSION; you'll have to live without it. There's no weird, busted markup. Best of all, there's no lies or deception: ASP.NET MVC
answered Sep 16 '16 by Robert Harvey
2
votes
DAO code goes into the Model, not the controller. DAO code is actually farther away from the controller than the business logic, and that logic doesn't go into the controller either. Write a layer t …
answered Jul 4 '16 by Robert Harvey
0
votes
The Model is everything that is not in a View or a Controller. That includes the ORM, regardless of whether it is Ruby on Rails, ASP.NET MVC or some other flavor of MVC. …
answered May 19 '16 by Robert Harvey
1
vote
. ASP.NET MVC has no responsibility whatsoever in the streaming process. The browser streams the video content directly. Further Reading HTML <video> element …
answered May 5 '16 by Robert Harvey
1
vote
The View is responsible for displaying data and accepting input from the user. The Controller is responsible for accepting requests and directing them to the proper method in the model for performing …
answered Apr 11 '16 by Robert Harvey

15 30 50 per page