- folks can now build a release/debug build without having a key
locally.
- when we want to publish a release that has been signed you can use:
`-p:SignAssemblies=True`.
- I know you already have a PFX file, so you'll need to convert it to
a strongnamekey (there are lots of tools for this online, but if you
need any help let me know).
start prepping for multi os build workflows by allowing us to build
with the newer `dotnet` cross platform tooling, this also just upgrades
us to the latest dotnet lts
i also started cleaning up the csproj file so it's a bit more clear
to read for external parties, and hopefully easier to read. part of this
was just done by the dotnet upgradeassistant, part of it was required to
make it work without warnings on the latest dotnet build, other parts
were just me cleaning up best practices (like removing the home
directory of a certain user :) they can still specify it manually if
they need too).
refs #1
this helps fix the initial "build fail due to missing key" if someone
just checks out the project loads it up, or tries to build it in debug
mode. since releases are really the only things we should be signing it
was quick to move it in there.
long term, we still want folks being able to build release builds
locally too, without a key/generating one, and only sign the real
releases we distribute to folks, but this gets me unblocked to start
porting the build from MSBuild (something windows only), to the newer
dotnet build stuff that is cross platform
