Quote:
Originally Posted by RbnJrg
But I don't know why Sigil with its "own" runtime doesn't work in my system.
|
It would work just fine _IF_ the other runtime wasn't already installed. The problem isn't the version of the runtime Sigil that tries to install
itself. The problem is caused by Sigil trying to install its version
in addition to (or over top of) the one you have installed.
That is what shouldn't be happening. I'm just lamenting the fact that Windows makes it so difficult to manage this situation from a deployment standpoint. Having to check for different versions of different language editions of the same runtime just isn't feasible. Especially when language-specific versions of a C++ runtime (whose version numbers clearly don't match their counterparts') doesn't even make a little bit of sense to me.
Alas.