You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the first thing a lot of people would do to try out this project is run the WPF sample app. When doing so it's likely they'll notice that the Current Version displayed on the main window usually doesn't change from 1.0 to 1.1 as expected after doing an "Install Now". In the following code from UpdateWindow.xaml.cs you can see it's possible for updateManager.CleanUp to finish before the BeginInvoke that closes the update window finishes. If that happens, the CleanUp method sets the updatemanager's state back to unchecked before the closed event handler inside the main window does its check to see that the state is AppliedSuccessfully. The Closed handler in the MainWindow code only calls OnPropertyChanged("AppVersion") if the state is AppliedSuccessfully. Maybe the easiest thing is to make sure the Update window closes before CleanUp is called.
I think the first thing a lot of people would do to try out this project is run the WPF sample app. When doing so it's likely they'll notice that the Current Version displayed on the main window usually doesn't change from 1.0 to 1.1 as expected after doing an "Install Now". In the following code from UpdateWindow.xaml.cs you can see it's possible for updateManager.CleanUp to finish before the BeginInvoke that closes the update window finishes. If that happens, the CleanUp method sets the updatemanager's state back to unchecked before the closed event handler inside the main window does its check to see that the state is AppliedSuccessfully. The Closed handler in the MainWindow code only calls OnPropertyChanged("AppVersion") if the state is AppliedSuccessfully. Maybe the easiest thing is to make sure the Update window closes before CleanUp is called.
The text was updated successfully, but these errors were encountered: