Change Microsoft.Xaml.Interactions.Core to Microsoft.Xaml.Interactivity #282
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.
Fixes #209
The major revision is the perfect time to fix this long-standing issue with the complexity of usings behaviors involving having to remember and include multiple namespaces in XAML. This removes the warnings from CA1020 as well.
Talked to Sergio, we think just aligning on
Microsoft.Xaml.Interactivity
as the main namespace would make sense (it's shorter, the more familiar name, and means the core attachment point doesn't move), this would look like this:Before:
After:
For migration, folks should just be able to change the xmlns for Core: