Skip to content
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

If reference assembly exists for nuget library, no HintPath is added #3443

Closed
kzu opened this issue Sep 14, 2016 · 3 comments
Closed

If reference assembly exists for nuget library, no HintPath is added #3443

kzu opened this issue Sep 14, 2016 · 3 comments
Labels
Resolution:Duplicate This issue appears to be a Duplicate of another issue
Milestone

Comments

@kzu
Copy link

kzu commented Sep 14, 2016

from: https://bugzilla.xamarin.com/show_bug.cgi?id=43915#c18

It comes down to Nuget on Windows. Under Xamarin Studio on Mac when you add the FSharp.Core Nuget package it adds a reference to the correct mobile platform and adds a HintPath to the reference like so

<Reference Include="FSharp.Core">
  <HintPath>packages\FSharp.Core.4.0.0.1\lib\portable-net45+monoandroid10+monotouch10+xamarinios10\FSharp.Core.dll</HintPath>
</Reference>

This tells the build system to look for FSharp.Core in the nuget package directory.

Under Visual Studio this hint path is NOT added to the reference. As a result the system ALWAYS picks up the System provided FSharp.Core which is the older version. Hence the error.

Adding the correct HintPath to the project file seems to fix the issue. But why does Nuget NOT add the hint path in the first place is the real question here.

Is this by-design?

@yishaigalatzer
Copy link

This is a duplicate of a known bug in the F# project system. We discussed with Don Syme and agreed that the fix will need to go there.

@rrelyea can you please find and dedup the issue.

@idg10
Copy link

idg10 commented Aug 17, 2017

This looks like it could be a duplicate of #1510 - although that issue purports to be about a Numerics component, it looks like it's caused by the basic root issue described in this issue.

The issue that had been tracking this over in F# was dotnet/fsharp#939 but that got closed without it being fixed. Someone ran into this again recently, and I thought it might be helpful to put together a timeline for this bug which you can find at dotnet/fsharp#3415 (comment)

@nkolev92
Copy link
Member

nkolev92 commented Feb 1, 2018

Duplicate of #1510.

@nkolev92 nkolev92 closed this as completed Feb 1, 2018
@nkolev92 nkolev92 added this to the 4.7 milestone Feb 1, 2018
@rrelyea rrelyea added the Resolution:Duplicate This issue appears to be a Duplicate of another issue label May 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution:Duplicate This issue appears to be a Duplicate of another issue
Projects
None yet
Development

No branches or pull requests

5 participants