asp.net mvc - ASP.MVC: Implementing a non-templated view engine? -
I have ASP I am quite new to MVC. For our new web application, I am considering visual options for two engines:
- Some of the available visual engines (default one, envolcity, braille, etc.) Generator as using.
- Implement application-specific C # DSL to generate HTML code so that the code code of the main code is stored in C # sections (using some sort).
The idea behind 2. Every time a new view is required, the need to write a direct HTML code will be reduced, but I'm not sure that this is a good way. One drawback of this is that it will not be possible to change the generated code without composing the project again.
What do you think?
I have seen the approaches used in other such projects, and in general they are of much value Are more upset than in comparison. The flexibility to lose you, the cost of paying for freedom of the generation phase is very high. Think about how many requirements apply only in a special case, and now imagine how you should handle it. In addition, if your thoughts are causing you too much pain, then I would suggest that you do not use ideas correctly. You should see very few repetitions in your thoughts on the site. Common pieces should be reprinted in different parts and pulled from there, for example.
Comments
Post a Comment