Quote:
Originally Posted by KevinH
Have you tried installing an updated c++ runtime library?
|
This just peaked my interest. On nearly all of the machines I test Sigil on, I'm using the VS2017 vc++ runtime. It's binary-compatible and is, in fact, considered the most recent version of the vc++ runtime for VS2015 (confusing, I know).
The reason I've been loathe to advise someone to upgrade to the VS2017 redistributable runtime is because it can't coincide with the older VS2015 redistributable. It will, in fact,
replace the VS2015 redistributable in add/remove programs. This in itself is not an issue as any application that requires the VS2015 runtime will work with the VS2017 runtime. The problem is that some applications don't check the proper registry keys to see if a compatible runtime is already installed. This can result in specious warning messages about VS2015 runtime being required when installing certain applications.
So I'm waiting as long as I possibly can to start distributing the vs2017 runtime with Sigil to allow other application installer packages to "get it right."
So if someone wants to try the latest VS2017 runtime with Sigil to see if it resolves their issues, there is no real danger. The only thing that might happen is a hinky app that doesn't follow the rules won't install. And you can always uninstall the VS2017 runtime and reinstall the VS2015 runtime provided you don't have any applications that were compiled with the VS2017 toolchain and require the VS2017 runtime (they're not
forward compatible). In which case, you'd already have/need the VS2017 runtime installed anyway.
In any case, now that I've confused the heck out of you with technobabble, feel free to download the
VS2017 redistributable from Microsoft and try it. Make sure you get the one for the version of Sigil you installed (x86 vs x64) or just install both.
P.S. the VS2015 redistributable runtime can be difficult to find/download from Microsoft's site without an account (albeit a free one). If you would happen to need to roll back, just uninstall the VS2017 runtime and then reinstall Sigil. It will install the VS2015 runtime when it detects no compatible version is already installed