confirmed this is a bug.

It looks like the following tags in the props file are ignored.

<DisableImplicitFSharpCoreReference>true</DisableImplicitFSharpCoreReference>        
<DisableImplicitSystemValueTupleReference>true</DisableImplicitSystemValueTupleReference>

if you set those manually into your fsproj then it works and it uses FSharp.Core 4.6

I tested this multiple times with older SDKs - why is it not loading this variables from obj/*.paket.props anymore!?

/cc @KevinRansom @cartermp

ok scratch that. It's a timing issue.
It works as soon as the props file is there, but the very first build is creating the props file and that's too late. So I guess we need to move it back into paket's targets file.

references: #3721 #3725

Ok please retry with latest.

But keep in mind you need to nuke obj file and check that paket's targets file is already updated. So do a paket restore or something before you build.

Paket 5.241.6 seems to do the job 👍

But then I'm using FAKE 5.19 to build and it's using Paket 5.241.2 that overwrites targets file with older version.
Until FAKE catches up with newer version of Paket I can workaround that with following:

dotnet paket restore // extracts targets file version 5.241.6
PAKET_SKIP_RESTORE_TARGETS=true dotnet fake build  // prevent extracting paket targets file

Unless there's a better way of doing that?

The other way is to put the tags into the fsproj as described above.

/cc @matthid

Ok cool - placing those properties in fsproj worked as well 👍
For me issue can be closed noe unless you want to keep it open

Unless there's a better way of doing that?

No, that's why we have that option. I'm trying hard to only ship "stable" versions of Paket with Fake and Fake will always recommend using that version. Another possible option is to use the version FAKE recommends and apply the workaround (setting those MSBuild variables) to the directory.props

It doesn't matter. In any case a new fake release is required and that always takes a while, so feel free to fix when appropriate and then it will flow into fake as usual ;)

I don't feel like this is critical enough to justify rushing a release train. Several workarounds are available.