Nice article: I've had to create HTML emails from SS for a while and have had to do all of my work in stored procedures.

I'm curious, have you considered doing the XML/XSL-T work in the script task instead? If the code was all self contained in the task, then a more generic use of it would expand the possible application. Imagine a FOR EACH task looping through a series of queries that had to send a series of different emails to different end users. The loop could collect the content (XML) and based on what that content was grab the XSL needed. Pass those two variables into the script (along with To, Cc, etc) and let the task do the rest.

I wonder which approach would be less resource intensive?

Anyway, thanks for the article, it will prove helpful in the near future.