Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Finalizing an object
Hey people
I have an object that I would like to kill straight away instead of it sitting on the heap. My problem is that if I call dispose then its not guranteed to be killed and I have an event linked to my object from an another class which when called goes to the code for the old object still on the heap which causes some major problems.
Can you help sorry about the low points availiable for this question but I have almost run out.
Thanks
Simion
I have an object that I would like to kill straight away instead of it sitting on the heap. My problem is that if I call dispose then its not guranteed to be killed and I have an event linked to my object from an another class which when called goes to the code for the old object still on the heap which causes some major problems.
Can you help sorry about the low points availiable for this question but I have almost run out.
Thanks
Simion
Asked:
Who is Participating?
You can define an interface (or abstract class) that your classes can use to communicate. Since you can only inherit from one class, but you can inherit (implement) multiple interfaces, I use interfaces.
Any class that needs to have a callback to another class implements a standard interface. I implement a Register(object) method to keep a list of objects with callbacks (events) hooked to my instance and an Unregister() method that is called from the instance's Dispose method. The unregister method loops through all registered objects, notifying them to unhook the event handler. It's just a minor extenstion of the message above, but it's simple and effective and you don't have to worry about releasing an instance. When it's Dispose() method is called, it notifies everyone in its list to unhook any events. What's really cool, after you get used to the idea, is being able to cascade the disposal of registered objects as well.
Here's a reference, if you're interested:
Explicit Interface Implementation Tutorial
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csref/html/vcwlkExplicitInterfaceImplementationTutorial.asp
Any class that needs to have a callback to another class implements a standard interface. I implement a Register(object) method to keep a list of objects with callbacks (events) hooked to my instance and an Unregister() method that is called from the instance's Dispose method. The unregister method loops through all registered objects, notifying them to unhook the event handler. It's just a minor extenstion of the message above, but it's simple and effective and you don't have to worry about releasing an instance. When it's Dispose() method is called, it notifies everyone in its list to unhook any events. What's really cool, after you get used to the idea, is being able to cascade the disposal of registered objects as well.
Here's a reference, if you're interested:
Explicit Interface Implementation Tutorial
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csref/html/vcwlkExplicitInterfaceImplementationTutorial.asp
Hey guys well thanks for the comments. I will split the points between you. Not that there much to split sorry about that. I'm doing my best to get more points but no one will accept my answers.
Actually although you helped me I realised that I was playing the dangerous game of static events which was why they were not disposing with the object. Hahahah The laugh of a crazy man who spend 5 hours wondering what the hell was going on. Well at least I'm a wiser man.
Thanks
Simion
Actually although you helped me I realised that I was playing the dangerous game of static events which was why they were not disposing with the object. Hahahah The laugh of a crazy man who spend 5 hours wondering what the hell was going on. Well at least I'm a wiser man.
Thanks
Simion
I hate it when that happens ;). BTW, you didn't split the points ... you might want to ask an admin to reopen the question so you can.
Eric
Eric
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month7 days, 16 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
// add an event handler
b.ButtonClick += new ButtonEventHandler(onButto
// remove an event handler
b.ButtonClick -= new ButtonEventHandler(onButto
This would keep the event from calling your disposed object.
At any rate, there isn't a way to kill an object straight away in C#; the closest you can get is to call Dispose() on the object, and then call System.GC.Collect() force the garbage collection routines to kick in but even then there isn't really any guarantee that your object will be destroyed because of the generational aspect of the garbage collector.
Eric