/build/static/layout/Breadcrumb_cap_w.png
04/15/2019 330 views

Hello Guys,

After spending couple of hours researching and looking for the solution over the internet, i figured out this is my last resort.

I'm working as a packager for one firm and the issue I'm facing is as follows:

For visualization and VM management we are using VMWare vSphere. The latest version of VMtools installs the  Visual C++ 2017 Redistributable as well.

We pack Redistributable as separate packages and are used as prerequisites for other applications we pack.

Since VC2017 is now present on the VMs, application that I need to pack wont install it so I'm looking for the best way to check if applications require VC2017 or not.

Did anyone had the similar problem ?
What would you guys suggest and what would be the best way to check this?


1 Comment   [ + ] Show comment

Comments

  • Are you looking to check to see if the application you're packaging requires Visual C++, or checking if the computer you're going to install the application on is missing Visual C++?
    • Yeah, I'm missing the way to check if application installs VC2017 alongside itself, since its already present on the system.

All Answers

0

You're working as a packager and asking this question?!? Hmmm...

The obvious first step is to edit the ARP entry which is where most installers go to check installed state.

Answered 04/16/2019 by: VBScab
Red Belt

  • What should i edit there?
    • This content is currently hidden from public view.
      Reason: delete For more information, visit our FAQ's.
This content is currently hidden from public view.
Reason: delete For more information, visit our FAQ's.
0

Have you tried installing VC++ 2017 onto a system that already has it installed?  A lot of runtimes are designed to just reinstall without issues.  You can make any MSI capable of repeated reinstallation by removing the advertising tables.  Any MSI also logs registry information when it installs and this can be found easily - you can run a bit of vbscript that instantiates the windows installer object and allows you to retrieve all the MSI installs on the system and then look for the particular GUID or appname.  There are just so many ways of doing this that you are truly spoilt for choice.

The optimal solution depends on how you are deploying the apps in your environment and how you implement scripts to check the environment before allowing deployment to commence.

Answered 04/28/2019 by: EdT
Red Belt

0

1. We need to validate the requirement on vanilla build .

2. Try to look into logs ( application logs/temp) , see if there are entry for checking for visual redist. If installer is MSI , we can look into tables to validate.


Best way would be test it on machine where nothing is installed , preferably not on VMware ( if they install visual redist for running vmtools).

There are other tools which can help us like virtualbox or Hyper-V Vms.

Answered 05/06/2019 by: rock_star
2nd Degree Black Belt