I know that you don't want to explain, but if connection pooling is causing an issue with your tests, don't you think it is doing its job? How can you be sure that the problems you are facing are not also going to happen in production?
Thanks, Shawn Wildermuth Wildermuth Consulting Services, LLC http://adoguy.com http://wildermuthconsulting.com Microsoft MVP (C#), MCSD.NET, Author and Speaker -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Andy Smith Sent: Friday, February 16, 2007 3:33 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: [ADVANCED-DOTNET] Diable Connection Pooling for an Entire Process? Hi - I'm working with unit tests, and for a particular reason (won't bore you with the details, has to do with timing issues when killing connections during tests), I'd like to disable connection pooling for the entire process that the unit tests will run under. I know it's possible to set Pooling=false in the connection string, but that would entail a change to code that I'd rather avoid, since it only applies to when a unit test is running. Anyone know if it's possible to disable connection pooling for an entire process? Thanks! Andy =================================== This list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
