-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#line annotations no longer generated with relative paths with dotnet-t4 #152
Comments
I can see that this is because there is a new option However this defaults to |
There doesn't seem to be any way of controlling this from the dotnet-t4 tool. |
A workaround is to install version 2.2.1+650c1854cb explicitly. |
mwadams
added a commit
to endjin/t4
that referenced
this issue
Apr 19, 2023
…nerator. This enables us to (optionally) restore what was the default behaviour prior to v2.3.0. This commit resolves mono#152
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In our JSON Schema code generation project, we use T4 to generate code at build time.
There is a fair bit of code to generate, and we do this "one time" and commit the results to our repo, rather than running the template generation with every build, and check in the product.
We are currently running
T4 text template processor version 2.3.1+932110915c
from an orchestrating batch file which looks like this:The individual batch files contain a set of commands that look like this:
With previous versions of the dotnet-t4 tool (prior to 2.3.0), we used to get relative paths in the #line annotations.
But in the 2.3.0 and 2.3.1 versions we see
This is a problem for our scenario because it ties those annotations to the machine on which it was generated [and incidentally generates hundreds of spurious file changes when there are only small numbers of actual changes]
The text was updated successfully, but these errors were encountered: