You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visual Studio peaks at the template directive's language argument to determine the default output extension. It uses .cs for C# and .vb for VB. If the language argument isn't specified, it assumes C#.
mono-t4, however appears to use .txt as the default extension. This requires me to specify the -o command-line option duplicating the input path and filename.
Changing it for preprocessed templates per #130 definitely makes sense.
However, I'd like to create a perception that T4 is for generating any kind of text, not just C#/VB.NET code, and keeping it as .txt would help with that I think?
Visual Studio peaks at the
template
directive'slanguage
argument to determine the default output extension. It uses.cs
for C# and.vb
for VB. If the language argument isn't specified, it assumes C#.mono-t4, however appears to use
.txt
as the default extension. This requires me to specify the-o
command-line option duplicating the input path and filename.Would you consider changing the default to align better with the Visual Studio tooling? Or would this be too much of a breaking change?
The text was updated successfully, but these errors were encountered: