This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 60
T4 VS Project Integration Error #77
Comments
Note that this bug only occurs on the initial creation of the generated files that are in nested folders. Once the folders are already added, the existing project integration works as designed. The above code fix will correct the initial folder additions to the VS project. |
Odd. You shouldn't be able to pick project folders that don't exist. How are you specifying those? |
They were initially created and then selected i the UI, but then I sometimes like to delete the whole Generated folder tree for a clean build. |
Aha! A loophole, eh? Fair enough... :-) |
Fixed in v1.3.0.4 |
msawczyn
added
pending release
Issue is resolved in the current codebase, will be published with the next release
released
Issue is resolved in a current release
and removed
pending release
Issue is resolved in the current codebase, will be published with the next release
labels
Jul 9, 2019
Closing since fix was released. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When nested folders are specified for the targets of the t4 generated files, the top level folder will be created, but if there are multiple sub folders under the main folder, only the first one will be created. This results in the newly generated files being added to the VS project under the xxx.tt template file.
Found the cause in MultipleOutputHelper.ttinclude. Initialization of bool found = false; is in the wrong place.
Please change:
To:
The text was updated successfully, but these errors were encountered: