Currently, the AprsSharp version sent to the APRS-IS server is hard-coded in to the connection logic. However, the version used for publishing packages is saved in the package properties (Directory.Build.props sets it across all projects/assemblies).
This changes our code to use reflection to get the assembly version of the AprsIsConnection being used to communicate to the server. Thus eliminating one place to remember to change the version on each release. It should now only be required to update the build properties in the code on each version.
Changes
Use reflection to reference assembly version for identifying software version to APRS-IS servers
Validation
Updated tests
Ran AprsSharp CLI and noted the version had updated to the full semver "0.1.0" string
Temporarily updated just the AprsIsConnection version to "0.1.1". Verified that APRS-IS saw "AprsSharp 0.1.1" while local --version flag said 0.1.0 still. This verifies it's querying the AprsIsConnection assembly version and not the entrypoint assembly.
Description
Currently, the AprsSharp version sent to the APRS-IS server is hard-coded in to the connection logic. However, the version used for publishing packages is saved in the package properties (Directory.Build.props sets it across all projects/assemblies).
This changes our code to use reflection to get the assembly version of the AprsIsConnection being used to communicate to the server. Thus eliminating one place to remember to change the version on each release. It should now only be required to update the build properties in the code on each version.
Changes
Validation