Wix Setup - Addin installs but does not show anywhere in Outlook

Add-in Express™ Support Service
That's what is more important than anything else

Wix Setup - Addin installs but does not show anywhere in Outlook
 
Carlos Gonzalez




Posts: 25
Joined: 2009-12-22
I thought that by buying the VDProj to WiX converter I would not have to do coding. That's what was advertised on your site.
If I have to start from scratch and create a new WiX project then what was the purpose of the converter? I am confused.

The documentation in the Add-In Express shows the following entries should exist in the Product.wxs. It shows the MSO.2005 dll:

<Fragment>
<ComponentGroup Id="ProductComponents" >
213
Add-in Express™
www.add-in-express.com
Add-in Express for Office and .net Creating MSI Installers
<Component Id="ProductComponent" Guid="15eb145d-2f8a-4ea4-a0be-6e81c14db478"
DiskId="1" Directory="INSTALLFOLDER" >
<RegistryKey Root="HKCU" Key="Software\[Manufacturer]\[ProductName]">
<RegistryValue Type="string" Name="Installed" Value="[INSTALLFOLDER]"
KeyPath="yes" />
</RegistryKey>
<File Id="_$(var.MyAddin1.TargetName)_dll"
Name="$(var.MyAddin1.TargetFileName)" Source="$(var.MyAddin1.TargetPath)" />
<File Id="_adxloader_dll_manifest" Name="adxloader.dll.manifest"
Source="$(var.MyAddin1.ProjectDir)Loader\" />
<File Id="_adxloader_dll" Name="adxloader.dll"
Source="$(var.MyAddin1.ProjectDir)Loader\" />
<File Id="_adxloader64_dll" Name="adxloader64.dll"
Source="$(var.MyAddin1.ProjectDir)Loader\" />
<File Id="_AddinExpress_MSO_2005_dll" Name="AddinExpress.MSO.2005.dll"
Source="C:\Program Files (x86)\Add-in Express\Add-in Express for .NET\Bin\" />
<File Id="_Interop_Excel_dll" Name="Interop.Excel.dll"
Source="$(var.MyAddin1.TargetDir)" />
<File Id="_Interop_PowerPoint_dll" Name="Interop.PowerPoint.dll"
Source="$(var.MyAddin1.TargetDir)" />
<File Id="_Interop_Word_dll" Name="Interop.Word.dll"
Source="$(var.MyAddin1.TargetDir)" />
<File Id="_Interop_Office_dll" Name="Interop.Office.dll"
Source="$(var.MyAddin1.TargetDir)" />
<File Id="_Interop_VBIDE_dll" Name="Interop.VBIDE.dll"
Source="$(var.MyAddin1.TargetDir)" />
</Component>
</ComponentGroup>
</Fragment>

But the ones that the converter produced look different and don't show the MSO.2005 dll:

<Directory Id='TARGETDIR' Name='SourceDir'>
<Directory Id='DesktopFolder' Name='Desktop' />
<Directory Id='ProgramMenuFolder' Name='Program Menu' />
<Component Id='com_00245906_D73B_BC49_8643_64CB30199C11' Guid='2D2D4402-4C1F-4541-9F69-3715BBBA3C9E' Permanent='no' SharedDllRefCount='no' Transitive='no'>
<File Id='_00245906_D73B_BC49_8643_64CB30199C11' DiskId='1' Hidden='no' ReadOnly='no' System='no' Vital='yes' Compressed='yes' Name='adxloader64.dll' Source='..\..\Loader\adxloader64.dll' KeyPath='yes' />
</Component>
<Component Id='com_0BBBC40A_042D_E348_A2CF_7CCB287D6D0E' Guid='F628569B-FC38-4B55-B39E-23157629790C' Permanent='no' SharedDllRefCount='no' Transitive='no'>
<File Id='_0BBBC40A_042D_E348_A2CF_7CCB287D6D0E' DiskId='1' Hidden='no' ReadOnly='no' System='no' Vital='yes' Compressed='yes' Name='adxregistrator.exe' Source='C:\Program Files (x86)\Add-in Express\Add-in Express for .NET\Redistributables\adxregistrator.exe' KeyPath='yes' />
</Component>
<Component Id='com_0FAB97E3_6615_3D41_ADC5_A146A4D5F04A' Guid='8E883114-D8E1-498F-B4BC-779EFD63E508' Permanent='no' SharedDllRefCount='no' Transitive='no'>
<File Id='_0FAB97E3_6615_3D41_ADC5_A146A4D5F04A' DiskId='1' Hidden='no' ReadOnly='no' System='no' Vital='yes' Compressed='yes' Name='app.config' Source='..\..\app.config' KeyPath='yes' />
</Component>
<Component Id='com_A403A18E_325B_E240_B46A_6F57B0813E32' Guid='8B1465B4-0340-46BA-8B63-D7E2EF4C065D' Permanent='no' SharedDllRefCount='no' Transitive='no'>
<File Id='_A403A18E_325B_E240_B46A_6F57B0813E32' DiskId='1' Hidden='no' ReadOnly='no' System='no' Vital='yes' Compressed='yes' Name='adxloader.dll.manifest' Source='..\..\Loader\adxloader.dll.manifest' KeyPath='yes' />
</Component>
<Component Id='com_DAAC69E3_432B_214E_BB45_6611DF57C948' Guid='6F5AC22C-3205-4BD3-8C66-F694C8CC648A' Permanent='no' SharedDllRefCount='no' Transitive='no'>
<File Id='_DAAC69E3_432B_214E_BB45_6611DF57C948' DiskId='1' Hidden='no' ReadOnly='no' System='no' Vital='yes' Compressed='yes' Name='adxloader.dll' Source='..\..\Loader\adxloader.dll' KeyPath='yes' />
</Component>
<Component Id='com_FDCFEDA2_A79F_2646_BDC9_21BDCFF63561' Guid='44A10FFA-AE55-4497-AE39-00E3094A94BB' Permanent='no' SharedDllRefCount='no' Transitive='no'>
<File Id='_FDCFEDA2_A79F_2646_BDC9_21BDCFF63561' DiskId='1' Hidden='no' ReadOnly='no' System='no' Vital='yes' Compressed='yes' Name='ICCOOutlookAddIn.dll' Source='..\..\bin\Obfuscated\ICCOOutlookAddIn.dll' KeyPath='yes' />
</Component>
</Directory>

Should I stick with the format that the converter produced? Is there a new version of the converter that fixes this issue and maybe I just need to re-convert using the new version? My version is 1.4.129.0 dated 1/29/2014.

Let me know how to proceed.
Posted 20 Feb, 2014 16:34:30 Top
Andrei Smolin


Add-in Express team


Posts: 14106
Joined: 2006-05-11
Carlos,

The following scenarios are possible:
1) there's a bug in the Converter
2) there's a problem in your original setup project

If we assume that version 1 is correct, then we need to have a reproducible case. Say, you can create a new empty (no code) add-in project, create a regular setup project for it and convert the setup project. The two setup projects should deliver the same set of files to the target machine and perform the same registration actions.

As to version 2, could you please confirm that your original setup project works correctly? Does it deliver that file to the target machine?

You can install the last converter version, see http://www.add-in-express.com/downloads/vdproj-wix-converter.php. Nevertheless, it doesn't contain a "fix" for the issue. I strongly suggest that you start with checking if your original project delivers that file.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 21 Feb, 2014 05:58:47 Top
Carlos Gonzalez




Posts: 25
Joined: 2009-12-22
The old version (before the vdproj to WiX conversion) still works fine and yes, it delivers the AddInExpress.*.2005.dlls, the adxloader dlls and the adregistrator.exe together with all the other files.

I can email you the old project so you can troubleshoot why the converter did not work.

Let me know how to move forward on this.

Thanks
Posted 24 Feb, 2014 09:42:14 Top
Andrei Smolin


Add-in Express team


Posts: 14106
Joined: 2006-05-11
Carlos,

You can find the support email address in {Add-in Express installation folder}\readme.txt. Please make sure your email contains a link to this topic.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 24 Feb, 2014 09:47:40 Top
Carlos Gonzalez




Posts: 25
Joined: 2009-12-22
I think I found out what the problem is:

When I did my conversion I upgraded the solution to Visual Studio 2013 first, then converted using the vbproj to wix converter. This resulted in a product.wxs that is missing a bunch of stuff.

If I convert to wix while on Visual Studio 2010, I get a lot more data on the Product.wxs file. All my DLLs show there. Then I can upgrade to Visual Studio 2013.

So the problem seems to be with the wix converter on Visual Studio 2013.
Posted 24 Feb, 2014 10:29:25 Top
Carlos Gonzalez




Posts: 25
Joined: 2009-12-22
I celebrated too soon:

If I try running the converted WiX project on Visual Studio 2010, I get the following errors:

Error 7 The file 'C:\Program Files (x86)\Add-in Express\Add-in Express for .NET\Bin\AddinExpress.MSO.2005.tlb' cannot be found. heat.exe 0 1 ICCOOutlookAddInSetup_wix
Error 8 The command ""C:\Program Files (x86)\WiX Toolset v3.8\Bin\heat.exe" file "C:\Program Files (x86)\Add-in Express\Add-in Express for .NET\Bin\AddinExpress.MSO.2005.tlb" -sw -gg -sfrag -nologo -srd -out "obj\\Release\Harvested XML\_AddinExpress.MSO.2005.com.xml"" exited with code 5059. C:\Temp\ICCO Outlook AddIn\ICCOOutlookAddIn\ICCOOutlookAddInSetup\8.0.475\ICCOOutlookAddInSetup_wix.wixproj 86 6 ICCOOutlookAddInSetup_wix

I don't see the tlb file on the bin folder, only DLLs.
Posted 24 Feb, 2014 10:49:19 Top
Sergey Grischenko


Add-in Express team


Posts: 7187
Joined: 2004-07-05
Hi Carlos,

Please open .vdproj in Visual Studio 2010 and exclude all .tlb files in the Detected Dependencies section of the setup. Then re-convert the project again.
Posted 24 Feb, 2014 11:39:31 Top
Carlos Gonzalez




Posts: 25
Joined: 2009-12-22
Yes. That did it.

So to recap for anyone that might experience the same problem, the vdproj to .net conversion procedure is:
Before upgrading to VS2013, exclude the tlbs from the vdproj, then run the converter from VS2010 and create the wix setup project.
Then upgrade the solution to VS2013, remove the incompatible vdproj project, and rebuild the solution and voila, you get your application installation files, including the setup.exe which I was missing before.

Upgrading first to VS2013 messed everything up and made me lose many hours.

Thank you for your help.
Posted 26 Feb, 2014 11:19:23 Top
Andrei Smolin


Add-in Express team


Posts: 14106
Joined: 2006-05-11
Many thanks, Carlos!

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 27 Feb, 2014 05:07:16 Top