Skip to content
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.

Consider Writing the Provider in PowerShell #16

Open
bgshacklett opened this issue Sep 15, 2017 · 1 comment
Open

Consider Writing the Provider in PowerShell #16

bgshacklett opened this issue Sep 15, 2017 · 1 comment

Comments

@bgshacklett
Copy link

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.

@jirkapok
Copy link

See also #5

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants