repository-pattern

Repository dependency? Lets say I have a domain that looks like the following: public class User { public int UserId { get; set; } public Lazy<Post> Posts { get; set; } } public class Post { public int PostId { get; set; } public User Poster { get; set; } } A user with my posts. How do I set up my repository so that for every user , it returns a list of Post and for every post , I get the Poster ? I have 2 repositories: public class UserRepository : IUserRepository { public IQueryable<User> GetUsers(); } public class PostRepository : IPostRepository { public IQueryable<Post> GetPosts(); } I

So I'm extremely new to ASP.NET MVC and Interface design. I've been asking a lot of questions and reading a lot of articles trying to make sense of it all. Due to a crisis at work, I have been called upon to do my best and learn this environment. And although it's been frustrating to grasp, I am slowly getting it. I have created an image in photoshop that shows my basic understanding of how the Repository Pattern works and why it's very much recommended. I'm trying to deploy this pattern at work and I want to make sure I get the major points I ask you to point out any glaring (not anal or

I have a Solution with several projects in it, including two asp.net mvc projects that share a Repositories and Models that live in a external assembly (also in the same solution). Essentially... Core/ -Repositories -Models Domestic.Web/ -Basic MVC Site, references the core project International.Web/ -Basic MVC Site, references the core project What I want to do is build a Silverlight 3 / RIA Services application for all the database admin. Thats fine except RIA Services (for the most part) is only really documented with the Entity Framework - you can find some info on Linq2Sql and even less

Namespaces omitted for brevity... I have written the following service provider and registered in config/app.php: class OfferServiceProvider extends ServiceProvider { public function register() { $this->registerLossControlManager(); } protected function registerLossControlManager() { $this->app->bind('LossControlInterface', 'LossControl'); } } Here is my LossControlInterface interface LossControlInterface { /** * @param int $demandId * @param float $offerTotal * @param float $productTotal * @param null|int $partnerId * @return mixed */ public function make($demandId, $offerTotal, $productTotal

I am struggling with my design (or over-design) of a web project I am doing. I have a MyProject.Data, MyProject.Business, and MyProject.Web DLL's. My data layer (EF6 based) contains my entities, db context. My business layer contains my repositories (yeah maybe not a true repo pattern). I have added IdentityFramwork to the Web Project, and of cource it creates ApplicationUser. I already have a User POCO in my Data layer. I would like to move the Application user into the Data layer, so I can use it in conjunction with other entities. One way to do this is have my Data.User extend IdentityUser,