Thanks a lot for the quick answer. I'm using session per conversation pattern in a WinForms MDI app and since there are customers having CAL licensing for MSSQL server the number of connection that the application is opening is critcal. No multithreaded involved.
I have to admit I had completelly forgotten about ADO.NET connection pooling since I started using ORMs :) I also missed the fact that there is out there (in NH) an connection release mode and it defaults to AfterTransaction which basically means that only one connection will be used in a single threaded app. Thanks again Dan -- 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.
