Thomas Nieto

This is because `Install-PSResource` isn't adding the install script path to the `Path` environment variable so it can be ran without prepending the path. In PowerShellGet v2 `Install-Script` did this...

Instead of trying to do too much with `Register-PSResourceRepository` and adding more parameters there. A better idea would be to create a new cmdlet that does that `Reset-PSResourceRepository`.

I'd be fine with changing the default behavior for `Test-ScriptFileInfo` to return an object of the script info metadata. Then no `-PassThru` flag is needed or a new cmdlet. It...

A `PassThru` parameter isn't needed in this case. If I'm reading the OP request correctly it is to send the script info comment block string to the pipeline so that...

@anamnavi good to hear. During that work please make sure `SupportsPaging` is added as well.

Why do these parameter sets need to be added the current command syntax? The current command syntax has a `Type` and `Tag` parameter and those shouldn't be in their own...

Why does PSGalleryScripts still exist? I know it was there for PSGet v2 when the initial requirement had scripts and modules in separate repos but that has been long since...

@SydneyhSmith / @SteveL-MSFT if this issue is not completed before PSGet 3.0 GA will it be a breaking change?

Related issue in regards to the DSC resource but still the same feature request: https://github.com/PowerShell/PowerShellGetDsc/issues/7 > > One issue here is you're going to need to check all existing modules...

@SydneyhSmith any chance this can be added to 3.0? This is a huge missing feature in a multi-user environment.