67 votesHolger Hoffmann commented
It would also be necessary to have an option to skip the automatically generated BasedProxyClass.
If you providing the BaseProxyClass by a NuGet package or other project you don't need to generate it every time you add new proxy class. The BaseProxyClass is located in another assembly and should not be added to the project which contains domain/solution specific proxy classes.Holger Hoffmann commented
Another issue occurs if you are using multiple Assemblies/Projects to split your code in logical parts.
If your using a base library which contains the BaseProxyClass it will not possible to use this proxy class in another project.
If you generate a proxy class in this scenario then required namespaces are missing and must be included manuely in each generated proxy class. This happens because the namespace of the base library and the project containing generated proxy classes are different.
Please provide a configuration to define adtional namespaces to include in generated proxy classes.
The issue with INamingService could als be solved be providing a configuration based mapping to define different names for classes and properties.
At the moment the generation of proxy classes is not usable for projects. It may works for a single small project, but for companies with multiple projects and base libraries it's not comfortable.
Any feedback would be nice.
12 votesHolger Hoffmann supported this idea ·