Thomas Nieto

Still active

This was using the gallery. My internet wasn't the problem and I believed I checked v2 and it was fine.

I maintain the replacement for `OneGet/PackageManagement` called [AnyPackage](https://github.com/anypackage/anypackage) and have a [Scoop](https://github.com/anypackage/scoop) package provider for it.

There is an anti-pattern when putting all "settings" into a single cmdlet. Ideally there would be a cmdlet(s) to set the individual setting. Here are some examples that aren't real...

It looks like that enum is used by DSC in various places to enable/disable features if it doesn't have the `command` type.

Does this enhancement also handle the scenario of real .NET objects like `FileInfo` with PowerShell's ETS (Extended Type System) properties? Here is an example with `Get-ChildItem` with `FileInfo` and `DirectoryInfo`....

I also have had the same concern for a while. I would have wanted a `New-PSResource` or `Build-PSResource` and publish only pushes the resource to the repository.

@SydneyhSmith I know this is close to release but the existing functionality is already there just splitting it into two cmdlets.

In the winPS adapter class-based resources are called directly and do not use the LCM. So the document should only be limited to `Script` and `Binary` resources. https://github.com/PowerShell/DSC/blob/47c0d4fc61affb61547bdcf4cd250a80aa29f717/powershell-adapter/psDscAdapter/win_psDscAdapter.psm1#L398-L400 https://github.com/PowerShell/DSC/blob/47c0d4fc61affb61547bdcf4cd250a80aa29f717/powershell-adapter/psDscAdapter/win_psDscAdapter.psm1#L425-L442

I don't understand what you mean by guessing. Surely there is a way test the endpoint if it accept a v3 or v2 request. During my impromptu testing if the...