ASP.NET MVC Framework ASP.NET MVC Framework (Part 1) Use the ASP.NET MVC Framework to Write Web Apps without Viewstate or Postbacks마소가 또 이상한거 만드네. 흠좀무..
기존의 ASP.NET 모델과 좀 다르고, 오히려 Ruby on Rails라든지, 자바 진영의 수많은
이상한 프레임웍 쓰던 분들이 이쪽으로 넘어오게 만드는데 목적이 있지 않을까!?
그런데 .NET 프레임워크 3.5가 필요하다는 말이 있어서 흠좀무..
LINQ같은거 없앤 버전도 좀 내놔줘. 서버마다 2.0 까는것도 힘들다규.
뒤통수를 후려갈기는 리플 하나.
Hi Dan,
>>>>>> So you can use the existing ASPX,ASCX... views with declarative server controls, but if the server controls need viewstate and page lifecycle to work, what's the effect of having server controls in MVC based views ?
The views themselves are standard .aspx, .ascx, .master files - so there is still a code-behind class, and you can handle rendering events off of controls to cleanly separate view markup from view rendering logic.
In terms of declarative controls, the control model is the same for building controls - the difference is just that you can't use the postback feature. Logically this is like building a .aspx page today that doesn't have a <form runat="server"> control on it. So controls like and other controls work just fine - you'd just use a standard form post or <a href=""> url for post operations. 쒰!!!! 이건 또 뷰스테이트 안쓰는 모델이네
We'll also then have a set of MVC aware server controls that you can also use in these postback-less view pages. They'll integrate cleanly with controller based logic.
Hope this helps,
Scott
그럼 기존의 ASP.NET 모델은? - Model / View 모델이라고 하는군. 아무튼 흠좀무 흠좀무..
What is the MVC noise all about, anyway? Pt 1What is the MVC noise all about, anyway? Pt 2What is the MVC noise all about, anyway? Pt 3얘네 시리즈나 스프링노트에 번역을 해볼까. 물론 내가 공부하려는 목적으로.
