In my ASP.NET MVC app, I have a fairly complex edit page which c开发者_如何转开发ombines a number of models into one view.
I have an application that is centered around a database (ORM is LINQ-SQL) that has a table called Assignment. I am using the repository pattern to manipulate the database. My application is basically
I\'m trying to implement the Unit of Work/Repository pattern, as described here: http://blogs.msdn.com/adonet/archive/2009/06/16/using-repository-and-unit-of-work-patterns-with-entity-fr开发者_如何学运
I\'m refactoring all my repository interfaces of various types. Most of them contain very similar methods like Add, Update but some have methods which only makes sense for a specific type. This is a b
I\'m trying to create a fake repository for unit testing with a class object that has a one to many relationship.I\'m using ASP.NET MVC and Linq to SQL.My reference is Steven Sanderson\'s \"Pro ASP.NE
We are about to start up a new project similar to a previous one. I could just copy the old design but I am not all too satisified with the old design.
The title might be a little misleading because I didn\'t really know what to call it. Here is my dbml and I am using the repository pattern to communicate between my application layer and my SQL layer
I\'ve read a lot about repository pattern implementation and I st开发者_如何学运维ill can\'t find out how should I implement entity projections querying?
We are trying to find out the best practice when using DDD and we are having some discussions on what makes the most sense or is the \"right way\".
I am building an application using asp.net mvc, DI, IoC, TDD as a bit of a learning exercise. For my data access I am using the repository pattern. Now I am looking at membership and how this can wor
加载中,请稍侯......