I'd like to take this a little bit further. I need to be absolutely sure that we are not encountering incompatibilities with off-line systems.
I had the following situation: My software (with off-line FNC Maps and a local maptile server) was running fine on a Windows10 laptop. Installation was in January 2022, and the laptop was isolated from internet connections. Over the next 6 months, I would keep my development environment FNC Maps+Core up to date with the latest releases from TMS. In ~August 2022 I released and installed a new version of the software on the laptop. The software would now crash occasionally. I then connected the laptop to the internet. After a Windows update (Evergreen?), there were no problems with running of the new software. (Unfortunately, I do not have a record of WebView2 Runtime or exact FNC Maps/Core releases for Jan 2022/August2022.)
@Pieter, talking about your tests above you say "If something is not functioning properly after the release, we typically check if there is a need for an update of the DLLs, or if something is wrong with the edge chromium version and immediately release an update mentioning this in the version history. Right now, the browser is running stable for quite a while now. Sometimes for accessing the latest APIs, there is a need for new DLLs...."
I can programatically determine the current version of WebView2 Runtime. Now I need to know the minimum, safe version of WebView2 Runtime that I can use in conjunction with any release of FNC Maps+Core (which TMS has obviously tested). And, how can I find out that minimum, safe version programatically?
(And do you think that my hypothesis of an incompatibility between a newer FNS Maps+Core with an older WebView2 Runtime may be plausible?)