C#如何从外部进程关闭无固定标题的.NET异常子窗口？

Great question—dealing with unmanaged window detection when titles overlap is such a common headache for helper apps that hook into third-party software. Let’s walk through reliable ways to identify and close that .NET Framework exception window, even when it shares the main app’s title.

1. Use Window Class Names to Filter #

.NET exception dialogs (especially WinForms-based ones) have distinct class names you can target. Grab a tool like Spy++ (included with Visual Studio) to inspect the window—you’ll likely see something like WindowsForms10.Window.8.app.0.141b42a_r8_ad1 for the main dialog frame, or the generic #32770 dialog class paired with unique child controls.

In your code, after detecting a window has opened, check its class name first to narrow down candidates:

[DllImport("user32.dll", SetLastError = true, CharSet = CharSet.Auto)]
static extern int GetClassName(IntPtr hWnd, StringBuilder lpClassName, int nMaxCount);

// When you detect a window open:
StringBuilder className = new StringBuilder(256);
GetClassName(windowHandle, className, className.Capacity);

// Check for .NET-specific window classes or dialog frames
if (className.ToString().StartsWith("WindowsForms10.Window") || className.ToString() == "#32770")
{
    // Now verify it's the exception dialog (see step 4 for checking child text)
}

2. Verify Owner Window Relationships #

Exception dialogs are almost always modal, meaning they’re owned by the main app window. You can use this relationship to confirm you’re targeting the right window:

• Use GetWindow with the GW_OWNER flag to get the parent window handle of the candidate window.
• Compare that owner handle to the main app window handle you’ve already identified. If they match, you’re one step closer to confirming it’s the exception dialog.

3. Hook Into Window Creation Events #

Instead of just polling for window opens, set up a WH_CBT hook with SetWindowsHookEx to catch window creation events as they happen. This lets you inspect every new window immediately, so you can filter by class name, owner, and content before the dialog even becomes visible.

Just a heads-up: Global hooks need careful handling (especially for mixed 32/64-bit environments) and often require a separate DLL if you’re targeting processes outside your own.

4. Inspect Child Control Text #

Even if the window title matches the main app, the exception dialog will have unique text in its client area (like "Unhandled exception has occurred in your application"). Use FindWindowEx to locate child static controls, then SendMessage with WM_GETTEXT to retrieve their content and check for exception-specific keywords.

Pro Tip #

Spy++ is indispensable here. Use it to capture the exact control IDs, class names, and text snippets from the exception window—this gives you concrete values to target in your code instead of guessing.

内容的提问来源于stack exchange，提问作者FailedShack