While doing some research on what it will take to get things moving again on this project, I've been unable to find a well documented way to create a OneGet/PackageManagement provider using C#. The most recent documentation on the matter recommends building said provider as a PowerShell Script module:
https://github.com/OneGet/oneget/blob/master/docs/writepowershellbasedprovider.md
With this in mind. I would suggest that the current plan of writing this provider in C# be re-evaluated. Writing the provider in PowerShell would also bring an additional benefit of lowering the barrier to entry for potential contributors.
jirkapok
commented
6 years ago
While doing some research on what it will take to get things moving again on this project, I've been unable to find a well documented way to create a OneGet/PackageManagement provider using C#. The most recent documentation on the matter recommends building said provider as a PowerShell Script module: https://github.com/OneGet/oneget/blob/master/docs/writepowershellbasedprovider.md
There is a small mention of writing a Package Provider in managed code in the Wiki at https://github.com/OneGet/oneget/wiki/ImplementingPackageProvider, but it is lackluster in addition to being out of date compared to the previously linked document.
With this in mind. I would suggest that the current plan of writing this provider in C# be re-evaluated. Writing the provider in PowerShell would also bring an additional benefit of lowering the barrier to entry for potential contributors.