sandord / subspace.texttemplating Goto Github PK

This can be accomplished, for example, by removing the context argument from TransformText and TransformFile and have these methods take a properties argument which accepts an anonymous type like the following:

new { Context = myContext }

and

new { Context = myContext, SecondProperty = myInstance }

This style is not supported by T4 and an argument for dropping it may be to stay as close to T4 as much as possible.

Change the script generators to use a CodeDomProvider

By implementing a caching mechanism, performance can be greatly improved because templates will not have to be compiled anymore every time they are transformed.

The inherits attribute allows specification of a base class for the generated template class.

The AppDomain assures that the assembly can be unloaded (by unloading the AppDomain itself) so under certain circumstances, this may be an advantage. In addition, it provides AppDomain separation, which may be desirable under certain circumstances.

List the additional features as well.

Add support for Visual Basic

This is probably better than loading the generated assembly in the current app domain as there is no way of unloading it.

Visual Studio 2010 SP1 adds support for T4 template inheritance, reflect that implementation.

This notation implies a <%= %> with automatic XML entity encoding.

A build script should be available.

Currently, a lock is held on the assembly cache and the compilation and execution stages. This means that multiple threads cannot perform transformations simultaneously. This is particularly hurtful for performance in web scenarios.

Implement unit tests that compare the output of T4 templates that are transformed by Visual Studio with the transformation output generated by this library.