API show allow you to use a custom ITemplateResolver

[georgiosd]

It would make testing in LINQPad possible, not to mention the ability to use dependency injection.

Are you open to refactoring the code so that there is also a BuildService which is constructed?

[markkemper1]

Always open to refactoring . Can you provide a code example of how you would like to use the api?

[georgiosd]

I haven't looked at the code base in depth but I was thinking something like:

ITemplateLoader which is an interface that allows the engine to load templates. The default implementation would inject a default implementation ITemplateResolver.
Then there would be a BuildService that injects an ITemplateLoader and can build emails.

This would allow the following use cases plus backwards compatibility:

• Use Injection of BuildService in own code with a custom binding of ITemplateLoader to say, load templates from a DB
• Use Injection of BuildService in own code with a custom of ITemplateResolver to use a custom way to locate the template on disk
• For compatibility, in your static methods, you would construct the default versions of the above and leave them as-is

Thoughts?

[georgiosd]

#4