Whenever a new service is created there are some generated classes that are generated equally. Those classes might be extended (but this is probably rarely)
So they might be pushed into the Arc4u instead of being generated every single time from scratch.
It should be checked, if some, most or all those classes can be pushed to the Arc4u, instead of being generated multiple times.
Here again: central enhancement for new features would be even easier, because they could be included in a new release, instead of a regeneration
Whenever a new service is created there are some generated classes that are generated equally. Those classes might be extended (but this is probably rarely) So they might be pushed into the Arc4u instead of being generated every single time from scratch.
Those classes are for example
Customer.ProjectName.ServiceName.Facade.EnvironmentControllerCustomer.ProjectName.ServiceName.Domain.EnvironmentInfoCustomer.ProjectName.ServiceName.Domain.DatabaseInfo(which should be placed inside it own file anyway --> see StyleCop)Customer.ProjectName.ServiceName.IBusiness.IEnvironmentInfoBLCustomer.ProjectName.ServiceName.Business.EnvironmentInfoBLIt should be checked, if some, most or all those classes can be pushed to the Arc4u, instead of being generated multiple times. Here again: central enhancement for new features would be even easier, because they could be included in a new release, instead of a regeneration