I couldn't agree more then. Well, I personally don't use it, as I use Castle NHibernate Integration for resolving it. It's just since the OP has already used it, I choose to continue it from what he's done.
On Mon, Apr 30, 2012 at 3:18 PM, Ramon Smits <[email protected]> wrote: > As the OP is developing a Windows Service app, I think it's better to use >> CallSessionContext or "call", which internally use CallContext for * >> temporary* session storage. For a web app, "web" (or >> WebSessionContext) is better used, which internally use HttpContext for >> *temporary >> *session storage. >> > > Agreed, still, my opinion is that this method to resolve an nhibernate > session would only be used in scenarios where injection is not possible. > For example, I would not use this in MVC apps. > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > -- Regards, Maximilian Haru Raditya -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
