Fixup to WPF to adapt to removal of legacy API's from WinForms#2168
Merged
vatsan-madhavan merged 2 commits intodotnet:release/3.1from Nov 8, 2019
Merged
Conversation
ghost
requested a review
from 
RussKie
approved these changes
Nov 8, 2019
vatsan-madhavan
added
ask-mode
* NO MERGE *
rladuca
approved these changes
Nov 8, 2019
vatsan-madhavan
removed
the
* NO MERGE *
ghost
locked as resolved and limited conversation to collaborators
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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