using-statement

I asked a question regarding returning a Disposable ( IDisposable ) object from a function , but I thought that I would muddle the discussion if I raised this question there. I created some sample code: class UsingTest { public class Disposable : IDisposable { public void Dispose() { var i = 0; i++; } } public static Disposable GetDisposable(bool error) { var obj = new Disposable(); if (error) throw new Exception("Error!"); return obj; } } I coded it this way deliberately, because then I call: using (var tmp = UsingTest.GetDisposable(true)) { } Using the debugger, I notice that the Dispose

I have started to use classes implementing IDisposable to write blocks in streams, with the using statement. This is helpful to keep a correct nesting and avoid missing or wrongly placed start/end parts. Basically, the constructor writes the start of a block (e.g. opening XML tag), Dispose() the end (e.g. closing XML tag). Example is the UsableXmlElement below (it's for large XMLs, so LINQ to XML or XmlDocument in memory are no options). However, these IDisposable do not implement the sophisticated pattern recommended by Microsoft, with Destructor/Finalizer, separate Dispose(bool) method and

I really want to get this out of my head. Please see below code: using (DataTable resultTable = DBUtility.GetSingleDBTableResult(connectionString, "SELECT * FROM MyDBTable")) { List<string> resultsList = new List<string>(); foreach (DataRow dataRow in resultTable.Rows) { resultsList.Add(dataRow[0].ToString()); } return resultsList; } Is the datatable disposed? Can someone explain how this is translated to a try/catch/finally block? MSDN states that if an exception occurred, the Dispose method will still be called but what about the return statement? Or should i just use below code: List<string

This question already has answers here : Closed 8 years ago . Possible Duplicate: What happens if I don't close a System.Diagnostics.Process in my C# console app? As System.Diagnostics.Process inherits from Component which implements IDisposable , should I always create a Process with a using block? For example, this...: using (var process = new Process()) { process.StartInfo.FileName = "some process.exe"; process.Start(); process.WaitForExit(); } ...instead of this: var process = new Process { StartInfo = { FileName = "some process.exe" } }; process.Start(); process.WaitForExit(); I ask

This question already has an answer here: try/catch + using, right syntax 7 answers What is a correct approach try/catch inside using or using inside try/catch? using (SqlConnection connection = CreateSqlConnection(connString)) { using (SqlCommand command = CreateSqlCommand() { try{//open connection + execute command + do something else} catch{//do something} } } vs. try { using (SqlConnection connection = CreateSqlConnection(connString)) { using (SqlCommand command = CreateSqlCommand() { //open connection + execute command + do something else } } } catch { //do something } From my point of

There are several questions on StackOverflow regarding closing WCF connections, however the highest ranking answers refers to this blog: http://marcgravell.blogspot.com/2008/11/dontdontuse-using.html I have a problem with this technique when I set a breakpoint at the server and let the client hang for more than one minute. (I'm intentionally creating a timeout exception) The issue is that the client appears to "hang" until the server is done processing. My guess is that everything is being cleaned up post-exception. In regard to the TimeOutException it appears that the retry() logic of the