-
Notifications
You must be signed in to change notification settings - Fork 751
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
Project capabilities should always be present for SingleProject #17923
Conversation
@Mergifyio backport release/stable/5.3 |
✅ Backports have been created
|
@Mergifyio backport release/stable/5.2 |
✅ Backports have been created
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-17923/index.html |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-17923/index.html |
The build 136057 found UI Test snapshots differences: Details
|
…5.2/pr-17923 Project capabilities should always be present for SingleProject (backport #17923)
…5.3/pr-17923 Project capabilities should always be present for SingleProject (backport #17923)
GitHub Issue (If applicable): closes #
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When selecting the project properties in Visual Studio an exception is encountered
What is the new behavior?
We now always provide the required MAUI capability which seems to resolve the problem in Visual Studio without adjustments to the csproj.