This issue occurred again after upgraded to app-pro template to ver 2.1.1, even with license code configured in the appsettings.json
Resolved the issue, it seems missed the license code, the license code should be added with the moudle template.
when can support module template?
how to do db migration for a module application?the module application template not included a db migtator project
Hi@yekalkan,
Thanks for your cliarification, after I changed my network to another one, both module and module-pro template works fine via CLI, but before that module-pro template not work in the network.
BTW, some package references of moudle-pro template is older than the module template.
What is the different between the -t module and -t module-pro, the -t app and -t app-pro. Via the CLI, using -t module-pro creating a new module failed, but use the -t module succeed.
