Instead of having to start with the SDK solution create NuGet packages that you'll then be able to add to your app.
[x] Let's use our NuGet-publishing GitHub workflow if possible.
[x] Remove the note from WorkingWithHastlayer.
[x] Add a NuGetTest solution that runs the verification tests with the NuGet packages.
[x] Hardware Frameworks need to be packaged as well, and then used as plain files somehow.
[x] Is it better to create a different solution just for NuGet publishing, without a lot of the sample and test projects, or make affected projects <IsPackagable>false</IsPackagable> (publish-nuget can already ignore such projects without erroring out)?
[x] Figure out something for Lombiq.Arithmetics and Hast.Vitis.HardwareFramework. These most possibly need their own NuGet publish workflows. Publish them first.
[x] Add NuGet-referencing verbiage to Hastlayer.cs:
"Did you install the necessary NuGet package for the given device?" for "There is no supported device..."
"Did you install the necessary NuGet package for the given device?" for "No suitable hardware implementation..." (device support packages should already depend on the necessary composer packages, hence the same text).
[x] Should we package up Hast.Console, perhaps as a .NET Tool? - This doesn't make much sense, no.
Instead of having to start with the SDK solution create NuGet packages that you'll then be able to add to your app.
<IsPackagable>false</IsPackagable>(publish-nugetcan already ignore such projects without erroring out)?Lombiq.ArithmeticsandHast.Vitis.HardwareFramework. These most possibly need their own NuGet publish workflows. Publish them first.Hast.Console, perhaps as a .NET Tool? - This doesn't make much sense, no.Prerequisite: https://github.com/Lombiq/Hastlayer-SDK/issues/34
Jira issue