我见过许多使用“DoEvents-Hack”的商业应用程序。特别是当渲染开始发挥作用时，我经常看到这样的情况:

while(running)
{
    Render();
    Application.DoEvents();
}

他们都知道这种方法的害处。然而，他们使用黑客，因为他们不知道任何其他解决方案。以下是Tom Miller的博客文章中的一些方法:

Set your form to have all drawing occur in WmPaint, and do your rendering there. Before the end of the OnPaint method, make sure you do a this.Invalidate(); This will cause the OnPaint method to be fired again immediately. P/Invoke into the Win32 API and call PeekMessage/TranslateMessage/DispatchMessage. (Doevents actually does something similar, but you can do this without the extra allocations). Write your own forms class that is a small wrapper around CreateWindowEx, and give yourself complete control over the message loop. -Decide that the DoEvents method works fine for you and stick with it.

可以，但这只是个黑客。

参见DoEvents邪恶吗?

直接从开发人员引用的MSDN页面:

Calling this method causes the current thread to be suspended while all waiting window messages are processed. If a message causes an event to be triggered, then other areas of your application code may execute. This can cause your application to exhibit unexpected behaviors that are difficult to debug. If you perform operations or computations that take a long time, it is often preferable to perform those operations on a new thread. For more information about asynchronous programming, see Asynchronous Programming Overview.

因此微软对它的使用提出了警告。

此外，我认为这是一个黑客，因为它的行为是不可预测的，容易产生副作用(这来自于尝试使用DoEvents而不是旋转一个新线程或使用后台工作)。

这里没有大男子主义——如果它是一个强有力的解决方案，我会全力支持它。然而，尝试在。net中使用DoEvents只会给我带来痛苦。

请查阅应用程序的MSDN文档。DoEvents方法。

应用程序。如果在消息队列中放入图形处理以外的内容，DoEvents可能会产生问题。

它可以用于更新进度条，并在MainForm构造和加载等过程中通知用户进度(如果这需要一段时间)。

In a recent application I've made, I used DoEvents to update some labels on a Loading Screen every time a block of code is executed in the constructor of my MainForm. The UI thread was, in this case, occupied with sending an email on a SMTP server that didn't support SendAsync() calls. I could probably have created a different thread with Begin() and End() methods and called a Send() from their, but that method is error-prone and I would prefer the Main Form of my application not throwing exceptions during construction.

DoEvents确实允许用户单击或键入并触发其他事件，后台线程是一种更好的方法。

但是，在某些情况下，您可能会遇到需要刷新事件消息的问题。我遇到了一个问题，在RichTextBox控件忽略ScrollToCaret()方法时，该控件在队列中有消息要处理。

下面的代码在执行DoEvents时阻塞所有用户输入:

using System;
using System.Runtime.InteropServices;
using System.Windows.Forms;

namespace Integrative.Desktop.Common
{
    static class NativeMethods
    {
        #region Block input

        [DllImport("user32.dll", EntryPoint = "BlockInput")]
        [return: MarshalAs(UnmanagedType.Bool)]
        private static extern bool BlockInput([MarshalAs(UnmanagedType.Bool)] bool fBlockIt);

        public static void HoldUser()
        {
            BlockInput(true);
        }

        public static void ReleaseUser()
        {
            BlockInput(false);
        }

        public static void DoEventsBlockingInput()
        {
            HoldUser();
            Application.DoEvents();
            ReleaseUser();
        }

        #endregion
    }
}

Yes.

但是，如果您需要使用应用程序。DoEvents，这主要是一个糟糕的应用程序设计的指示。也许你想在一个单独的线程中做一些工作?