Evaluate OutputFileName and OutputDirectory Item Metadata#197
Evaluate OutputFileName and OutputDirectory Item Metadata#197
Conversation
393d19b to
381de2d
Compare
|
@dotnet-policy-service agree company="dSPACE GmbH" |
|
Any blockers on this? Fixing the ignored extension directive inside of the template would be most welcome. |
Still waiting for someone to review. Unfortunately @mhutch hasn't been active here in months and it's unclear to me if Microsoft has completely given up on T4. |
I no longer work at Microsoft and am currently taking a break from software development to focus on metalsmithing. I intend to get back to maintaining this at some point, however I no longer have commit access (despite being the sole maintainer) so have forked it into my own GitHub account. |
This adds the missing functionality to evaluate Item Metadata from
T4TransformandT4PreprocessinT4.BuildTools.Furthermore, the
T4Preprocessitems have their namespace calculated automatically from their relative path; thereby mimicking the behavior of the legacy T4 external tool of Visual Studio.Also a bug has been fixed when a template itself defines the output extension via
<#@ output extension=".whatever" #>.This fixes the following open Issues:
The automatic namespace calculation may fix #183, although OP requests an explicit override; this could be resolved with further Item Metadata. I'm happy to implement this if required.