Correct way to inject dependencies in Business logic service?
Currently the structure of my application is as below
Web App –> WCF Service (just a facade) –> Business Logic Services –> Repository -> Entity Framework Datacontext
Confused on how to properly employ a Repository Pattern with Service/Business Layer on top
I’m building a ASP.NET Web Api 2 solution for learning purposes, and I’ve hit a snag. I was wondering if anyone could tell me what exactly it is that I’m missing.
Confused on how to properly employ a Repository Pattern with Service/Business Layer on top
I’m building a ASP.NET Web Api 2 solution for learning purposes, and I’ve hit a snag. I was wondering if anyone could tell me what exactly it is that I’m missing.
Confused on how to properly employ a Repository Pattern with Service/Business Layer on top
I’m building a ASP.NET Web Api 2 solution for learning purposes, and I’ve hit a snag. I was wondering if anyone could tell me what exactly it is that I’m missing.
Confused on how to properly employ a Repository Pattern with Service/Business Layer on top
I’m building a ASP.NET Web Api 2 solution for learning purposes, and I’ve hit a snag. I was wondering if anyone could tell me what exactly it is that I’m missing.
Confused on how to properly employ a Repository Pattern with Service/Business Layer on top
I’m building a ASP.NET Web Api 2 solution for learning purposes, and I’ve hit a snag. I was wondering if anyone could tell me what exactly it is that I’m missing.
How far can I drift from my original domain model and still have the benefits of an ORM?
I have the following domain models:
How far can I drift from my original domain model and still have the benefits of an ORM?
I have the following domain models:
Is it faster to query using linq-to-entities or a data adapter?
I’m creating an MVC application in VS2012 and I reverse-engineered the models from existing Oracle tables. The tables are part of a MASSIVE database. Besides the main tables that I need to insert, update and delete from I also (on a whim) selected a few tables and views that my application only needs to read from. Now I am doubting my decision and considering deleting the less-important models.
Is it faster to query using linq-to-entities or a data adapter?
I’m creating an MVC application in VS2012 and I reverse-engineered the models from existing Oracle tables. The tables are part of a MASSIVE database. Besides the main tables that I need to insert, update and delete from I also (on a whim) selected a few tables and views that my application only needs to read from. Now I am doubting my decision and considering deleting the less-important models.