Devart Forums

The integrated Entity Developer doesn't seem to have an option to initiate code generation or have it generate code on save. It used to I believe. It also does not write the connection string, although it does create the app.config file if it doesn't exist.

This is an EFCore model (EFML).

kentatcap wrote:The integrated Entity Developer doesn't seem to have an option to initiate code generation or have it generate code on save.

The code should be generated on saving the *.efml model.

kentatcap wrote:It also does not write the connection string, although it does create the app.config file if it doesn't exist.

Please double click the diagram surface to open Model Settings and make sure that the "Use the following connection string from App.Config" option is turned on. Does this help?

Shalex wrote:The code should be generated on saving the *.efml model.

It does not. I've been using the separate stand alone to force generate the files. See below screen cap right side Solution Explorer. The DTOs is there because I have some partials, but it should have created a Classes for the entities as set in the EF Core Template and Converters folder for as set in the DTOs template.

Shalex wrote:Please double click the diagram surface to open Model Settings and make sure that the "Use the following connection string from App.Config" option is turned on. Does this help?

This does not help either. See pictures above and below.

The .NET Core projects are currently not supported by Entity Developer. We will notify you when the corresponding support is implemented.

The .NET Core projects in Visual Studio 2017 are supported by Entity Developer: viewtopic.php?f=1&t=35436.