dispose

I have a simple Windows form application. On the form I have a custom class that has it's own Dispose method. So the question is when should I call this? Is the FormClosed event (i.e. Form1_FormClosed) the correct place to do this? Or should I be writing a custom Dispose method for the form? For bonus points: Can a from be reopend once closed? (Obviously if it can then the FormClosed is the wrong way to go!) Thanks. A wee bit of surgery is required. Open the node next to your form in the Solution Explorer window. Double-click the Designer.cs file for the form. Locate the Dispose() method and

I'm trying to abstract/encapsulate the following code so all client calls don't need to repeat this code. For example, this is a call, from a view model (MVVM) to a WCF service: using (var channelFactory = new WcfChannelFactory<IPrestoService>(new NetTcpBinding())) { var endpointAddress = ConfigurationManager.AppSettings["prestoServiceAddress"]; IPrestoService prestoService = channelFactory.CreateChannel(new EndpointAddress(endpointAddress)); this.Applications = new ObservableCollection<Application>(prestoService.GetAllApplications().ToList()); } My original attempt at refactoring was to do

I am receiving data from UdpClient via the usual async callback: private void OnUdpData(IAsyncResult result) { byte[] data = _udpReceive.EndReceive(result, ref _receiveEndPoint); //Snip doing stuff with data _udpReceive.BeginReceive(OnUdpData, null); } When I Close() the UdpClient in the main thread, the callback fires as I would expect, but at this point _udpReceive is already disposed and I get an ObjectDisposedException when I try and call EndReceive() . I was expecting to just get an empty buffer. What is the correct way to handle this? Is there some member of UdpClient I can check before

Disposable.Create require an Action as parameter. The Action is run when the Rx subscription is being disposed. When disposing a Rx subscription I’d like to run some asynchronous clean up code, however using async () => with Action is identical to async void , which I’d like to avoid. For more details on why I want to avoid this, see here . Is it possible to create something like a Disposable.AsyncCreate , which accepts Func<Task> rather than Action . If so how should I use it as part of a CompositeDisposable ? Or are there other patterns for dealing with asynchronous Disposal? You could do

Some time ago i posted a question related to a WriteableBitmap memory leak, and though I received wonderful tips related to the problem, I still think there is a serious bug / (mistake made by me) / (Confusion) / (some other thing) here. So, here is my problem again: Suppose we have a WPF application with an Image and a button. The image's source is a really big bitmap (3600 * 4800 px), when it's shown at runtime the applicaton consumes ~90 MB. Now suppose i wish to instantiate a WriteableBitmap from the source of the image (the really big Image), when this happens the applications consumes

I have lots of code like this: FileStream fs = File.Open(@"C:\Temp\SNB-RSS.xml", FileMode.Open); using (XmlTextReader reader = new XmlTextReader(fs)) { /* Some other code */ } This gives me the following Code Analysis warning: CA2000 : Microsoft.Reliability : In method 'SF_Tester.Run()', object 'fs' is not disposed along all exception paths. Call System.IDisposable.Dispose on object 'fs' before all references to it are out of scope. If I follow the suggestion and I put the File.Open in a using statement, I get this: CA2202 : Microsoft.Usage : Object 'fs' can be disposed more than once in

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. In your specific example, no, it's unlikely that it would be particularly useful. Forms do not hold onto a

I'm ASP.NET MVC newbye and I'm learning and experimenting Enterprise design patterns: very interesting and helpful things indeed! But I keep missing something about the concept of disposing resources. To be more specific want to focus on the mechanism of controllerFactory which injects in the controller constructor an implementation of IFuncyRepository or IFuncyService or anyother kind of "resource" to be used in the controller (In my case I'm using StructureMap as IoC). My question is WHERE / IF / HOW these injected resources get Disposed. The book I'm following as guideline is ASP.NET Design