These notes are aimed at developers wishing to use Visual Studio 2019 (VS 2019) or other tool to continue development on, or make enhancements to MSFS2020-PilotPathRecorder.
Please share knowledge here that could help to make future development more pleasant and/or less frustrating!
See the build file for details, but
know that when you push a Git tag whose name ends with -release
to the repository, a new release will be built and created
using the current version of the code in that branch.
If when building the project you receive the error:
Unable to find manifest signing certificate in the certificate store.
You may have enabled manifest signing without having created the proper certificate. See below for ways to address this error, involving alternatives such as creating your own certificate, or to leave signing disabled.
Using VS 2019, it's easy to create and sign with your own "test" certificate.
With the project selected in the Solution Explorer:
- Select
Properties
(e.g.,Alt + Enter
) - Select
Signing
- Select
Create Test Certificate...
- Enter a new password
- Ensure
Sign the ClickOnce manifests
is checked - Save the change (e.g.,
Ctrl+S
)
Disabling the signing is appropriate for development purposes; however, it's better to create and sign the released program with a certificate (see above.)
You can disable the signing of the manifest file by changing the SignManifests
configuration value from true
to false
. Within VS 2019 for example, this
can be accomplished with the project selected in the Solution Explorer:
- Unload the project (e.g.,
Project >> Unload Project
) - Edit the Project File (e.g.,
Project >> Edit Project File
) - Change the value for
SignManifests
fromtrue
tofalse
- Reload the Project (e.g.,
Project >> Reload Project
)
Within VS 2019, you can disable signing with the project selected in the Solution Explorer:
- Select
Properties
(e.g.,Alt + Enter
) - Select
Signing
- Ensure neither the
Sign the ClickOnce manifests
checkbox nor theSign the assembly
checkbox are checked - Save the change (e.g.,
Ctrl+S
)
Once the desired change is made, cleaning and rebuilding the project without the error depicted above should be possible.
The following additional endpoints (see LiveCam) can be helpful during development or customization of LiveCams:
http://localhost:8000/eval/Model.values
(shows current real-time LiveCam values)http://localhost:8000/eval/template
(renders a templatePOST
ed to this endpoint)
The default handler for an unrecognized HTTP request will attempt to read and return the resource (file) named by the URL path. This enables built-in resources to be accessed by liveCam templates. As of this writing, there is no way to load new resources from the dialog; however, they can be manually copied into the application runtime directory, if needed.