本文介绍了BackgroundWorker.RunworkerCompleted& ProgressChanged事件偶尔不会触发的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个基于.Net framework 3.5和C#开发的Windows应用程序.应用程序使用 BackgroundWorker 以执行其一些独立任务

We have a windows application developed on .Net framework 3.5 and C#. Application uses theBackgroundWorker to execute some of its independant tasks

BackgroundWorker.RunworkerCompleted 不会偶尔触发BackgroundWorker.ProgressChanged 事件.

   BackgroundWorker.RunworkerCompleted and BackgroundWorker.ProgressChanged events doesn't fired occasionally.

A) BackgroundWorker . RunworkerCompleted-应用程序日志指出 BackgroundWorker.Dowork 事件的最后一条语句是执行并跳过 BackgroundWorker.RunworkerCompleted.

A) BackgroundWorker.RunworkerCompleted - Application log states that theBackgroundWorker.Dowork event's last statement is executes and skips theBackgroundWorker.RunworkerCompleted.

B) BackgroundWorker.ProgressChanged  -应用程序日志指出事件调用的上一条语句成功执行,而该事件跳过.

B) BackgroundWorker.ProgressChanged  - Application log states the the previous statement of the event call executes successfully and this event skips.

在两种情况下,当我们重新启动应用程序时,它在一段时间到几天内都能正常运行.但是突然之间由于事件未触发,应用程序开始出现不良行为.没有固定的模式可以确定何时跳过这些事件.

In both case, when we restart the application, it works nicely for some time to few days. But all of sudden due to the events not fired, applicaiton start misbehaves. There is no fixed pattern to find out when these events get skipped.

任何帮助将不胜感激.

 

 

推荐答案


这篇关于BackgroundWorker.RunworkerCompleted& ProgressChanged事件偶尔不会触发的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-13 21:59