Hi , i have a problem with the automaticUpdater.I'm using .Net Profiler to see memory performance and seems that AutomaticUpdater is been disposed but not Garbaged cause there is an event that still keepAlive the AutomaticUpdater and all Login form too.I have a Winforms App , with Login Form. Inside this form i have the AutomaticUpdater. I tried to dispose automaticupdater too without any result. I havent used neither 1 event of AutomaticUpdater , nothing. I did only begin setup (GUID , toolstripmenu , UpdateType = CheckAndDownload , WaitBeforeCheck = 5)
.Net Profiler : Disposed instances with direct EventHandler roots (Show details) (Ignore...)One type has instances that are disposed and directly rooted by an EventHandler. This often indicates that an EventHandler has not been properly removed and is a common cause of memory leaks.Investigate the type below for more information.AutomaticUpdaterDid i wrong something?
Regards
The AutomaticUpdater is designed to last the lieftime of your application. It should be placed on your main form and last until your app closes (at which time Windows, by design, cleans up all the memory).
That being said, a number of people do what you do (put the AutomaticUpdater on the "login form" or "splash screen" of an app). We're going to make the AutomaticUpdater more flexible for cases like these.
In the meantime just put the AutomaticUpdater on your main form.
We have a new version coming out with 2.6.15 soon. But it won't implement the feature I was talking about (it does fix other bugs and add other features).
