locked
C++ redistributable 2017 installation removes silently C++ redistributable 2015 update 3 RRS feed

  • Question

  • Hello,

    on my computer:

    C++ redistributable 2015 update 3 - 14.0.24215 - ( both x86 & x64 )

    had been installed.

    After installing C++ redistributable 2017 - 14.10.25017 - ( both x86 & x64 )

    the C++ redistributable 2015 update 3 have been disappeared. They are no longer present. They have been silently removed during the installation of C++ redistributable 2017.

     

    I have two question:

     

    -- 1.  --  What is the reason for that    -    I mean in the past the C++ Redist 2015 package did not removed the C++ Redist 2013 package and the C++ Redist 2013 package did not removed the C++ Redist 2012 package, and so one...     they always left the previous Redist. package installed ...  why is the installation of the C++ Redist 2017 now behaving differently....   what is the reason for that ?

    -- 2. -- How can I make sure, that the C++ Redist 2017 installtion DOES NOT uninstall the C++ Redist 2015 Update 3 package ? 

     

     

    Thursday, August 3, 2017 1:27 PM

Answers

  • From the version numbers, it looks that VC++ 2017 runtime continues the VC++ 2015 line so it is actually the next (and better) update to VC++ 2015. It should work for apps built with both 2015 and 2017.

    -- pa


    • Edited by Pavel A Thursday, August 3, 2017 3:23 PM
    • Proposed as answer by Baron Bi Friday, August 4, 2017 1:51 AM
    • Marked as answer by ThePerfectWave Friday, August 4, 2017 10:14 AM
    Thursday, August 3, 2017 3:23 PM
  • It was actually documented in this blog post.

    This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.

    • Proposed as answer by Baron Bi Friday, August 4, 2017 1:51 AM
    • Marked as answer by ThePerfectWave Friday, August 4, 2017 10:14 AM
    Thursday, August 3, 2017 8:44 PM

All replies

  • From the version numbers, it looks that VC++ 2017 runtime continues the VC++ 2015 line so it is actually the next (and better) update to VC++ 2015. It should work for apps built with both 2015 and 2017.

    -- pa


    • Edited by Pavel A Thursday, August 3, 2017 3:23 PM
    • Proposed as answer by Baron Bi Friday, August 4, 2017 1:51 AM
    • Marked as answer by ThePerfectWave Friday, August 4, 2017 10:14 AM
    Thursday, August 3, 2017 3:23 PM
  • It was actually documented in this blog post.

    This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.

    • Proposed as answer by Baron Bi Friday, August 4, 2017 1:51 AM
    • Marked as answer by ThePerfectWave Friday, August 4, 2017 10:14 AM
    Thursday, August 3, 2017 8:44 PM
  • Ok thanks for your fast answers.
    Friday, August 4, 2017 10:15 AM