Is there any reasons to prefer SparkViewEngine over XSLT (or vice versa) for a standalone email gene
Posted
by Stephane
on Stack Overflow
See other posts from Stack Overflow
or by Stephane
Published on 2010-05-24T14:14:08Z
Indexed on
2010/05/24
16:01 UTC
Read the original article
Hit count: 363
I have a service that receives an object containing all the data needed to build a newsletter. I need to be able to generate the email using different templates. I don't want to involve the whole ASP.NET stack for that, so I want a separate templating engine.
Reading a lot of opinions, I have found that XSLT was not getting very much love when it comes to templating engines. Why?
SparkViewEngine is a "new cool toy", but it seems mature enough considering the number of projects that have been built with it. What do you think?
Did you used those 2 engines? in which situation, and what strength/pain did you enjoy/endure
© Stack Overflow or respective owner