repository-pattern

问题 I am trying to implement search functionality on a list of customers, the functionality is detailed in this tutorial on the Asp.Net site, http://www.asp.net/entity-framework/tutorials/sorting-filtering-and-paging-with-the-entity-framework-in-an-asp-net-mvc-application In my controller i have the following public ViewResult Index(string sortOrder, string searchString) { ViewBag.CustomerNameSortParm = String.IsNullOrEmpty(sortOrder) ? "CustomerName desc" : ""; ViewBag.PrimaryContactNameSortParm

问题 I'm creating a new project using MVC5 and plain ADO.NET (just as a learning exercise) and I need to create a repository that registers a model with several related objects that also need to be created at the same time and those objects in turn may need to insert other objects. The easiest solution I can think of is to have a massive method(in the repository) that receives an instance of the parent object(which contains all the related objects that needs to insert) and also have a single

问题 I'm creating a new project using MVC5 and plain ADO.NET (just as a learning exercise) and I need to create a repository that registers a model with several related objects that also need to be created at the same time and those objects in turn may need to insert other objects. The easiest solution I can think of is to have a massive method(in the repository) that receives an instance of the parent object(which contains all the related objects that needs to insert) and also have a single

问题 I had this code from a previous question, but its not compiling: public interface IEntity { // Common to all Data Objects } public interface ICustomer : IEntity { // Specific data for a customer } public interface IRepository<T, TID> : IDisposable where T : IEntity { T Get(TID key); IList<T> GetAll(); void Save (T entity); T Update (T entity); // Common data will be added here } public class Repository<T, TID> : IRepository { // Implementation of the generic repository } public interface

问题 With ASP.NET 5, there's already a DI shipped as default and it looks interesting. I have been using Autofac with MVC 5 which has the option to register all the assembly at once. Here is a sample code that register all the classes that ends with "Service" in Autofac. // Autofac Configuration for API var builder = new ContainerBuilder(); builder.RegisterModule(new ServiceModule()); ... ... builder.RegisterAssemblyTypes(Assembly.Load("IMS.Service")) .Where(t => t.Name.EndsWith("Service"))

问题 With ASP.NET 5, there's already a DI shipped as default and it looks interesting. I have been using Autofac with MVC 5 which has the option to register all the assembly at once. Here is a sample code that register all the classes that ends with "Service" in Autofac. // Autofac Configuration for API var builder = new ContainerBuilder(); builder.RegisterModule(new ServiceModule()); ... ... builder.RegisterAssemblyTypes(Assembly.Load("IMS.Service")) .Where(t => t.Name.EndsWith("Service"))

问题 Im trying to implement a UnitofWork pattern using this Scott Allen tutorial My current SqlUnitOfWork is the folowing public class SqlUnitOfWork : IUnitOfWork { public SqlUnitOfWork() { var connectionString = ConfigurationManager .ConnectionStrings[ConnectionStringName] .ConnectionString; _context = new ObjectContext(connectionString); _context.ContextOptions.LazyLoadingEnabled = true; } public IRepository<PhysicalTest> PhysicalTests { get { if (_physicalTests == null) { _physicalTests = new

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . Let's start with two quotes that sums this issue up: "Wrapping up DbContext is a leaky abstraction. No matter what, you'll end up in

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . Let's start with two quotes that sums this issue up: "Wrapping up DbContext is a leaky abstraction. No matter what, you'll end up in

问题 I have a base repository contract which other contracts extend, like follows public interface IBaseRepository<T> where T : class { IList<T> GetContents(); } and then there are other contracts which extend it like follows public interface IRepository1 : IBaseRepository<MyClass1> { } public interface IRepository2 : IBaseRepository<MyClass2> { } I implement IRepository1 as follows public class Repository1 : IRepository1 { public IList<MyClass1> GetContents() { //some code goes here } } similarly