adxloader.dll / adxloader.dll.manifest not taken into consideration .MSI installed version

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

adxloader.dll / adxloader.dll.manifest not taken into consideration .MSI installed version
 
Pawel Forys




Posts: 17
Joined: 2016-04-27
Hi,
In the development environment, when I run my Outlook add-in in debug mode from Visual Studio 2015, everything works fine and I am able to use my custom app settings from app.config. Following the instructions: https://www.add-in-express.com/docs/net-msi-setup-project.php, I have manually created the setup project and as outcome - the .msi package. Installation went correct and my add-in is starting with Outlook, however the custom app settings are not present.

After long investigation and following many topic from this forum I have concluded that there is no problem with the .manifest content file and reference to the .config file but in general with loading of the manifest. As a proof, I removed the adxloader.dll and adxloader.dll.manifest from the list of files to be installed via .msi. This didn't block the plugin from running in my Outlook and obviously the symptom were the same - no config values. So it seems like for my plugin, it doesn't make any difference if those files are in the application folder after installation or not. Is there other default adxloader.dll, that add-in may use?

Thanks and best regards
Pawel Forys
Posted 27 Apr, 2016 07:27:21 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
Joined: 2004-07-05
Hi Pawel,

I think that the .config file is not installed by the setup program. Please check if you added the .config file to the setup project.
Posted 27 Apr, 2016 10:01:23 Top
Pawel Forys




Posts: 17
Joined: 2016-04-27
Hi Sergey,
You are right, it doesn't add it to the project automatically. I did that manually and referenced the file name in the .manifest file. I have also tried with different naming conventions like App.config, Project.dll.config or Project.config.
My manifest looks as follows:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <assemblyIdentity name="Office.Apps.Addin, PublicKeyToken=5ecf78d4caff8e6e" imageRuntimeVersion="v4.0.30319" />
  <loaderSettings generateLogFile="true" shadowCopyEnabled="false" privileges="user"  configFileName="App.config" />
</configuration> 


The list of files in the installation folder:


22.03.2016  18:51         4'044'664 AddinExpress.MSO.2005.dll
01.04.2016  21:41           609'280 adxloader.dll
27.04.2016  17:17               326 adxloader.dll.manifest
01.04.2016  21:41           717'312 adxloader64.dll
19.01.2016  19:51           165'752 adxregistrator.exe
19.04.2016  13:11               760 App.config
05.04.2016  16:58           203'264 Autofac.dll
07.04.2016  16:35            20'992 Autofac.Extras.DynamicProxy2.dll
18.04.2016  11:03           273'408 AutoMapper.dll
07.04.2016  16:35           435'712 Castle.Core.dll
05.04.2016  11:29           940'544 MahApps.Metro.dll
30.03.2016  18:03            43'824 Microsoft.Exchange.WebServices.Au
30.03.2016  18:03         1'130'264 Microsoft.Exchange.WebServices.dl
03.02.2010  01:03         1'103'256 Microsoft.IdentityModel.dll
31.08.2012  00:20            59'664 Microsoft.IdentityModel.Extension
15.04.2016  11:24           981'696 Microsoft.Office.Interop.Outlook.
15.04.2016  11:24            64'168 Microsoft.Vbe.Interop.dll
30.03.2016  18:02           520'192 Newtonsoft.Json.dll
27.04.2016  17:17            55'296 Office.Apps.Addin.dll
15.04.2016  11:24           466'640 Office.dll
05.10.2013  03:38            32'408 stdole.dll
30.03.2016  18:02           471'240 System.Web.Http.dll
05.04.2016  11:29            55'904 System.Windows.Interactivity.dll


As I mentioned, the add-in is always working after installation, event when I don't include adxloader.dll and adxloader.dll.manifest. However app settings are never picked up.
Posted 27 Apr, 2016 10:39:32 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
Joined: 2004-07-05
Hi Pawel,

The name of the config file should be <The name of the project assembly>.dll.config, e.g. MyAddin1.dll.config.
Let me know if the issue still exists.
Posted 28 Apr, 2016 04:37:00 Top
Pawel Forys




Posts: 17
Joined: 2016-04-27
Hi Sergey,
Unfortunatelly not. I changed the config file name also I tried changing the the filename along with reference in manifest file, but it still seems like .manifest is not being taken into consideration at all.
Posted 29 Apr, 2016 03:45:31 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
Joined: 2004-07-05
Hi Pawel,

Can you please send me a sample project that reproduces the issue? I just can't reproduce it on my PC.
Posted 29 Apr, 2016 08:35:18 Top
Pawel Forys




Posts: 17
Joined: 2016-04-27
Hi Sergey,
I have uploaded the sample project to your support form. Thanks in advance for analysis.
Posted 02 May, 2016 09:11:05 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
Joined: 2004-07-05
Hi Pawel,

Thank you.
The add-in will work properly if you set the 'Register' property of the 'Primary output from OutlookAddin (Active)' to 'vsdrpDoNotRegister' in the FileSystem editor of the setup project (it is 'vsdrpCOM' in your setup now). I checked it out. The config file is picked up by the add-in.
Posted 03 May, 2016 03:47:43 Top
Pawel Forys




Posts: 17
Joined: 2016-04-27
Hi Sergey,
Many thanks for the help! The add-in works as expected now.

Best regards
Posted 03 May, 2016 06:30:50 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
Joined: 2004-07-05
Hi Pawel,

You are welcome!
Posted 03 May, 2016 07:38:48 Top