Detecting Install Conditions - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

chuckc3
Posts: 12
Joined: Fri Feb 19, 2010 4:31 pm

Detecting Install Conditions

I have to add a number of different prerequisites to my application installer including:

- Office 2003 PIAs
- VSTO SE RunTime
- Crystal Reports Runtime for VS 2008

I'm having trouble figuring out what the install conditions should be to detect if these items are already installed or not...I've looked all over the web and can't find that information anywhere. Does anyone have a recommendation on a general method to determine the install conditions for these applications?

Thanks,

Chuck
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Detecting Install Conditions

Hi Chuck,

The best way to see what install conditions you should use is to install the prerequisites on a clean machine and see what changes take place.

Usually the easiest way is to see changes that affect the registry hive, HKCU or HKLM. You can also see if certain files are installed on the machine,
for example a specific DLL file or EXE and search for them in the Install Conditions tab, Searches group.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
chuckc3
Posts: 12
Joined: Fri Feb 19, 2010 4:31 pm

Re: Detecting Install Conditions

Thank you Bogdan,

I appreciate your quick reply...I did a quick web search to see if I could find a tool that would help do a before-and-after analysis of what has changed in a particular installation. I found a tool that looks good for this purpose:

http://www.kephyr.com/systemsherlocklite/index.phtml

I'm going to give it a try.

I think it would be a good idea for the Advanced Installer team to build up a library of the data associated with these prerequisites such as:

- the download URL
- Install Conditions
- Etc.

It will save users a lot of time and effort finding this information for themselves. I will be glad to contribute what I find to that library...is there a place to post this information? I'll just add it to this thread for now.

Thanks,

Chuck
chuckc3
Posts: 12
Joined: Fri Feb 19, 2010 4:31 pm

Re: Detecting Install Conditions

I found a better tool for detecting install conditions...the SystemSherlock tool I mentioned is free, but it is a bit cumbersome to use and doesn't have a very good UI. Another tool I found is called "Total Uninstall". It's much easier to use and has a pretty good UI interface. It does a pretty good job of capturing all changes to files and the registry that take place during an install...you can then scan through that log file and determine what to use for an install condition. Here's some examples I did:

Crystal Reports Basic Runtime for VS2008:

• Install Condition: Registry Key Exists: HKLM\SOFTWARE\Business Objects\10.5\Crystal Reports
• Download Location: https://smpdl.sap-ag.de/~sapidp/0120025 ... 008sp1.exe


VSTO 3.0 RunTime:

• Install Condition: Registry Key Exists: HKLM\SOFTWARE\Classes\Installer\Features\05835BF8A6427053A8ED000690F3EF6A
• Download Location: http://download.microsoft.com/download/ ... stor30.exe

VSTO SE RunTime:

• Install Condition: Registry Key Exists: HKLM\SOFTWARE\Microsoft\vsto runtime Setup\v2.0.50727
• Download Location: http://download.microsoft.com/download/ ... /vstor.exe

Office 2003 PIAs:

• Install Condition: Registry Key Exists: HKLM\SOFTWARE\Classes\Installer\Features\9040941900063D11C8EF10054038389C
• Download Location: http://download.microsoft.com/download/ ... 003PIA.EXE
(Note – the above is a zip file and won’t work as a download – you have to download the Zip file, extract it, and use the MSI)

Office 2007 PIAs:

• Install Condition: Registry Key Exists: HKLM\SOFTWARE\Classes\Installer\Features\00002105501100000000000000F01FEC
• Download Location: http://www.microsoft.com/downloads/deta ... laylang=en
(Note – the above is a zip file and won’t work as a download – you have to download the Zip file, extract it, and use the MSI)

SQL Server CE:

• Install Condition: Registry Value: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server Compact Edition\v3.5\ENU\DesktopRuntimeServicePackLevel = 1
• Download Location: http://download.microsoft.com/download/ ... NU-x86.msi

I hope that helps someone else who has this problem...

Chuck
chuckc3
Posts: 12
Joined: Fri Feb 19, 2010 4:31 pm

Re: Detecting Install Conditions

With the help of Bogdan on the AI Team, I have found a problem with the install launch conditions I posted here - the launch conditions I posted work almost all the time, but I found a problem with 64-bit systems. Here's a better solution for some of the launch conditions:

VSTO 3.0 RunTime:

• Install Condition: Registry Value Exists: HKLM\SOFTWARE\Microsoft\vsto runtime Setup\v9.0.21022\Install
• Download Location: http://download.microsoft.com/download/ ... stor30.exe

VSTO SE RunTime:

• Install Condition: Search for Product Code: {388E4B09-3E71-4649-8921-F44A3A2954A7}
• Download Location: http://download.microsoft.com/download/ ... /vstor.exe

Office 2003 PIAs:

• Install Condition: Search for Product Code:{91490409-6000-11D3-8CFE-0150048383C9}
• Download Location: http://download.microsoft.com/download/ ... 003PIA.EXE
(Note – the above is a zip file and won’t work as a download – you have to download the Zip file, extract it, and use the MSI)

Office 2007 PIAs:

• Install Condition: Search for Product Code: {50120000-1105-0000-0000-0000000FF1CE}
(Note – the above is a zip file and won’t work as a download – you have to download the Zip file, extract it, and use the MSI)

SQL Server CE:

• Install Condition: Registry Value: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server Compact Edition\v3.5\ENU\DesktopRuntimeServicePackLevel = 1
• Download Location: http://download.microsoft.com/download/ ... NU-x86.msi

Return to “Common Problems”