Paket.PowerShell mismatched FSharp.Core

[ctaggart]

These is a place to jot down some notes from a problem found with this pull request:
fsprojects#839

[ctaggart]

As I understand, binding redirects for PowerShell have to be done at the global level, so that is not an option.

paket.exe is ilmerging in FSharp.Core 3.1 (3.1.2.1), but UnionArgParser (0.8.7) being used reference FSharp.Core 3.0:

The next step is to see if there is a UnionArgParser that is buit with FSharp.Core 3.1.

[ctaggart]

Sadly, making UnionArgParser.dll reference FSharp.Core 4.3.1.0 did not resolve the issue. The troubleshooting scenarios I can think of are:

1. See if it is possible to reproduce the problem without PowerShell. Simply have an Console App use paket.exe as a library.
2. Don't use paket.exe and use the individual libraries instead. Not what I was hoping for a final distribution, but good for troubleshooting.

[ctaggart]

I was able to reproduce the problem with an console app.

Reading up on the notes on FSharp.Core.dll, is seams that --noframework option that I used would make it so that FSharp.Core.dll wasn't referenced.

http://fsharp.github.io/FSharp.Compiler.Service/corelib.html

but sadly it is

[ctaggart]

It appear that coding Paket.PowerShell.dll in C# may work, but I'd much prefer to stick to F#. The simplest solution would be to simply merge it too by adding it to this list:

https://github.com/fsprojects/Paket/blob/master/build.fsx#L149-L164

As long as nothing breaks when running on Linux/Mac, that should be fine.

[ctaggart]

The solution I went with was to merge.
https://github.com/fsprojects/Paket/blob/master/build.fsx#L183-L198