Adding "|vstolocal" parameter causes Runtime error. - Advanced Installer Community
jfoxcroft
Posts: 3
Joined: Wed Feb 28, 2018 7:12 pm

Adding "|vstolocal" parameter causes Runtime error.

I am having the identical root issue that the original poster had presented on the forums here:

viewtopic.php?t=20441

Essentially, not having the |vstolocal parameter appended to the Manifest registry value invokes the VSTO installer and causes two instances of the add-in to show up... adding the parameter back, however, causes the locally installed add-in to stop functioning and throw a runtime error when I attempt to enable it.

Image

If I remove the |vstolocal parameter again, when restarting Outlook, I again have two instances of the add-in loading and functioning correctly. The first time I ran through this I double-checked the .AIP but then I decided to rebuild it via the wizard and not touch anything besides loading up my files that need to be dropped into Files and Folders. That being said, if the way I built out the .AIP or the compiled MSI had an issue, the add-in would not load even after removing the |vstolocal parameter but it does. Something about that |vstolocal parameter is creating an issue with the add-in loading correctly.

I am building this to run on Windows 10 1703 in both Outlook 2013 and 2016; I have done two separate builds targeted to both flavors and the issue occurs on both. I would really like this to be installed under the LOCAL MACHINE context for All Users because this is an add-in that our organization would like all users to have when they receive their device... I had planned on adding this to our task sequence so this just gets dropped in during OSD but I can't do that if it has to be installed in the Current User context.

This was one of the features we were excited about this product for, any assistance on this is highly appreciated! Thanks!
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Adding "|vstolocal" parameter causes Runtime error.

Hello and welcome to our forums,

We will need to further investigate this on our side. Could you please send us by email to support at advancedinstaller dot com the following resources:

1. the .AIP (project file)
2. if possible, a download link of its built setup package so we can fully test and investigate it on our side

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jfoxcroft
Posts: 3
Joined: Wed Feb 28, 2018 7:12 pm

Re: Adding "|vstolocal" parameter causes Runtime error.

Email has been sent with download link for requested files.

Thank you!
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Adding "|vstolocal" parameter causes Runtime error.

Hello,

Thank you for your sent files. I've checked your project settings and your add-in installation project is configured correctly. The "Manifest" registry value is correctly set (i.e. with "|vstolocal" string appended).

After testing and installing your setup package I replicated the same load error. Most likely this happens because it seems to me that you used the ClickOnce published installation resources (i.e. .deploy files) instead of using the DLL and config files of your add-in application. Please note that when running our add-in wizard you should select to import the output of your application add-in project of your Visual Studio solution and not the output of the ClickOnce project publish operation.

Can you please proceed like this:

1. create a new "Office Add-In" project type
2. during the project wizard use the "Import the files from a Visual Studio Project" option and pick your office addin SLN (solution) file
3. run through the office wizard and finish it

Also, make sure that the created project will either check to make sure all of your office add-in dependencies (.Net Framework version, third party DLLs if any required) are already installed on target system or will deploy them during the installation process too.

Let us know if this helped.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jfoxcroft
Posts: 3
Joined: Wed Feb 28, 2018 7:12 pm

Re: Adding "|vstolocal" parameter causes Runtime error.

This worked, Daniel, thank you! Our .NET developer put this together and is obsessed with the ClickOnce stuff; he came to me with the guts and asked me to get it to a state in which it could be deployed but only gave me the ClickOnce resources. I went back, got the core dependency files and it is working as desired now.

Most excellent and thank you again! This is the first issue I have encountered with Advanced Installer (and I suppose wasn't really an issue at all) and loving the product so far. :D
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Adding "|vstolocal" parameter causes Runtime error.

You are always welcome.

I'm glad you got this working.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”