-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Referencing Paket.Core / Exe problems. #1958
Comments
|
Would you want to have a special package? Without ILMerged stuff? |
|
but paket.core is not ILMerged. What issue do you see with chessie? |
#r @"packages\Paket.Core.3.23.1\lib\net45\Paket.Core.dll"
#r @"packages\Chessie.0.0.1\lib\net40\Chessie.dll"
open Paket
open Chessie
let dependenciesFile = Dependencies(@"paket.dependencies")gives an error Although in the editor window it does not show any errors. |
|
is that the correct chessie version? |
|
That's the one that Nuget pulled down. ;-) |
|
Perhaps there's a minimum required version of Chessie that should be specified in Paket.Core? |
|
I guess that's the root cause. https://www.nuget.org/packages/Paket.Core doesn't specify a version. brb |
|
please retry |
|
Same. |
|
against chessie 0.6? |
|
Correct |
|
wtf |
|
can you zip that sampe and add it here? |
|
@forki let's review tomorrow / over the weekend together. |
|
Closing, nupkg now specify Chessie version |
Referencing both Paket.Core or Paket from the NuGet feed has issues related to (I believe) the fact that we ILMerge stuff in to both versions.
With Paket.Core, you'll get errors regarding Chessie. With Paket.exe, you have issues with FSharp.Core duplicates and invalid casts.
Perhaps someone can better explain this than me :-) What's the best way to solve this though?
The text was updated successfully, but these errors were encountered: