-
Notifications
You must be signed in to change notification settings - Fork 6.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
Move to WinAppSDK-1.1.0 #18603
Move to WinAppSDK-1.1.0 #18603
Conversation
7b47f98
to
cd269c0
Compare
Does this fix some of the settings bugs? |
Is this able to hop on .59 or has that train already left the station? |
It will fix the "unable to run elevated" issue so many people are having. |
Yes, this is what we were waiting for to include in .59 . |
@@ -180,16 +179,6 @@ IFACEMETHODIMP CPowerRenameItem::GetId(_Out_ int* id) | |||
return S_OK; | |||
} | |||
|
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.
Why was this removed? Wouldn’t expect it in a rev for 1.1
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.
From the PR description. Looks like it isn't used and breaks the build.
Removed PowerRename method was breaking the build because of the unresolved reference. Method is not needed, therefore deleted.
@@ -73,3 +73,8 @@ | |||
[assembly: SuppressMessage("StyleCop.CSharp.MaintainabilityRules", "SA1402:File may only contain a single type", Justification = "Not part of the project. WindowsAppSDK file.", Scope = "type", Target = "~T:Microsoft.WindowsAppSDK.Runtime.Packages.Singleton")] | |||
[assembly: SuppressMessage("StyleCop.CSharp.LayoutRules", "SA1516:Elements should be separated by blank line", Justification = "Not part of the project. WindowsAppSDK file.", Scope = "type", Target = "~T:Microsoft.WindowsAppSDK.Runtime.Packages.Singleton")] | |||
[assembly: SuppressMessage("StyleCop.CSharp.LayoutRules", "SA1516:Elements should be separated by blank line", Justification = "Not part of the project. WindowsAppSDK file.", Scope = "type", Target = "~T:Microsoft.WindowsAppSDK.Runtime.Packages.Main")] | |||
[assembly: SuppressMessage("StyleCop.CSharp.LayoutRules", "SA1513:Closing brace should be followed by blank line", Justification = "Not part of the project. WindowsAppSDK file.", Scope = "namespaceanddescendants", Target = "Microsoft.WindowsAppSDK.Runtime.Packages")] |
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.
These are pretty important rules. Can we maybe target the offending file or method?
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.
I wouldn’t block the release on this but would be nice to adjust
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.
The target part means these exceptions will be applied to the offending package. They'll still trigger in our code.
Regarding the copyright one, I think that could only be done locally in the file for it to be specific ... It's code from nuget, though. It's possible to make that one only apply to the Settings project, so I guess that's what we'll do.
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.
Tested and it looks good. No longer has the run elevation issue with 1.1.
I've added a commit to revert the change where we were showing a warning instead of starting Settings under those conditions.
Great work.
Don't want to bother but both Settings and PowerRename are not starting after a clean build. |
Wow. That's pretty weird. Any other info there? Like a call stack from VS? |
Looks like the error is on
|
@davidegiacometti You've installed winappsdk 1.1, right? Any errors in the command line when installing it? Did you restart after? This is pretty weird. Does the WinUI 3 Gallery from the store also crash in a similar fashion? |
@davidegiacometti , this issue microsoft/WindowsAppSDK#2492 seems to indicate somethings might need to be cleaned up. Can you try to really clean the repo with |
I agree that's really strange. I have installed 1.1 runtime and both VS extensions (C# and C++).
I am also experiencing the error with WinUI 3 Gallery. |
I have been able to fix it:
I think the build was failing becouse of 1.1 previews installed. |
Thanks for the heads-up @davidegiacometti . This is something I definitely want to repro locally to open an issue upstream. |
* Move to WinAppSDK-1.1.0 * expect.txt * Revert "[Settings]Don't launch if explorer is running elevated" This reverts commit c485da2. * Make copyright header analyze suppression module scope
Global suppressions can be reverted after microsoft/WindowsAppSDK#2569 |
Summary of the Pull Request
note: Removed PowerRename method was breaking the build because of the unresolved reference. Method is not needed, therefore deleted.
Someone please test ARM64 installer.
What is this about:
What is included in the PR:
How does someone test / validate:
Quality Checklist
Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.