search

sjh37 / EntityFramework-Reverse-POCO-Code-First-Generator

EntityFramework Reverse POCO Code First Generator - Beautifully generated code that is fully customisable. This generator creates code as if you reverse engineered a database and lovingly created the code by hand. It is free to academics (you need a .edu or a .ac email address), not free for commercial use. Obtain your licence from
https://www.reversepoco.co.uk/
Other
700 stars 230 forks source link

Need namespace declarations for different sub-folder outputs #750

Closed nealculiner closed 2 years ago

nealculiner commented 2 years ago

Thank you for adding the ability to generate objects in separate directories in 3.60. However, I use separate namespaces as for example I put my PocoObjects in a completely separate project. I may use Foo.EF.Core for my main project where the .tt files are but I may use Foo.Models for the store for PocoObjects for various projects to reference as a class library. As a result I use a separate namespace for PocoObjects vs. Configuration. I suggest:

Settings.Namespace = Settings.NamespacePoco = Settings.NamespaceInterface =

If set as "" then it uses Settings.Namespace, if set.

I'm not sure if I could output the PocoObjects to a separate location such as @D:\Dev\Foo\Entities from the .tt file located in D:\Dev\FooMain. Then I don't to cut/paste the files once generated.

Thank you.

nealculiner commented 2 years ago

I'm confusing something here, hold on...I see we do put namespaces in as I'm doing further down. I tried eliminating one of my .tt files and had an issue, I'll see what I'm doing wrong. Disregard!!!