As explained in the instructions, it is necessary to have both the .exe and the .exe.config file in the same folder when starting the program.
If it is missing, corrupted or not loaded for any reason (i.e. windows blocks it), the program will start, not connect and crash on first usage (key press, frequency change).
I don't think there's a way to fix this as there doesn't seem to be any other way to instruct the newer .net versions to load the older (simconnect) assembly properly, but to use the config file.
Maybe a missing config can be checked on startup to notify the user.
As explained in the instructions, it is necessary to have both the
.exeand the.exe.configfile in the same folder when starting the program.If it is missing, corrupted or not loaded for any reason (i.e. windows blocks it), the program will start, not connect and crash on first usage (key press, frequency change).
I don't think there's a way to fix this as there doesn't seem to be any other way to instruct the newer .net versions to load the older (simconnect) assembly properly, but to use the config file.
Maybe a missing config can be checked on startup to notify the user.