search

PowerShell / SHiPS

Simple Hierarchy in PowerShell - developing PowerShell provider got so much easier
MIT License
185 stars 31 forks source link

Need to target netstandard2.0 instead of cross-compiling #104

Closed Jaykul closed 5 years ago

Jaykul commented 6 years ago

Right now you're basically shipping two separate modules (one for Windows PowerShell, and one for PowerShell Core). The problem is that this forces anyone who wants to write a binary module to also ship two ...

There's no way for anyone to make a cross-platform binary (targeting netstandard2.0) while referencing SHiPS (or your copies of P2F) when your assemblies are targeted at netcoreapp2.0

This forces us to go against best practices and leaves us forced to target the same pre-release System.Management.Automation assemblies you're targeting.

jianyunt commented 5 years ago

It's using .netstandard 2.0 now.