Gijs Reijn

@SteveL-MSFT Got it Steve. Personally with all the issues related to the store, having the ability to choose the `installerType` and the `source`, just throws in a better installation experience....

@SteveL-MSFT Merge conflicts resolved. I had to rewrite a little part, because the PR was quite outdated. There's a new switch introduced that switches between `Microsoft.DSC` or `Microsoft.DSC.Preview` based on...

> @mdanish-kh can you do one more review of this? Thanks! > > @Gijsreyn there's an empty `build.ps1` file? Either I don't have my glasses on, or there is a...

> > Either I don't have my glasses on, or there is a little bug in GitHub @SteveL-MSFT, as you can see it's correctly in my branch: [Gijsreyn/operation-methods@`winget-manifest-uploader`/build.ps1](https://github.com/Gijsreyn/operation-methods/blob/winget-manifest-uploader/build.ps1) > >...

Also mentioned in the [discussion](https://github.com/PowerShell/DSC/discussions/638) from the RC release.

Hi @m-mrks, what is the module's installed location? If it is in your user profile, can you move the module to: `C:\Program Files\WindowsPowerShell\Modules`? I think this is a known limitation.

Yes correct, that's the PowerShell 7 folder. As you're using the WindowsPowerShell adapter, it should be in that folder you've mentioned :). I don't think this is a limitation of...

More of a personal opinion, I would move away from using `Install-Module` on PowerShell 7+. The `Microsoft.PowerShell.PSResourceGet` is shipped with it. You don't have to rely on the PowerShellGet anymore....

@SteveL-MSFT will the PS streams implementation in the `PSScript` resource also solve #833?

Sharp Mikey, I didn't think about that one. I was assuming that it would map one-on-one with the resource manifest.