Option to Generate DbContent and Entities in Different Locations

As of v2.1 EF Core tooling has a --context-dir option which allows generation of DbContext and Entities in different locations. It would be nice to have both --output-dir and --context-dir options via the UI for EFC PT.

[ErikEJ]

I meant;

In project A, launch Power Tool, Rev Eng, select tables, select to only generate DbContext.

In project B, launch Power Tool, Rev Eng, select tables, select to only generate Entity Types.

Done

(I need the project reference, in particular for .NET Framework projects, in order to add the files.)

[tonysneed]

Yes, so instead of a single text box for “Project Path”, you would have two text boxes: “DbContext Path” and “Entities Path”. You would want to disable one or the other if they select the option to generate DbContext only or Entities only.

The user could specify just a folder name for either of these, which would indicate folders within the current project, for example, Context and Models.

Or the user could enter a relative path for the Entities Path, pointing to another project within the same solution, for example, …\MyApp.Entities. In that case, the DbContext Path would default to “.” for the local project. The beauty of this is that entities can be output to a NET Standard library, which can be referenced by a project that has repository interfaces and has no dependency on EF Core or any other persistence stack.

See this repo, which I repurposed to demonstrate the kind of project structure which separates entities from context.