Why Not ? services.AddAutoMapper(AppDomain.CurrentDomain.GetAssemblies());
I don't like creating any empty Interface or something unless I am planning to use that after I only create an empty interface to fill it later to stick my infrastructure
If you need such comment that is mean something goes wrong
I dont like empty interfaces or service locators
I wouldn't call this awesome, it's more like a "crutch" because there's no better way right now
Yeah that's terrible…
Why bother with a special type if Program suffices? How would you know if the library accepts any type or if it needs the entry point specifically?
c# should get rid of all this magic behind the scenes, it's terrible for anyone who doesn't know the secret how that works.
For such a usecase, Why we have to create a useless type and get assembly from it. I mean why can't we have easy things like typeof() or nameof() similarly assembly(this) or assembly("MyApi.Application") etc..
Horrible One more reason to stay away from that crappy libraries
Why Not ?
services.AddAutoMapper(AppDomain.CurrentDomain.GetAssemblies());
I don't like creating any empty Interface or something unless I am planning to use that after I only create an empty interface to fill it later to stick my infrastructure
If you need such comment that is mean something goes wrong
I dont like empty interfaces or service locators
I wouldn't call this awesome, it's more like a "crutch" because there's no better way right now
Yeah that's terrible…
Why bother with a special type if Program suffices? How would you know if the library accepts any type or if it needs the entry point specifically?
c# should get rid of all this magic behind the scenes, it's terrible for anyone who doesn't know the secret how that works.
For such a usecase, Why we have to create a useless type and get assembly from it. I mean why can't we have easy things like typeof() or nameof() similarly assembly(this) or assembly("MyApi.Application") etc..
Horrible
One more reason to stay away from that crappy libraries