Disposing issue
in [CSharp]
|
From: Peter Duniho on 4 Feb 2010 13:59 Mr. Arnold wrote: > I am going to tell you again dummy. Ah, yes�resorting to insults always helps your case. > It's code owned by the DoD, and I am > not posting it. No one is asking you to. > And besides stupid, More insults. Way to go! You're really getting traction now! > I have been posting from home for > the last couple of days after getting out of the hospital this past > Monday So what? Is that supposed to excuse your poor behavior? > Jesus. I appreciate the compliment, but you go much too far.
From: Mr. Arnold on 4 Feb 2010 14:23 Peter Duniho wrote: <snipped> <pfft> Jesus <pfft> It over man move on.
From: Andreas Huber on 4 Feb 2010 16:46 "Mr. Arnold" <Arnold(a)Arnold.com> wrote in message news:%237SQ7ibpKHA.1548(a)TK2MSFTNGP04.phx.gbl... >> Well, your previous post very clearly claims that returning from the >> middle >> of a using block will *never* call Dispose. This is demonstrably false >> and >> you could have found that out yourself with a very simple test case. Just >> like with your "damage control" claim above you've obviously failed to >> consider all of the evidence before coming to your conclusion. > > Well, I am going to standby my claim about it. One shoe doesn't fit all > situations. The Using statement is suspect. Yep, you've already said that. Any comment about your "damage control" claim? > Just like the Using statement didn't do a finally on WCF Web service calls > in an iteration of more than five WCF calls to a WCF service wrapper. It > didn't Dispose or close anything and left the connections open. And on the > sixth iteration, the WCF aborted on timeouts on no more connection > available - of 5 connections simultaneously the default Prove it! And do spare us with your "the DOD owns the code" excuses. If the using statement behaved as you claim it does, you'd be able to write a repro in under an hour. By the way, a little bit of Googling would have shown you that WCF Dispose methods sometimes throw exceptions. As pointed out by others, this would perfectly explain the effects you are seeing, but is in no way attributable to the using statement or try-finally blocks. Oh, and let me make this cristal-clear: A Dispose method that can throws is buggy. > That's all I have see to know that the finally is not being exceuted as > you say it is 100% of the time. You're jumping to conclusions, *again*. I've never claimed that. I said: "Well, your previous post very clearly claims that returning from the middle of a using block will *never* call Dispose. This is demonstrably false and ....". As others have already pointed out, there *are* cases where Dispose is not called, e.g. when you kill a thread from unmanaged code or when the runtime encounters a fatal error. These most likely do not apply in your case however. The effects you are seeing are much more likely caused by a bug in your own code or a buggy Dispose implementation. > I am not testing anything, as I have already seen the Using statement not > do what it's suppose to do, and I find it suspect. See above, a bug in your code or a buggy Dispose implementation is much more likely.
From: Mr. Arnold on 4 Feb 2010 18:26 Andreas Huber wrote: <snipped> Move on man its not my code to begin with, it was in my face and I fixed it running on the DoD network, which doesn't allow me to breach my security clerance posted some code in this NG. Understand this, you are nobody of any importance to me. and I don't dance to your tune or any one's tune in a NG. You're not putting any money in my pockets only your lip service so disappear and move on.
From: Andreas Huber on 4 Feb 2010 19:13
> Understand this, you are nobody of any importance to me. and I don't dance > to your tune or any one's tune in a NG. And I did not expect you to, you're claims are simply indefensible. > You're not putting any money in my pockets Right, just like everybody else in this NG. Why do you even post here? > only your lip service "lip service"? Besides a good .NET reference, obviously you should also add a dictionary to your bookshelf. > so disappear and move on. You don't put up but I should disappear just because you say so? Right. |