[Nice3point]

Summary of the Pull Request

What is this about:

Redraws the Revit ribbon, the dockable panes, and the add-in windows after the API upgrades a family from an earlier Revit version.

Description:

What changed

• RevitContext.BeginModalLoopCompatibilityScope() returns a scope that posts the WPF frame notification MilChannelNotify to the MediaContextNotificationWindow of the current thread on dispose.
• Every call returns one stateless instance, with no lock, nesting counter, or dispose guard.
• The scope finds the notification window with FindWindowEx by its title and owner thread, and caches the handle per thread.
• CsWin32 generates the Win32 interop of the library and the test project from their NativeMethods.txt.
• The README "Context" section and the changelog describe the scope.

Where to look

• The scope names two WPF internals: the window title MediaContextNotificationWindow and the registered message MilChannelNotify. Both have the same values in .NET Framework and .NET. If WPF renames them, the scope posts nothing, and the interface behaves as without the scope.
• The scope departs from the reference counting of the other Begin...Scope() methods: it changes no state. A nested scope and a second dispose post a repeated notification, and WPF reads an empty render channel and returns.
• The library project suppresses PInvoke009. CsWin32 recommends System.Memory on .NET Framework for Span overloads, and the five functions take no Span. The package takes no new dependency.
• The test reads the composed frame through PrintWindow. Windows composes no frame for a window entirely outside the screen, so the 40-pixel window shows one column of pixels at the left edge of the virtual screen during the test.

How verified

• Build: Release.R20, Release.R21, Release.R24, Release.R26, and Release.R27, zero errors and no new warnings.
• RevitContextTests on Revit 2025 and 2027: 14 passed. On Revit 2026: 15 passed, with the test for a thread without WPF.
• BeginModalLoopCompatibilityScope_TemplateOfThePreviousVersion_WindowDrawsTheNextFrame creates a family from the installed template of the previous Revit inside the scope. With the post removed, it fails on Revit 2026: the window shows the color of the moment of the upgrade.
• Not covered: Revit 2021 to 2024 by a test run.

Quality Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.