Comparing Installer Results - 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

Comparing Installer Results

I am trying to migrate an installer from VS2008 to AI and I'm trying to compare the results of the two installers to understand why the AI installation isn't completely working. The problem is this - my solution is a Visio Add-in that must work in Vista and Windows 7 and with Visio 2003, 2007, and 2010. Visio is very protective about what add-ins it will allow to load. In order for Visio to allow the Add-in to load, (1) it must be properly registered for COM and (2) it must be granted full trust with a code access security policy that I create with an installer custom action.

I have a VS2008 installer that is working fine - I've migrated that installer from VS2008 to AI and it's not working - the AI installer is completing the installation successfully but Visio is not allowing the Add-in to start. Unfortunately, the VSTO loader is not very descriptive about error conditions - it simply says that there was an error condition in attempting to launch the Add-in and it did not load - there could be a number of reasons behind that, but from past experience, the problem usually falls into one of the two areas I mentioned above: (1) a code access security issue that the code wasn't granted full trust or (2) a COM registration issue.

I'm trying to validate that the AI installer is doing the same thing as the VS2008 installer that I know works and find the difference that is causing the problem. I've been looking around to see if there is a tool that will allow me to do that easily - there are some tools that help, but unfortunately, they're not that easy to use. Here's a summary of what I've done so far:
  • I've created a Virtual PC configuration that I can use as a baseline to compare both installations (VS and AI) - I pre-installed all the prerequisites into the baseline configuration because I'm sure the problem I'm having isn't in the prerequisites and it simplifies the analysis considerably to remove the pre-requisites because some of them are substantial
  • I'm using a tool called "SystemSherock" to create a before and after dump of the system registry and the C Drive for each installer and to compare the results. For both the VS and AI installers, I can use this tool to create a dump of the complete registry and CDrive and compare the results to see exactly what has been changed by each installer.
  • The output of that is four text files (one for VS and one for AI) showing what has been changed in the CDrive and in the registry. I'm using a tool called "ExamDiff" to compare the those files to look for differences
This approach is fairly time-consuming because there are a huge number of changes to the system that need to be compared even after I've eliminated all the prerequisites. Theoretically, the results produced by both installers on the target system should be exactly the same, but they're not. I'm going to post the results I found in a separate reply to this thread.

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

Re: Comparing Installer Results

Here is a summary of the differences I've found between the VS2008 installer and the AI installer that might be significant (there are many more that I didn't list here that I excluded):
  • The AI installer is creating a registry key for the installation in HKEY_CLASSES_ROOT\Installer\Assemblies. The VS installer is creating an equivalent set of keys in HKEY_CURRENT_USER\Software\Microsoft\Installer
  • The VS Installer is creating a number of registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem - I don't see any equivalent to that from the AI installer
  • The VS Installer is creating some registry keys in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 - I don't see any equivalent to that from the AI installer
  • The AI installer is creating a number of registry keys in HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam - The VS Installer seems to be deleting a number of keys in that area and I don't see any equivalent additions
  • The AI Installer is creating some registry keys in CRE HKEY_LOCAL_MACHINE\SOFTWARE\Caphyon - this is probably not significant
  • The AI Installer is creating a number of registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Assemblies - The VS Installer seems to be creating equivalent keys in HKEY_CURRENT_USER\Software\Microsoft\Installer
There's a huge amount of information in here and it's like looking for a needle in a haystack - if anyone has any suggestions for an easier method, I would appreciate it. There's a lot of "noise" in this data and I'm sure a lot of the differences are not significant. There are two things in the above results that may be significant:
  • The VS Installer seems to be doing the installation for the current user while the AI installer seems to be doing it for "All Users" - I don't know how to change this in the AI Installer configuration - I have the AI Installer configuration set for "Per User Only"
  • The VS Installer is creating a number of keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem - those keys seem to be missing from the AI installer - I'm not sure what is generating those keys
Any suggestions would be appreciated...

Thanks,

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

Re: Comparing Installer Results

I think I've found the problem...there was a file missing from the AI installer. The file was ProcessMaps.dll.manifest (ProcessMaps is the name of my Visio Add-in). This file was apparently added automatically by the VS2008 installer when I selected add "Project Output", but I had to manually add it to the AI installer. I don't think this file is needed for COM registration, but the VSTO loader needs it.

I still have an outstanding question about how to configure the "All Users" setting in the AI Installer.

I've sent the files I used for this analysis to Bogdan. It might be worthwhile for the AI Team to look into tools for doing this kind of analysis. It is a very cumbersome and time-consuming process to compare the results of two different installers on the target system, but it can be a good trouble-shooting approach if the tools made it easier to do.

Thanks,

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

Re: Comparing Installer Results

Hi,

Advanced Installer is resolving correctly the value of the property ALLUSERS, according to Microsoft standards.

The problem was in the .aip file, the property value was corrupted along the installation process.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”