We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi Matt,
You opened my eyes to the inversion of control.
I would be great to see full DDD implementation or web api and soa?
Also, interesting to know has to abstract DI from the solution and which ones can produce similar results with?
Best regards, Alex
The text was updated successfully, but these errors were encountered:
Actually, I would be interested to see how would you approach to stop leaking of data layer entities into presentation layer.
So, pretty much how would you aggregated roots in service layer with your great ideas of using inversion of control approach.
I've been looking for all available examples and looks like they all mostly rely on the fact that you have fool control entities and data context.
What about scenarios when you building web api on top of other service or data source or both?
Just curious to sew how would you structure your application if you need to translate into your domain entities?
Sorry, something went wrong.
No branches or pull requests
Hi Matt,
You opened my eyes to the inversion of control.
I would be great to see full DDD implementation or web api and soa?
Also, interesting to know has to abstract DI from the solution and which ones can produce similar results with?
Best regards,
Alex
The text was updated successfully, but these errors were encountered: