Added ModuleCreator template for External (Partial, Code-Behind)

[Jayson-Furr]

I have added a partial/code-behind copy of the external template. I have thought about creating a new module creator to generate multiple entities and their respective services based on a list, separate from the module name, specified in the creator. Does this sound like a good idea? Or, are modules based on single entity by design?

[dnfadmin]

All CLA requirements met.

[sbwalker]

@Jayson-Furr the purpose of the Module Creator in the framework is to provide developers with a basic functional starting point for module development - so the fewer number of options the better or else it becomes confusing and defeats the intended purpose ( some would argue that even having 2 templates - Internal and External - is too confusing ). In addition, each new template requires ongoing maintenance as the framework is improved over time. My opinion is that it would be awesome to have a more advanced Module Creator... but it should not be in the core framework. It should be created as a custom module that can be installed through Module Management similar to the Blog module.

[PavelVsl]

The best solution would be to create a standard dotnet new template
https://docs.microsoft.com/en-us/dotnet/core/tutorials/cli-templates-create-project-template.

[sbwalker]

I agree that support via the .NET CLI or even a custom Oqtane CLI ( ie. "oqtane new ..." ) would be a great addition to the project.

[Jayson-Furr]

I think the CLI would be a great addition.