[Copied from an email written by Jess Chadwick]
I love the work you've done with RazorSingleFileGenerator, but I could not use it in its current state on either of the two projects I am currently working on because we are using custom Razor keywords and base classes not derived from the Razor WebPage
base class. I recognized that your project could be easily modified to support everything I needed, so I did so. I have two main changes:
1) I wanted to use RazorSingleFileGenerator to work with arbitrary template base classes (i.e. not Helper- or WebPage-based), so I added the "BasicHost" to support this. It eliminates all unnecessary artifacts and is slimmed down to support
the barebones Execute method. I'm not in love with the name and am open to suggestions. This is contained in the first two changesets and can be imported autonomously from change #2.
2) At my current client we are using an extended Engine to support our own custom keywords. To this end, I added the ability to locate and import custom ISingleFileGenerators on the fly. The config-file based implementation seemed simple and
effective, but I'm open to alternatives.
Overall I love your project and I hope that you'll accept these changes because I really think they are quite simple - and powerful - additions to help the tool better support many different scenarios. Please let me know what you think or if I can
do anything else to help!
- Jess Chadwick