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

Consider Writing the Provider in PowerShell #16

Description

@bgshacklett

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions