blocks|key|3827800|text|我习惯于将BackgroundWorker作为Thread的包装器。所以我在图形用户界面上使用BackgroundWorker，而在更专业或更脏的工作(Windows服务等)上使用线程|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3827801|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I use to associate BackgroundWorker as a wrapper for what Threads would do. So I use BackgroundWorker on GUI works, and Threads on more specialized or dirty jobs (Windows Services, etc)

blocks|key|4670658|text|如果您所说的“线程”是指显式地使用System.Threading.Thread类来创建、配置和启动您自己的线程，那么答案是这样做对您来说是更多的工作，涉及更多的cpu周期，而不仅仅是从线程池中拉出线程(wjhich是其他技术所做的)，但它为您提供了更多的灵活性，因为它允许您指定线程优先级，以及使用线程池线程无法提供的其他几个特征。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4670659|当在设计时不知道所需的线程数量时，“线程池”方法更合适。该池最初包含少量线程，“准备好”供您调用它们。它可以根据需要动态创建新线程，并为您管理未使用线程的创建、协调和删除。有三种机制可以用来访问和使用池中的线程。|4670660|使用technique)|4670661|Using+()的计时器(最常见的technique)|unordered-list-item|4670662|Using计时器(几个variations)|ordered-list-item|4670663|System.Threading.ThreadPool提供了几个其他功能(BackGroundWorker类、QueueUserWorkItem()等))。|4670664|4670665|4670666|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

If by "Threads" you mean explicitly using the System.Threading.Thread class to create, configure and kick off your own threads, then the answer is that doing this is more work on your part, involves more cpu cycles than just pulling a thread from the thread pool, (wjhich is what the other techniques do), but it gives you more flexibility, as it allows you to specify thread priority, and several other characteristics that using Thread Pool threads does not afford you. 

The "Thread Pool" approach is more appropriate when the number of threads required is not known at design time. The pool initially contains a small number of threads, “ready” for you to call upon them. It can dynamically create new threads on demand, and it manages creation, coordination, and deletion of unused threads for you. There are three mechanisms you can use to access and use threads from the pool.

<ol>
<li>Using Delegate.BeginInvoke() (the most common technique)</li>
<li>Using timers (several variations)</li>
<li>System.Threading.ThreadPool provides several other features (BackGroundWorker class, QueueUserWorkItem(), etc.).</li>
</ol>

blocks|key|1163096|text|看一看this+great+threading+overview|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1163097|1163098|+BackgroundWorker提供以下功能：|blockquote|1163099|1163100|1163101|1163102|用于在不使用Abort|unordered-list-item|1163103|的情况下通知工作进程结束的"cancel“标志用于报告进度、完成和IComponent的cancellation|1163104|An实现的标准协议，允许它位于工作线程上的Visual+Studio+Designer异常处理中|1163105|更新窗体和|1163106|控件以响应工作进程或完成的功能。|1163107|1163108|最后两个功能特别有用-它意味着您不必在worker方法中包含try/catch块，并且无需调用Control.Invoke即可更新Windows窗体和WPF控件。|1163109|entityMap|0|LINK|mutability|MUTABLE|url|http://www.albahari.com/threading/part3.aspx#_BackgroundWorker^0|3|T|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1B|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|K|3|L|5|M|7|1F|8|@]|9|@]|C|$]]|$1|N|3|O|5|M|7|1G|8|@]|9|@]|C|$]]|$1|P|3|Q|5|M|7|1H|8|@]|9|@]|C|$]]|$1|R|3|S|5|M|7|1I|8|@]|9|@]|C|$]]|$1|T|3|U|5|M|7|1J|8|@]|9|@]|C|$]]|$1|V|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1L|8|@]|9|@]|C|$]]|$1|Y|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]]|Z|$10|$5|11|12|13|C|$14|15]]]]

Have a look at <a href="http://www.albahari.com/threading/part3.aspx#_BackgroundWorker" rel="noreferrer">this great threading overview</a>:

<blockquote>
 [The BackgroundWorker] provides the following features:
 
 <ul>
 <li>A "cancel" flag for signaling a worker to end without using Abort</li>
 <li>A standard protocol for reporting progress, completion and cancellation</li>
 <li>An implementation of IComponent allowing it be sited in the Visual Studio Designer
 Exception handling on the worker thread </li>
 <li>The ability to update Windows Forms and WPF controls in response to worker progress or completion.</li>
 </ul>
 
 The last two features are particularly useful – it means you don't have to include a try/catch block in your worker method, and can update Windows Forms and WPF controls without needing to call Control.Invoke.
</blockquote>

blocks|key|4670723|text|只有当你不需要处理UI+(WinForms或WPF)时才使用线程，当你必须处理UI时才使用后台工作线程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4670724|您可以避免大量的UI和后台工作进程(+lot+)问题。|offset|length|style|BOLD|4670725|entityMap^0|0|J|3|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Threads only when you don't have to work with a UI (WinForms or WPF) and background workers when you do have to deal with a UI.

You avoid a lot of problems with UIs and background workers.

blocks|key|1170196|text|BackgroundWorker类是将线程添加到窗体以执行一些繁重操作而不会阻塞UI的简单方法。你也可以用线程来做同样的事情，但是需要稍微多一点的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1170197|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The BackgroundWorker class is an easy way to add a thread to a Form to perform some heavy operation without blocking the UI. You could do the same with a thread but with slightly more coding.

blocks|key|4670917|text|BackgroundWorker类只是为您提供切换到UI线程上下文的事件，但请不要混淆；DoWork事件(实际上是您做工作的地方)仍然在另一个线程的上下文中执行(因为这就是整件事的重点)，在那里执行任何类型的UI交互或更新，往好了说都会抛出异常，往坏了说就会崩溃。当您试图做一些需要UI更新并且其作用域不超出表单范围的事情时，应该在表单上使用BackgroundWorker。对于其他后台操作，请考虑使用ThreadPool+(用于短期操作)或创建自己的线程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4670918|BackgroundWorker为ProgressChanged事件提供了便利，但是不要太习惯于在DoWork中进行UI更新。|4670919|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The BackgroundWorker class simply provides events that are switched to the context of the UI thread for you, but don't be confused; the DoWork event (which is where you actually, well, do the work) is still executed in the context of another thread (as that's the point of the whole thing) and performing any kind of UI interaction or update there will throw an exception at best, and crash at worst. The BackgroundWorker should be used on forms when you're trying to do something that requires a UI update and whose scope doesn't extend beyond that of the form. For other background operations, consider either using the ThreadPool (for short-lived operations) or creating your own Thread.

The BackgroundWorker provides convenience with the ProgressChanged event, but don't get too comfortable and start doing UI updates in DoWork.

What are the pros and cons in using the either for achieving a given task.

The million dollar question is which one to use and when?

Many Thanks.

BackgroundWorker and Threads

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

使用两者来完成给定任务的优缺点分别是什么？百万美元的问题是使用哪一个，什么时候使用？非常感谢。

问BackgroundWorker和线程
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问BackgroundWorker和线程EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问BackgroundWorker和线程
EN