Fabulous - Drop Paket?

Paket is used awkwardly in Fabulous. It doesn’t really manage anything.

It is used to download FAKE 4, download some dependencies and lock version for the NuGet packages (paket.template). But the .NET Standard libs manage their own dependencies using PackageReference, and the samples only directly reference the downloaded dependencies (Paket doesn’t manage the samples). https://github.com/fsprojects/Fabulous/blob/58bbfd79558f964270eeb66ba75acddea93f50da/Samples/AllControls/Droid/AllControls.Droid.fsproj#L91

It’s quite confusing.

I would like to uniformize the repo by going either full Paket or full NuGet. Problem is:

• Paket is not supported by Visual Studio for Mac (breaks IntelliSense, Restore working only with msbuild /t:Restore)
• Paket doesn’t seem to support dotnet/SourceLink (something I’d like to add later)
• We have to make sure by hand that Paket and Fabulous use the same version of the dependencies

So I wonder: Maybe it would be better to drop Paket and go full NuGet (PackageReference)? We can achieve the same “one place to manage all the dependencies” with a Directory.Build.props file.

What do you think?

[TimLariviere]

@slang25 Had to abandon CentralPackageVersions, because VS for Mac ignores it… But I still used the way CentralPackageVersions work and replaced my variables with PackageReference Include/Update

[TimLariviere]

Ah thanks, this looks interesting!