search

andymanic / OSRTT

OSRTT (Open Source Response time tool) is a complete LCD monitor response time testing solution made as easy and accessible as possible.
https://andymanic.github.io/OSRTTDocs/
Other
55 stars 4 forks source link

Running launcher from GitHub code #11

Closed WoodyPWX closed 1 year ago

WoodyPWX commented 1 year ago

Hello there,

I'm using OSRTT source code from GitHub, main branch. If I open OSRTT Launcher.sln in both VS2019 (or VS2022) and compile, it fails on this:

Build started... 1>------ Build started: Project: OSRTT Launcher, Configuration: Debug Any CPU ------ 1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(3476,5): error MSB3322: Unable to get MD5 checksum for the key file "OSRTT Launcher_1_TemporaryKey.pfx". Could not find file 'C:\Temp\OSRTT\OSRTT Launcher\OSRTT Launcher\OSRTT Launcher_1_TemporaryKey.pfx'. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Solution Explorer is showing these .pfx files missing: image

If I disable this signing: image

I can compile and start the launcher, but it never detects my OSRTT PRO unit, unlike your prebuilt version: image

The VS output window is spamming: The system cannot find the path specified.

Regards, Tomas

WoodyPWX commented 1 year ago

I think it's trying to run this: image so I've set correct working directory for debugging into directory with your downloaded build, including that file, so it's all good now :)

andymanic commented 1 year ago

You beat me to it! It uses the arduino CLI to detect which COM port to connect with so needs the program in the correct directory. As for the key files, I forgot they'd be linked in the SLN. Disabling signing or generating your own key is the fix and again you've beat me there.

WoodyPWX commented 1 year ago

Thanks for the clarification!