VCRedist修订历史和时间表? [英] VCRedist Revision History and timeline?

查看:81
本文介绍了VCRedist修订历史和时间表?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是否有一种方法可以获取修订历史记录/时间表,以及有关Microsoft已发行的所有这些不同VCRedist_x86版本的少量文档的信息?另外,如果您需要返回并获得较早的测试包,该怎么办? 某人很难找到最新版本,更不用说自定义#了.这不是一件容易的事.有人告诉我8.0.50727.5069是最新的,但为什么我有一个8.0.59193?这是没有道理的.谁能流下 关于如何了解这些更新的进度的一些启示?

Is there a way to get a revision history/timeline and maybe a small amount of documentation on all these different VCRedist_x86 versions that have been released by Microsoft?  Also what if you needed to go back and get an earlier package for testing?   It is hard enough for someone to find the latest version let alone a custom #.  This is not an easy task.  I am told that 8.0.50727.5069 is the latest, but why do I have one that is 8.0.59193?  This does not make sense.  Can anyone shed some light on how to understand the progression of these updates?

8.0.50727.4053
8.0.50727.42
8.0.50727.5069
8.0.59193

8.0.50727.4053
8.0.50727.42
8.0.50727.5069
8.0.59193

推荐答案

为什么需要自己进行部署?应用程序应该提供所需的任何版本的VC运行时,并且,如果有VC运行时安全更新,那么如果它们选择不让Microsoft的Windows Update来保管,则需要对其进行更新.
Why you need to deploy by yourself? Apps are supposed to ship whatever version of the VC runtime they need, and if there is a VC runtime security update, then the apps need to be updated, if they choose not to let Microsoft's Windows Update to take care of it.


这篇关于VCRedist修订历史和时间表?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆