Hello Community
Years ago I wrote an AddIn for Visio2003 with some stencils, a template and functions in a vsl file. I used the SDK publish tool to create a proper MSI file.
Right now my customer wants to update to Visio 2013 and I can't figure out why my installer is not working anymore. Unfortunately I decided (10 years ago) to use Delphi 5 to create the vsl (DLL) file and MakeMSI for the installer. So I am not using much of the Microsoft tool chain.
Now my problem is, that VSL file is not showing up in AddOns after installation. The VSL itself is actually working because when I add the install folder to the ADD-Ons path I see all my functions and they are working.
(http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=18029bfe-2115-492d-8ab2-d03e941dc7d5)
I checked the PublishedComponent table and played around with LCID, VisioVersion and Edition in the Visio 2013 Solution Publishing Tool – but without success.
(http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=2a139750-d108-412f-ab5f-2b12acfb62b8)
(http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=c81f59bc-4868-48c2-9765-94701e327259)
Also the Registry entries seem to be all right because the stencils and the template are correctly installed. The SDK VSLs show up in the same registry entry...
(http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=1d3ae81b-e332-42be-9f04-0addd0cdddc0)
The MSI file is not working with Win7 nor with Win8 - I tried it on two computers.
Hope someone can give me a hint what I can try next.
Thank you in advance
Cheers
Sebastian
P.S. I already asked the question on the microsoft community (http://answers.microsoft.com/en-us/office/forum/office_2013_release-visio/vsl-addin-with-msi-installer-does-not-work-with/323a0433-2083-43ca-a35c-a56042807404) without success.
Is the vsl digitally signed, or are Visio's security settings set to allow non-signed addons?
Could you possibly put your installer (MSI) file here so that we could try it?
I mean, I have messed a while ago with this publishing stuff..
Ended up creating a extension to build MSI from VisualStudio using WiX (does not depend on the publishing tool):
https://visualstudiogallery.msdn.microsoft.com/68d12e2d-eb42-4847-808a-7d80863bb90d
Hello Paul,
The vsl is not signed and all security features in Trust Center\Add-Ins are unchecked. The VSL is running if I add the vsl folder as Add-Ons folder. But the vsl is not running if I use my msi installer...
Cheers
Seb
I've taken a look at the MSI.
1. The main issue seems to be that you don't have VSL as "Key file" for your component.
Just put it as first file in your file list (so that it is "Key file" to the component), and everything should work.
See the screenshot in the attachment (screenshot from ORCA).
2. The Solution publishing tool seems to mess stuff a bit with your setup...
To allow ALL languages for Visio 2013 (and not only German 1031), you could try setting Language=1
That is, in the MSI in the Qualifer column you should get "1\xx\Rackdesign.vsl".
Note that this does not seem work for all versions (in particular, 2003); only 2007 and above.
3. Come on, move to WiX already :) MAKEMSI sucks :)
Please also mind the PM.
Hey Nicolay,
Thank you very much – it's working. Unfortunately I will not change to WiX because of your help ;).
Thank you very much again!
If you are in Dresden (Germany) for the next time I owe you a beer!
Cheers
Sebastian
Ein lecker Radeberger?
Oder zwei (http://rsdn.ru/Forum/Images/beer.gif)