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
It is talking specifically about T4 templates which are separate from this project. However, from a Visual Studio/MSBuild perspective, this would seem the appropriate mechanism to generate C# classes just prior to the compilation of regular project sources, so that the generated sources can be compiled in. With that said, I don't see anywhere in the documentation discussing support for the use of JSchema ToDotNet functionality with MSBuild as part of Design-Time codegen.
Is this supported or planned?
The text was updated successfully, but these errors were encountered:
solvingj
changed the title
Appropriate way to execute as a "pre-build
Execute codegen using ToDotNet library as a "pre-build" event
Mar 17, 2019
solvingj
changed the title
Execute codegen using ToDotNet library as a "pre-build" event
Design-Time codegen using ToDotNet library
Mar 17, 2019
I was able to take another approach and create a custom target as shown below.
Of note, it would be really amazing if the Nuget package included a first-class Json-To-Dotnet MSBuild Task. It would be very little additional effort.
This fairly recent article describes the use of codegen in a build process:
https://docs.microsoft.com/en-us/visualstudio/modeling/code-generation-in-a-build-process?view=vs-2017
It is talking specifically about T4 templates which are separate from this project. However, from a Visual Studio/MSBuild perspective, this would seem the appropriate mechanism to generate C# classes just prior to the compilation of regular project sources, so that the generated sources can be compiled in. With that said, I don't see anywhere in the documentation discussing support for the use of JSchema ToDotNet functionality with MSBuild as part of Design-Time codegen.
Is this supported or planned?
The text was updated successfully, but these errors were encountered: