How to use the unit of work and repository patterns in a service oriented enviroment
I’ve created an application framework using the unit of work and repository patterns for it’s data layer. Data consumer layers such as presentation depend on the data layer design. For example a CRUD abstract form has a dependency to a repository (IRepository).
Accessing Repositories from Domain
Say we have a task logging system, when a task is logged, the user specifies a category and the task defaults to a status of ‘Outstanding’. Assume in this instance that Category and Status have to be implemented as entities. Normally I would do this:
Patterns for a tree of persistent data with multiple storage options?
I have a real-world problem which I’ll try to abstract into an illustrative example.
Should unit test be in separated repository?
Should I put unit testing stuffs in a separate repository, not in the same repository as the programming library?
So I reference the programming library as submodule.
But most open source projects that I have seen do not organize the projects like what I mention above.
Can anyone explain which approach is better?
Are we using the repository pattern right?
We are using a bunch of separate classes suffixed with -repository to retrieve the data from the database; for each table its own repository.
In memory collection vs database vs individual classes for infrequently changed objects
I have a ASP.NET application which puts the users through a series of forms in a wizard like fashion and has them fill out fields on the form. In code, these forms and fields are represented as “Step” objects, with a collection of “Field” objects as properties.
Why do people fork repositories on GitHub? [closed]
Closed 9 years ago.
How do you get into the habit of using a repository (e.g. GitHub)?
Are there some best practices on the repository front, or some common newcomer-traps that I should avoid?
How do you get into the habit of using a repository (e.g. GitHub)?
Are there some best practices on the repository front, or some common newcomer-traps that I should avoid?
.NET MVC project architecture / layering
When planning the architecture for a mid-large scale MVC web application how do you implement the layers to be as decoupled as possible and easy to test? (basically follow best practices) Let’s say I’m using code first as my data access.