-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove implicit reference to Maui Compatibility and template references #22203
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I had tried this previously, the package was always referenced no matter what I did with UseMauiCompat. My expectation is that with these changes, unless the package is directly referenced or UseMauiCompat is explicitly true, then the package will not be included. If I'm reading it correctly, that seems to be the case. Correct?
That is correct. After this PR, if you are not adding the package or setting the property, then the compat package should not be included. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a new template in the house, maui-blazor-solution. Probably needs to be updated too!
/rebase |
c4541fd
to
479d8a6
Compare
Description of Change
For new users it's not advantageous (and can be confusing) to have the Maui Compatibility package referenced. Nothing from this package should be used by new projects.
TODO
What updates need to be made to the migration tool? Does it already set UseMauiCompat to true?