Clarify settings behavior

[Gijsreyn]

• I have signed the Contributor License Agreement.
• This pull request is related to a discussion.

---

When looking through the discussions, I noticed the following question asked by Tristan. After trying out some options, I thought the ConfigureBehavior would do the trick. Unfortunately, after trying it out, I took the conclusion from the description that only winget install is affected by these settings. This pull request clarifies it a bit more.

Microsoft Reviewers: Open in CodeFlow

[Trenly]

They affect more than just install. If I'm not mistaken, they also affect upgrade and import.

In fact, I would think it's nore likely a bug in DSC if they aren’t being considered when used with the WinGetPackage resource; especially becausethefe doesn’t seem to be Scope or Locale or InstallerType properties on the DSC Resource (@denelon - should these be added? Should I open an issue for that?)

[Gijsreyn]

Thanks for the reply Kaleb. If that's the case, then I would even think of renaming the setting name, as it states installBehavior, but that might be a preference and opinion.

[Trenly]

Thanks for the reply Kaleb. If that's the case, then I would even think of renaming the setting name, as it states installBehavior, but that might be a preference and opinion.

Unfortunately I think that renaming the setting would be considered a breaking change (unless both the old name and the new name would work)

[Gijsreyn]

I agree; maybe only introducing upgradeBehavior would suffice, as uninstallBehavior is already there.

[Trenly]

I agree; maybe only introducing upgradeBehavior would suffice, as uninstallBehavior is already there.

Then you get into weird semantics because an upgrade is just a special case of install

[denelon]

In general, a WinGet Configuration shouldn't be affected by a user's Package Management settings. That's probably something we'll need to clarify.

[Trenly]

In general, a WinGet Configuration shouldn't be affected by a user's Package Management settings. That's probably something we'll need to clarify.

In that case, does the DSC Resource need to be updated to support Scope, Locale, and installer type? It seems like a gap between the DSC Resource and the WinGet Client if there isn’t a way to specificy which is the preferred scope, or preferred installer

[denelon]

Yes, we have an issue open for that work as well.

• Expose more settings to Microsoft.WinGet.DSC/WinGetPackage #3401

[denelon]

• WinGet Configuration clarifications regarding WinGet Settings #5064

[Trenly]

Yes, we have an issue open for that work as well.

• Expose more settings to Microsoft.WinGet.DSC/WinGetPackage #3401

Ah, I knew I was missing something!

[JohnMcPMS]

They should be affecting configure. A package install via configure is: winget.exe -> Hosted PowerShell: WinGet DSC -> Hosted PowerShell: WinGet Client -> WinGet COM install. The COM server uses the same settings as winget.exe.

I think that the statements in this change are inaccurate; at a minimum with desired behavior but I think also potentially with actual behavior. If there is a discrepancy that would likely be a bug.