I am using Visual Studio version 16.11.3 in creating a UWP application package.
Upon completing the packaging and checking the output, the "Dependencies" folder containing the "Microsoft.VCLibs.x64.14.00.appx" has a higher version (14.0.30035.0) than is currently installed on the target machines (14.0.29231.0).
This causes issues when installing the 'appxbundle' file to the target machine as the higher version is not yet installed.
I need help in figuring out on a couple of issues:
If possible, can we make the dependency version on the package output to use the older version on the target machine instead of the higher one? To avoid the installation issues.
What triggers the change/update in the version of "Microsoft.VCLibs.x64.14.00.appx" when no code changes are made to update that dependency? Can it be avoided?
The only solution I have found before was to never update my Visual Studio version to have same dependency version every time I create a UWP package. However, is a problem for some dev machines that already has installed the latest Visual Studio version and already has the latest dependency version.