It sounds like you're referring to what The Pragmatic Programmer calls passive code generation.

Passive code generators save typing. [...] Once the result is produced, it becomes a full-fledged source file in the project; it will be edited, compiled, and placed under source control just like any other file.

Uses:

• Creating new source files
• Performing one-off conversions among programming languages
• Producing lookup tables and other resources that are expensive to compute at runtime

I would put the generated source files for any of the following:

• If you're planning to modify the generated C# code
• If you want to avoid having to generate the code before running in dev environments? E.g. if a tool must be installed to do the generation
• If the generation process is lengthy

It sounds like you're referring to what The Pragmatic Programmer calls passive code generation.

Passive code generators save typing. [...] Once the result is produced, it becomes a full-fledged source file in the project; it will be edited, compiled, and placed under source control just like any other file.

Uses:

• Creating new source files
• Performing one-off conversions among programming languages
• Producing lookup tables and other resources that are expensive to compute at runtime

I would put the generated source files into source control in any of the following situations:

• If you're planning to modify the generated C# code
• If you want to avoid having to generate the code before running in dev environments? E.g. if a tool must be installed to do the generation
• If the generation process is lengthy

It sounds like you're referring to what The Pragmatic Programmer calls passive code generation.

Passive code generators save typing. [...] Once the result is produced, it becomes a full-fledged source file in the project; it will be edited, compiled, and placed under source control just like any other file.

 

Uses:

 

• Creating new source files
• Performing one-off conversions among programming languages
• Producing lookup tables and other resources that are expensive to compute at runtime

I would put the generated source files for any of the following:

• If you're planning to modify the generated C# code
• If you want to avoid having to generate the code before running in dev environments? E.g. if a tool must be installed to do the generation
• If the generation process is lengthy

It sounds like you're referring to what The Pragmatic Programmer calls passive code generation.

Passive code generators save typing. [...] Once the result is produced, it becomes a full-fledged source file in the project; it will be edited, compiled, and placed under source control just like any other file.

Uses:

• Creating new source files
• Performing one-off conversions among programming languages
• Producing lookup tables and other resources that are expensive to compute at runtime

I would put the generated source files for any of the following:

• If you're planning to modify the generated C# code
• If you want to avoid having to generate the code before running in dev environments? E.g. if a tool must be installed to do the generation
• If the generation process is lengthy