Skip to content
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

RevEng: Command option for adding codegen template into project #2415

Closed
divega opened this issue Jun 18, 2015 · 1 comment
Closed

RevEng: Command option for adding codegen template into project #2415

divega opened this issue Jun 18, 2015 · 1 comment
Assignees
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone

Comments

@divega
Copy link
Contributor

divega commented Jun 18, 2015

We want customers to be able to easily add a package to enable reverse engineering of specific database engine and at any point switch from the default code generation provided by that package to using a template that becomes part of their application and thereon they can customize.

The idea came up in some brainstorming with @Eilon. He suggested that we could have an option, e.g. --customize for the reveng command line that will write the template file (originally stored as a resource in the assemblies of the package) into the project. Once the template is in the project the reverse engineering pipeline would know to use it.

The templates will be provider specific, but the --customize option should work across different reverse engineering packages. We should decide whether the template should need to have a specific name and be put in a specific location in the package. Hopefully there will be a way to specify a custom name in the command line but we should have a default.

cc @lajones

@lajones
Copy link
Contributor

lajones commented Jul 15, 2015

Fixed by #2598
Actual command dnx . ef revEng customize <provider_assembly_name>

@lajones lajones closed this as completed Jul 15, 2015
@rowanmiller rowanmiller modified the milestones: 7.0.0, 7.0.0-beta6 Jul 15, 2015
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
@ajcvickers ajcvickers modified the milestones: 1.0.0-beta6, 1.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Development

No branches or pull requests

4 participants