Error in updating winforms application (NullReferenceExcepti

After using this solution: http://wyday.com/wybuild/help/automatic-updates/

I get this error:System.NullReferenceException: Refercia de objeto n definida para uma instcia de um objeto. em wyUpdate.frmMain.CancelUpdate(Boolean ForceClose) em wyUpdate.frmMain.btnCancel_Click(Object sender, EventArgs e) em System.Windows.Forms.Control.OnClick(EventArgs e) em System.Windows.Forms.Button.OnClick(EventArgs e) em System.Windows.Forms.Button.WndProc(Message& m) em System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) em System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) em System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I use windows 7 and wyBuild version 2.6.11.3.

I will be more specific. After clicking the update button, the wyUpdate executable forces the application to exit (asking to directly end the process).Then I agree to close the process.

After opening the app once again, the wyUpdate executable runs but stops in the "extracting files" task (just after "downloading updates" task). It stays in an infinite loop. When I cancel the update, I get the error I mentioned in the previous post.

Try updating to wyBuild 2.6.14. Then add the latest AutomaticUpdater (2.6.14) and wyUpdate.exe (2.6.14) with your app. Tell me if you still get this error.

Hi,

I update to wyBuild 2.6.14 today. I did update the winform component and the file wyUpdate.exe. The same problem persists.

We can't reproduce this here and there's not enough information (the code you're using, the actions you're taking, etc.). Can I schedule a time to remotely debug this? Are you free sometime in the next couple of days? Email me at wyatt@wyday.com some time you're free.

Yes, I am free the next few days. I will e-mail you tomorrow.

Thank you for the promptitude.

We also have occasional reports from users of "wyUpate stuck in an update loop". I don't know it there's a null reference exception, too.

Problem is we've never seen it ourselves, though. Is there a way to get wyUpdate to log events errors to a file for these users? This would help us (and wyUpdate) in debugging.

We don't do any logging (yet). If any other customers report this behavior we'd like to help you fix this. Either by doing a remote debug on the user's computer or by helping you do the debug. The bug that Fabio was getting was due to a 3rd part library that wasn't playing nice (it aborted the Application.Exit() function that the AutomaticUpdater calls and it never called it again).

Thanks for the info. This is going to be a hard bug to catch. We're visiting a customer today who has the wyUpdate loops, so we'll try see why.

Reply
Discard post