install - Correct way to do vc10 runtime installation -
I want to extract my hair from installing VC10 runtime!
I have two applications, each with its own installer to ensure that everyone can be sent as standalone, in each installer, VCDIDEX. Includes XE stuff which installs VC10 runtime.
Now, an installer includes 'SP0' runtime - this is a while ago - it is called 'i0', and one also includes 'sp1' runtime - it is now being created - Call it 'i1'
If my user installs alone or alone i1, then everything is great if my user first installs i0 and then i1, everything is great.
However, if my user installs i1 first, then runtime installation fails when he tries to install i0.
Redists by hand I see that the SP1 installer gets bothered when it sees that SP1 is already installed.
Apart from this, the fact is that the culprit seems stupid, how will I score it? Is there a 'force' flag, can I give the SP0 installer? Is there a way to 'properly' check the runtime - and which version of it - is already installed?
A better way to do this may be to privately deploy the VC runtime with your application. . To do this, simply include msvcp100.dll and msvcr100.dll in your installer package. In this way, your application system will not use CRT and you will not be able to run redistributions if you have other dependencies, you can know which files are included.
Comments
Post a Comment