dispose

问题 I am getting this warning from FxCop: "'RestartForm' contains field 'RestartForm.done' that is of IDisposable type: 'ManualResetEvent'. Change the Dispose method on 'RestartForm' to call Dispose or Close on this field." Ok, I understand what this means and why this is what needs to be done... Except System.Windows.Forms.Form doesn't allow you to override either .Close() or .Dispose() , so what to do? Currently I'm running with this solution: private void RestartForm_FormClosing(object sender,

问题 So in my apps, I tend to create new instances of forms on the fly, then use Form.Show() to display them (non modal). private void test_click(object sender, EventArgs e) { var form = new myForm(); form.Show(); } However, Code Cracker tells me that these forms should be disposed. So, I wrapped them with the "using" statement, but then they close immediately after opening. using (var form = new myForm()) { form.Show(); } I don't want to use Form.ShowDialog() , because in a few instances I'm

问题 Something like: using (IDisposable disposable = GetSomeDisposable()) { //..... //...... return Stg(); } I believe it is not a proper place for a return statement, is it? 回答1: As several others have pointed out in general this is not a problem. The only case it will cause you issues is if you return in the middle of a using statement and additionally return the in using variable. But then again, this would also cause you issues even if you didn't return and simply kept a reference to a

问题 The .NET IDisposable Pattern implies that if you write a finalizer, and implement IDisposable, that your finalizer needs to explicitly call Dispose. This is logical, and is what I've always done in the rare situations where a finalizer is warranted. However, what happens if I just do this: class Foo : IDisposable { public void Dispose(){ CloseSomeHandle(); } } and don't implement a finalizer, or anything. Will the framework call the Dispose method for me? Yes I realise this sounds dumb, and

问题 If I have a method like this: public void Show() { Form1 f = new Form1(); f.ShowDialog(); } Do I still need to call dispose on the form even though it will go out of scope, which will be eligible for garbage collection. From some testing, calling this Show() multiple times .. at some point it seems like the GC collects it since I can see the memory spiking then it goes down at some point in time. From MSDN it seems to say you MUST call dispose when the form is not needed anymore. 回答1: In your

问题 I face a recurring problem in the code I write: modifying some global value (I'll use a registry value just as an example) and then trying to revert the modifications to original state. I thought I'd try to use IDisposable to solve this problem. When created, the object would read the registry value, store it locally, and then modify it. When destroyed, it would revert the setting. It would be used something like this: using(RegistryModification mod = new RegistryModification("HKCR\SomeValue"

问题 I'm loading an Image from a byte[] using MemoryStream and getting information about the image by inspecting it's ProperyItems . In the process of doing this though, I noticed some odd behaviour where some of the image's PropertyItems were disappearing. After much debugging I finally figured out that this was being caused by the MemoryStream being disposed. MemoryStream ms0 = new MemoryStream(imageBytes); Image img0 = Image.FromStream(ms0); Console.Out.WriteLine("Without using, Image

问题 I launch a timer only one time in my application: CustomTimer timer = new CustomTimer(mod); timer.Interval = interval.TotalMilliseconds; timer.AutoReset = false; timer.Start(); So the AutoReset is set to false. At the end of the timer, will the dispose method be called automatically? 回答1: No it will not. AutoReset will simply state whether the Elapsed event should be triggered each time the interval elapses, or only the first time. You can e.g. hook up an event handler to the Tick event and

问题 Why I see "Hello" words many times when I add timer.Dispose() to my code in release mode. Without timer.Dispose() I see "Hello" once. Thanks. using System.Threading; namespace ConsoleApplication1 { class Program { static void Method(object state) { Console.WriteLine(state); GC.Collect(); } static void Main() { var timer = new Timer(Method, "Hello", 0, 200); Console.ReadLine(); timer.Dispose(); } } } 回答1: You see it once because the garbage collector has collected the timer object. Since there

问题 I am working on this high frequency production system. There is a C# / CLI layer which calls into a C++ library. What we are observing is that managed objects are going into generation 2 of the garabage collector and getting 'stuck'. Eventually the C# applications grind to a halt as RAM runs out. These managed objects are local objects and should have a very short lifetime. Also they are only referenced once. The C# applications are having to call .Dispose() on all their objects that hold