How does server control violate the MVC design pattern?

The reason I ask is tvanfosson's (first) comment on his answer to another question of my question , where he said (about ASP.NET MVC): "the lack of control on the server side is due to the inherent separation of problems that make MVC a good template development. ".
Of course, I know ASP.NET server controls, and I think I know the MVC pattern, but I don’t understand how server controls break MVC.

Thank.

+5
source share
2 answers

Found an answer to Stephen Sanderson's "About the ASP.NET MVC 2 Framework" (p. 5)

"... (, ) (, ) .
".

0

, postback + viewstate + events.

, , . viewState, , , . , .

, -. , HTTP. asp.net, , , 1. URL-.

imho MVC asp.net MVC /. , , , -. , , /, ; , , , .

+1

All Articles