Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In a pre-WCF .NET (C#) web service, I have an expensive IDisposable resource that I’m holding a static (actually ThreadStatic) reference to. (Internally it holds a SqlConnection.) How can I insure that this is disposed when the app pool refreshes, should I simply suppress the FxCop warning and not worry about it, or is there a third option?
Originally the service opened the connection on each request with a using block, but that design was rejected due to a “connection resource issue.”
This design will be rejected due to a connection resource issue. If you had problems before, you’ll have them again, since you will now be using more SqlServer connections (if it’s thread static, then each thread will have one SqlServer and – more importantly – one underlying real connection, even when it’s not using the connection and would have returned the underlying connection to the pool).