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
Chuck
FOLLOW US
Get the latest news in Application Packaging