teacherjae.blogg.se

1. #WHTIS A VISUAL STUDIO 2015 PRODUCT KEY FOR INSTALL#
2. #WHTIS A VISUAL STUDIO 2015 PRODUCT KEY FOR UPDATE#

The only problem is that my application is 32-bit running on 64 and I need the 32-bit version of the run-time. HKLM\Software\Microsoft\DevDiv\Servicing\14.0.

#WHTIS A VISUAL STUDIO 2015 PRODUCT KEY FOR INSTALL#

Then my install comes along and checks the registry setting you mentioned.

#WHTIS A VISUAL STUDIO 2015 PRODUCT KEY FOR UPDATE#

The machine in question has Visual C++ 2015 update 3 圆4 already installed by another application. The files are probably installed to standard locations so that might be an easier thing to check. Maybe a better approach would be to check a file version instead of dealing with installation package information.

Using the version comparison works fine, but again its tied to that product code. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ I guess I could ask if there is a way to handle compound conditions in prereq editor.įor now, we're living with this as the search criteria. I know this might be confusing so fire any questions if you think you can help. Is there any way I can better handle the installation of VC++ runtimes (x86) so that I don't run up against conflicts attempting to install our minimum over a more recent version. So I don't have a way using the prereq editor to use compound conditions. The only issue here is that the version information is not held in a single value. This key has x86 and/or 圆4 keys sub-keys, which hold versioning information. HKLM\Software\Microsoft\VisualStudio\14.0\VC\Runtimes. I did find another code that would be nice to use as it is also not tied to a product code registry key. The problem is that if a newer version, with a different product code is in place, my prerequisite installer will fire and fail as Microsoft doesn't allow that I guess.Ĭhecking for the 圆4 version is nice because it just deals with the actual version of the runtime installed and not specific to that versions install package. Currently, the requirement is checked for installation by checking a version under its Product Code registry key. I'm trying to find a better way to detect the presence of our minimum VC++ 2015 requirement without checking version specific registry information specific to its version.