Dependency on old vcredist causes install failure

[wertzui]

Whenever I want to upgrade to the newest version, I get the following error:

You have dotnetcore-sdk v2.2.104 installed. Version 2.2.105 is available based on your source(s).
dotnetcore-sdk not upgraded. An error occurred during installation:
Updating 'vcredist140 14.16.27027.1' to 'vcredist140 14.12.25810' failed. Unable to find versions of 'visualstudio2017-workload-azure, visualstudio2017-workload-manageddesktop, visualstudio2017-workload-netcoretools, visualstudio2017-workload-netweb, visualstudio2017-workload-node, visualstudio2017-workload-universal' that are compatible with 'vcredist140 14.12.25810'.

I can ignore the dependencies and it will work without problems, but this removes the whole point of automatically updating to the newest version without manual intervention. And since it is working with the newer vcredist version, I think it should not require an old version.

[jberezanski]

I realize it's been over a year, but I have only noticed this issue now, sorry.

For the record: the dependency in dotnetcore-sdk specifies only a minimum acceptable version of vcredist140 (it does not require this exact version) and in a typical environment it should not force installation of an earlier version on top of an existing later one. In fact, if you install dotnetcore-sdk on a clean system, you will get the latest vcredist140 available on chocolatey.org. So there seems to be something wrong with your Chocolatey setup.

Actually, it's even weirder. dotnetcore-sdk depends not on vcredist140, but on vcredist2015 and it is vcredist2015 which depends on vcredist140. But the latest vcredist2015 (from February 2017) depends on vcredist140 14.0.24215.1 (again, as a minimum), so I have no idea where version 14.12.25810 came from.