How does ENFORCED share issues in ASP.NET MVC?

Question

I have been studying, playing and working with ASP.NET MVC since preview 1 in 2007 (December). I have been a fan of this since 2008, and I support him all the way.

However, I continue to hear and read “ASP.NET MVC Provides a Strict Separation of Problems,” including reading it in Professional ASP.NET MVC 1.0 by Rob Konye, ​​Scott Hanselman, Phil Haack, and Scott Guthrie.

What I do not understand is enforcement . What if I define my controller with actions only with

return View();

and in the view (aspx viewer) am i doing everything? (data sampling, business logic, decision making, rendering, etc.).

How do I (ASP.NET MVC) ENFORCE separate me problems?

I think this is a blatant exaggeration, and it should read "suggests separation of concerns."

Can you convince me of this?

Answer 1

I do not think it imposes this, so they are probably mistaken. As you said, "offer" or "promotion" is the best word.

Answer 2

The main thing is that it starts on the right foot - that is, a separate controller and view. If you decide to do something crazy, nobody will stop you. In addition to reliable reviews. And common sense.

-, , .

Answer 3

, . MVC.

, , , . , .Net Rails.

Answer 4

" " ? , View ? - lint , MVC ( )?

Moreover, what would be the use of all these fingers? Are we not trying to write applications that our users like?