Fixup to WPF to adapt to removal of legacy API's from WinForms #2168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #2169
This is a fixup to WPF to adapt to legacy api removal in WinForms (see dotnet/winforms#2157).
Risk
Low - minor changes to ElementHost.
Customer Impact.
Doesn't seem like very much of an impact from WPF directly. Indirect impact from WinForms changes are off-topic here.
Testing
None - this builds.
Related: We need this to get #2161 going.
/cc @RussKie