Overhaul the NuGet packaging infrastructure and the way the Core binaries get acquired. #146
Commits on Nov 14, 2022
-
Start writing an MSBuild script that creates NuGet packages for the c…
…ore. For now it downloads the artifacts from GitHub Releases.
Commits on Nov 15, 2022
-
-
-
-
Restore the template packages.
And add a property to them that seems to save time.
-
-
Remove the "Install/Download tiledb" steps from CI.
And disable fail-fast in the Run-Tests action matrix.
Commits on Nov 16, 2022
-
Remove all CI jobs except of Run-Tests.
Now that we don't use a nuspec to pack the C# library there are little reasons to specifically test it with a packed NuGet package. The Release job also went away; it would upload the 0.0.0-local package. We need a dedicated release workflow.
-
Remove RollForward from TileDB.CSharp.
It does not apply to libraries.
Commits on Nov 17, 2022
-
Update package metadata and move them to a dedicated file.
I had originally removed the nuspec files from the native packages but changed my mind for aesthetic reasons since they generate an empty .NET Standard 2.0 dependency group.
-
Add support for generating development editions of the native packages.
They have SemVer 2.0 versions that identify the branch.
-
Enable Central Package Management with package source mapping.
And support changing the native package under a different name in development builds.
-
-
Refactor the nightly build workflow to use native development NuGet p…
…ackages. The core is built in separate jobs and not once for each .NET version.
-
-
Require
VersionandVersionTagto be specified.Make the version tag optional for development builds. And fail if no native binaries were found in development builds.
-
Commits on Nov 23, 2022
Commits on Nov 24, 2022
-
Remove the RID-specific build instructions in the metapackage's descr…
…iption. This package is not intended to be directly referenced by the average developer, at least not without `TileDB.CSharp`.