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

Add FSharp.Core package reference with IsImplicitlyDefined = true #3678

Closed
Alxandr opened this issue Oct 2, 2017 · 8 comments
Closed

Add FSharp.Core package reference with IsImplicitlyDefined = true #3678

Alxandr opened this issue Oct 2, 2017 · 8 comments
Labels
Bug Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code. Resolution-By Design

Comments

@Alxandr
Copy link

Alxandr commented Oct 2, 2017

I just wrote a tool that extracts ProjectReference entries from a msbuild project. It removes any references that is automatically added by the framework by checking for metadata IsImplicitlyDefined. This works for C# and VB, but F# does not add this metadata.

Also, looking at this it seems the same is true for System.ValueTuple.

Repro steps

Create a fsharp SDK based project (for instance dotnet new classlib --language F#). Extract all ProjectReferences.

Expected behavior

FSharp.Core should be added with metadata IsImplicitlyDefined equal to true.

Actual behavior

FSharp.Core is not added with IsImplicitlyDefined.

Known workarounds

Manually add it, which defeats the purpose altogether.

Related information

.NET Command Line Tools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.0.0/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d
@dsyme
Copy link
Contributor

dsyme commented Oct 13, 2017

@KevinRansom Could you take a look at this please?

@0x53A
Copy link
Contributor

0x53A commented Oct 17, 2017

It looks like this would also solve other issues - according to this comment, PackageReferences without IsImplicitlyDefined take precedence over ones with it. So this would fix the issue where it is impossible to override the implicit FSharp.Core later, which was an issue in Paket.

@dsyme
Copy link
Contributor

dsyme commented Feb 24, 2018

@KevinRansom did you take a look at this?

@dsyme dsyme added Bug Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code. labels Feb 24, 2018
@cartermp cartermp added this to the 16.0 milestone Aug 29, 2018
@cartermp cartermp modified the milestones: 16.0, 16.1 Feb 21, 2019
@cartermp cartermp modified the milestones: 16.1, 16.2 Apr 23, 2019
@cartermp cartermp modified the milestones: 16.2, Backlog Apr 30, 2019
@jeffkl
Copy link

jeffkl commented May 14, 2019

I'd like to send a PR to fix this, may I submit it?

https://github.com/microsoft/visualfsharp/compare/master...jeffkl:fix?expand=1

@cartermp
Copy link
Contributor

@jeffkl absolutely!

@cartermp
Copy link
Contributor

Closing out as per the resolution of #6730

@knocte
Copy link

knocte commented Jul 30, 2022

Closing out as per the resolution of #6730

So then F# will never be compatible with Central Package Management (Nuget new feature)? See NuGet/Home#11949 (comment)

@cartermp
Copy link
Contributor

Things can always change, and you can always just use paket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code. Resolution-By Design
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants