At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
Is Entity Framework 6 agnostic enough different sql server and OS platforms?
It’s my first time using sql server, I usually go with MySQL, so I’m unsure how to do this.
Is Entity Framework 6 agnostic enough different sql server and OS platforms?
It’s my first time using sql server, I usually go with MySQL, so I’m unsure how to do this.
Is Entity Framework 6 agnostic enough different sql server and OS platforms?
It’s my first time using sql server, I usually go with MySQL, so I’m unsure how to do this.
In what situation do Entity Framework enums become useful?
I am working on a project where there will be plenty of static options being stored in the database. I looked at using Enums for this, but do not see how they could be useful.
In what situation do Entity Framework enums become useful?
I am working on a project where there will be plenty of static options being stored in the database. I looked at using Enums for this, but do not see how they could be useful.
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