I do not want to spend a lot of time on something that does not have lot of support or no roadmap. Do we even have to worry about this view engines in the wake of vs2010/.Net 4.0?
views:
59answers:
3
+2
A:
Stick to the WebForms view engine and you should be fine. It's developed by Microsoft, it has decent documentation, it's the default view engine and it's partially tied to the WebForms framework which isn't going anywhere (at least not yet).
Mauricio Scheffer
2010-01-18 00:51:26
+2
A:
Umm, just use what you want that works today
Both Spark and NHaml are complete enough for production use
What special requirements do you have?
Spark markup is more like pure HTML
NHaml is just fun and geeky and quick
I wouldn't say that Spark *gives* more pure HTML. All the view engines can produce the same HTML. I *would*, however, say that Spark's syntax in itself looks more like HTML.
Eilon
2010-01-18 05:23:37
Duh. That's waht I meant
2010-01-18 22:52:05
Spark for the win!
Arnis L.
2010-01-18 23:09:26
+1
A:
There's no reason to worry about view engines at all ... you can always use the Microsoft view engine with no further consideration. IMHO, the only other view engine that is worthwhile for a large/production project is Spark. Regarding long-term support ... who knows. It's open source, and the creator has moved on to Microsoft. This could either be a good thing (i.e. possibly Spark features in future MS releases), neutral (no change), or bad (if he has little time to improve Spark due to time commitment.
Andrew
2010-01-18 05:15:58