Quote:
Originally Posted by BetterRed
I get twitchy when application packages install '3rd Party' software, especially if its into the Windows directory without a) asking for my permission, b) asking me to agree to the license conditions. And particularly when it's a discrete un-installable item that I wouldn't even have noticed being installed had I taken my eye off the install.
BR
|
I don't know what answer you're expecting here, and I don't understand why you're complaining about it here.
The separately uninstallable, side-by-side assembly package is how Microsoft wants applications to handle deployment of their C++ library runtime in VS2013 compiler artefacts.
This is their own recommended packaging mechanism. See
http://msdn.microsoft.com/en-us/library/ms235299.aspx for details (please make sure to also read the sub-articles.)
That package is signed by Microsoft thus its integrity is as guaranteed as you can get (if you're worried about this, you shouldn't be running untrusted binaries, you should audit the code and then compile it yourself), and installs as a SxS assembly activable through the executable's embedded manifest thus in no way affects any other application on the system (unless their manifest specifically requests this particular version of the VS2013 runtime--in which case you probably already have it installed!).
If any of that runs contrary to how you expect the system to work, I suggest you open a ticket with Microsoft's Servers and Tools division, who is in charge of this. Complaining to Sigil's developers is like complaining to some random driver off the street who drives the same car model that you are that you don't like how the transmission works in that model.