Hi,
First of all, if there is no strong reference that is pointing to your views, then there should be no memory leaks as they would be garbage-collected when needed.
Based on my understanding, the ShotdownStarted event is invoked when the corresponding Dispatcher of the thread is closed (which usually happens when the thread finished its execution.) Hence, this event should not be used to detect when the components are being disposed and neither should be fired manually. Regarding this same subject, I believe you might find the following threads in the MSDN forums interesting:
Also, based on my understanding, when an application exits, all it's resources included the memory allocated is releases, so it doesn't seem to be necessary to check if a view was garbage-collected a this point.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini
First of all, if there is no strong reference that is pointing to your views, then there should be no memory leaks as they would be garbage-collected when needed.
Based on my understanding, the ShotdownStarted event is invoked when the corresponding Dispatcher of the thread is closed (which usually happens when the thread finished its execution.) Hence, this event should not be used to detect when the components are being disposed and neither should be fired manually. Regarding this same subject, I believe you might find the following threads in the MSDN forums interesting:
Also, based on my understanding, when an application exits, all it's resources included the memory allocated is releases, so it doesn't seem to be necessary to check if a view was garbage-collected a this point.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini