Closed TheAngryByrd closed 8 years ago
:+1: thanks!
I was wondering if there are any updates on this issue?
I added profile 259 support in my fork (before noticing this issue), but took a slightly different approach of adding a second .fsproj file specific to profile 259. The resulting nuget package keeps the existing lib/net40 folder, and adds lib/portable-net45+win+wpa81+blahblahblah. I though doing it that way would have less of a chance of breaking existing consumers.
Would it be worth creating a separate PR?
@jlewicki It would, that's the preferable approach
Unnecessary after #74
This is the initial pull request to address #29 and #54 . This is bound to break things. One of them being support for .net 4.0 Please test aggressively and provide feedback .