manager.PackagesDownloadStarted not fired

Hey guys,

Maybe i’m just not good enough with C#, but for me it seems that the event manager.PackagesDownloadStarded is not fired.

My Code:

using nUpdate.Updating;
using System;
using System.Diagnostics;
using System.Globalization;
using System.Threading;
using System.Windows;

namespace KLauncher____Installer {
 /// <summary>
 /// Interaktionslogik für MainWindow.xaml
 /// </summary>
 public partial class MainWindow: Window {
  public MainWindow() {
   InitializeComponent();
  }

  private void button_Click(object sender, RoutedEventArgs e) {
   UpdateManager manager = new UpdateManager(new Uri("ServerURL"), "Key provide by nUpdate Administration", new CultureInfo("de-DE"));
   manager.PackagesDownloadStarted += Manager_PackagesDownloadStarted;
   var updaterUI = new UpdaterUI(manager, SynchronizationContext.Current);
   updaterUI.ShowUserInterface();
   manager.RestartHostApplication = false;

  }
  public void Manager_PackagesDownloadStarted(object sender, EventArgs e) {
   MessageBox.Show("Event fired!");
  }
 }
}

Please tell what i’m doing wrong:)

Have nice easter days.

[dbforge]

Ah, I see. You’re using WPF, that’s the problem. But, in any case, that wouldn’t have been the necessary event. 😉 Version 3.x of nUpdate requires a small workaround for WPF as nUpdate, by default, calls Application.Exit which will not close the host application correctly. The library was originally invented to serve only for Windows Forms. To fix that, create a new class and add this content:

using nUpdate.Updating;

public class WPFUpdateManager : UpdateManager
{
    public WPFUpdateManager(Uri updateConfigurationFileUri, string publicKey, CultureInfo languageCulture) : base(updateConfigurationFileUri, publicKey, languageCulture)
    { }
    public override void TerminateApplication()
    {
        Environment.Exit(0);
    }
}

Then use that class instead of UpdateManager. This should fix your problem. This will be fixed in v4 as WPF will become fully supported then.

[dbforge]

See also: #31 This issue is now fixed and thus, a workaround is no longer necessary.