Is Maverick. net easy to use?

After reading the MVC documents for a few days, I still don't know how to implement the MVC application under. net. I have a few questions:
1The basic idea of MVC is easy to understand (not to mention understanding), but how to implement MVC, theoretically, code-behind achieves the separation of C and V in a sense. how to embody the MVC Architecture under. net
2Does Asp.net need to use the MVC Architecture? It's hard to say.
Anyway, I think it is a little lame. These dynamic pages can be defined in resources or placed on the web. in config, there is no need to develop something similar to struts. It is difficult to maintain simple and clear event programming.
In particular, we can see the messy view of the demo in Maverick. net. What is the difference with the previous ASP style? Can it be done by an artist ?? It seems that it is not easy to process An ASPX file.
3In the ASP. NET architecture, whether a "pure" MVC framework is required is still a topic of debate.
Maverick. NET and UIP make the development process more complicated, clearer, or uncertain.
4What is the difference between structs and structs in Java (I have never engaged in Java)
5In the spring development guide, I talked about the relationship between spring and MVC, But how should I understand it?

Attached to maverick.net-1.1.zip download

Part of the content is transferred from the perspective of life Maverick. Net (original)

Put it on the homepage first. If Dudu thinks it is inappropriate, cancel it.