-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add support for DSCv3 in configuration PowerShell modules #5470
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
Conversation
@@ -10,7 +10,7 @@ | |||
|
|||
// Forcibly set the target and supported platforms due to the internal build setup. | |||
// Keep in sync with project versions. | |||
[assembly: TargetPlatform("Windows10.0.22000.0")] | |||
[assembly: TargetPlatform("Windows10.0.26100.0")] |
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 feel like there was a reason that I didn't update that... but now I'm not remembering it.
|
||
await installDSCv3.InvokeAsync(); | ||
|
||
if (installDSCv3.HadErrors) |
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.
Install-WinGetPackage
does not produce an error on failed install. The result object must be inspected.
I'm not sure of the "correct" PowerShell design, but maybe one of:
- A new cmdlet like
Validate-WinGetPackageInstall
that throws if the install failed - A new parameter like
-ThrowOnFailure
- A breaking change to throw on failure (maybe with a parameter to not)
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 can change the script to inspect the result object.
Microsoft Reviewers: Open in CodeFlow