In the current application I am working on I have a custom ControllerFactory class that create a controller and automatically sets the Elmah ErrorHandler.
I am reading nhibernate cookbook 3.0 and the fluent tutorial and I am kinda confused which one I should be using(cookbook by itself has many different ways)
Edit I would like to try to do what Remo Gloor has recommended Create a SessionFactoryProvider derived for Provider that retruns a SessionFactory using the code in OnApplicationStarted
I\'d like to get a IQueryable<User> being POCO. I have two functions in my repository which converts O/RM to POCO and vice versa. This works fine when saving or getting one user, but what about
Lets say I have an entity called User which has many Posts. My service looks like this for the deletion of a post:
I\'ve been search开发者_如何学编程ing for the \'right\' way to integrate repositories and unit of work into my project, yet I keep running across different variations.Some have the repositories as mem
In keeping with the Repository pattern of data input, I\'ve a question in regards to using inherited classes. For instance, suppose I would have the class...
I have created a repository class that I want to use in a code behind page. I\'m using constructor injection in the code behind page to instantiate the repository.
Psssst...! Read on, by all means.But I can tell you here that the problem had nothing to do with the DataContext, but with Dependency Injection.I have left the question up, as it documents one possib
I was wondering if building a repository on the top LLBLGen (adapter) is a good idea. I don\'t want to overengineer and reinvent the wheel again. The DataAccessAdapter class could be some kind of a ge