Should I have separate units of work for each EF bounded context?
I have some EF bounded contexts like follows
Should I have separate units of work for each EF bounded context?
I have some EF bounded contexts like follows
Is it ok to have special domain factory – or something similar – directly in DAL?
In DDD application, I know that Domain Factory should be the single point of Domain object creation (input from the UI, the results of queries from persistence) – but I’m facing a problem that for very complex queries, we use stored procedures with multiple data sets – so data are translated to structures (classes) highly dependent on persistence implementation, e.g.
How do you apply Single Responsibility principle to a repository
I am trying to apply “SOLID” whenever I can and try to use common sense and avoid a pattern when I see that a pattern is creating more problems than it’s trying to solve. I don’t want to apply a pattern and make life difficult for somebody else using my code just for the sake “I write patterns” if you see what I mean.
Can tags be used as bookmarks under semantic versioning?
Shameless plug: this question is for StackMode – a StackExchange client for GNU Emacs 24+.
TDD with repository pattern
In my new project, I decided to try with TDD. And in very beginning I encountered a problem. First thing that I want to do in my application is to give ability to read data from data source. For this purpose, I want to use repository pattern.
And now:
TDD with repository pattern
In my new project, I decided to try with TDD. And in very beginning I encountered a problem. First thing that I want to do in my application is to give ability to read data from data source. For this purpose, I want to use repository pattern.
And now:
Is it good to split big repository into smaller ones to have separate history/issue etc or keep it big? [duplicate]
This question already has answers here: Choosing between Single or multiple projects in a git repository? (6 answers) Closed 8 years ago. We are currently porting our huge svn repo to git and we are thinking to export subdirectories of repository, each one containing source code of independent binaries, documentation or robot tests, into separate […]
Is it good to split big repository into smaller ones to have separate history/issue etc or keep it big? [duplicate]
This question already has answers here: Choosing between Single or multiple projects in a git repository? (6 answers) Closed 8 years ago. We are currently porting our huge svn repo to git and we are thinking to export subdirectories of repository, each one containing source code of independent binaries, documentation or robot tests, into separate […]
Is it good to split big repository into smaller ones to have separate history/issue etc or keep it big? [duplicate]
This question already has answers here: Choosing between Single or multiple projects in a git repository? (6 answers) Closed 8 years ago. We are currently porting our huge svn repo to git and we are thinking to export subdirectories of repository, each one containing source code of independent binaries, documentation or robot tests, into separate […]