There is however a small issue with the way this is implemented, if you do a lot of template nesting, TextTemplating will append the relative path directories and then place them next to a #line directive in the code it uses to generate the output. The problem with this is that the #line directive has a maximum path length of 260 characters.

If like me you have includes which navigate up directories, this appended path can very quick exceed this length. For this reason I very much advise using the registry entry, even though this is not ideal with source control.

I wrote a batch script which will point the registry entries to the appropriate directory, dependent upon where the working copy is located.

In case it helps anyone, the statement “T4 does not support relative path references in nested templates” is now incorrect with the introduction of VS2010 which is very, very nice!!

I can get the location of the include file by scanning the ProjectItems collection and then using get_FileNames(0) but when I try to use a variable name in the include statement it fails.

My short question is: Is there a way to specify a variable file name in the include statement?

The Same file we can perform successfully through Visual studio.

Our code for custom host is as below:

CustomCmdLineHost host = new CustomCmdLineHost();
Engine engine = new Engine();
//Transform the text template.
string output = engine.ProcessTemplate(input, host);

It always gives the error as Loading the include file ‘D:\IncludedFile.tt’ returned a null or empty string.

As per the MSDN this error comes if the included file is empty, however its not.
http://msdn.microsoft.com/en-us/library/bb126242.aspx

Please suggest.

Kind regards ^_^

Anyway, Thank you very much for your speedy replies!