Revert integration of T4 code generation into project file #940
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit f669558 from merge of PR #776.
The integration required parallel builds to be turned off for MoreLinq. Since PR #776, more frameworks are being targeted and this slows the build down considerably, taking per target 5 seconds (on my machine) and a total time of approximately 44 seconds:
Reverting means that parallel builds can be enabled again and as a result, the total build time drop to approximately half:
The cost of integrating T4 (which is rarely invoked) does not seem to justify the cost of doubling the build times. There's a small inconvenience to having to remember keeping the generated code fresh if the template is change by invoking the help shell scripts if you're not using Visual Studio, where it happens the moment the template is saved. The freshness of the generated code is asserting during CI build
MoreLINQ/appveyor.yml
Lines 79 to 83 in 62914fb