Some information:
ASP.net MVC is primarily a paradigm shift in how you structure and develop ASP.NET applications. Moving from the "mentality" behind the code to most of the standard MVC Ruby on Rails, such as the mentality. I welcome it as a simulation tool for simple unit testing and code separation (although the embedded html code can be controversial).
Expression and XAML are a way to describe the level of presentation that can be simple for designers.
The question arises:
If we use ASP.NET MVC to develop our next website, how should a development team that uses Expression and XAML create (V) iews or integrate into the development flow?
More specifically, Expression users can still work in the ASP.NET MVC world?
Note that pages in the Expression model also use paradigm-based code.
source
share