x64 and x86 installer issue

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

x64 and x86 installer issue
creating one installer for x64 OS + x86/x64Outlook; and x86OS + x86Outlook 
Samir Gulrajani


Guest


I have one Outlook plugin created using Add-in Express; the project is set to taget "Any CPU"
The installer project's Property Page >> Configuration Manager is set to "Any CPU".

The installer works perfectly on x64 OS + x64 Outlook; and x64 OS + x86 Office. But not on x86 OS + x86 Office.

The installer, runs without any errors on our client's computer without any exceptions. However, it does not put the addin in Outlook. The addin does not even show in the AddIns listing as disabled. At this point of time, the "adxloader.log" is not created in the MyDocuments folder.

So, when we go to manually add it, nothing happens. But it does create that "adxloader.log" file. Contents below: 

Add-in Express Registrator Log File: 03/01/2013 09:03:06

Installation directory: C:UsersBidtracerMBAppDataRoamingBidTacher
Registrator version: 7.1.4050.1
Operating System: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 32-bit
Process Owner: Administrator
Command Line: "C:UsersBidtracerMBAppDataRoamingBidTacherdxregistrator.exe" /install="BidTacher.dll" /privileges=admin
Run 'As Administrator': No
Process Elevated: No
Integrity Level: Medium
UAC (User Account Control): On
--------------------------------------------------------------
09:03:06 0160 Starting the add-in registration process.
09:03:06 0160 Loading mscoree.dll
09:03:06 0160 Success.
09:03:06 0160 .NET Framework installation directory: 
09:03:06 0160 The latest version of .NET Framework: 'v4.0.30319'
09:03:06 0160 Loading CLR: v4.0.30319.
09:03:06 0160 Calling CLRCreateInstance method.
09:03:06 0160 Success.
09:03:06 0160 Calling GetRuntime method.
09:03:06 0160 Success.
09:03:06 0160 Checking if the hosting API of .NET Framework v4.0 beta is installed.
09:03:06 0160 The hosting API is up to date.
09:03:06 0160 Calling GetInterface method for the CorRuntimeHost interface.
09:03:06 0160 Success.
09:03:06 0160 Starting CLR...
09:03:06 0160 Success.
09:03:06 0160 Getting the CLR version.
09:03:06 0160 The CLR v4.0.30319 has been initialized successfully.
09:03:06 0160 Creating a new domain setup.
09:03:06 0160 Success.
09:03:06 0160 Getting the add-in directory.
09:03:06 0160 Success. The directory is 'C:UsersBidtracerMBAppDataRoamingBidTacher'
09:03:06 0160 The 'shadow copy' is disabled.
09:03:06 0160 Creating a new application domain.
09:03:06 0160 Success.
09:03:06 0160 Getting the base directory for the domain.
09:03:06 0160 Success. The directory is 'C:UsersBidtracerMBAppDataRoamingBidTacher'.
09:03:06 0160 Searching for the Add-in Express core library.
09:03:06 0160 Success. The 'AddinExpress.MSO.2005.dll' file is found.
09:03:06 0160 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
09:03:06 0160 Assembly identity is 'AddinExpress.MSO.2005'.
09:03:06 0160 Success.
09:03:06 0160 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
09:03:06 0160 Success.
09:03:06 0160 Calling the managed registration procedure.
09:03:06 0564 Connecting to the application domain of the Add-in Express loader.
09:03:06 0564 Success.
09:03:06 0564 Loading the 'bidtacher.dll' assembly.
09:03:06 0564 Success.
09:03:06 0564 Registering the 'bidtacher.dll' assembly (administrator).
09:03:07 0564 The ' bidtacher.dll' assembly has been registered successfully.
09:03:07 0160 Success.
09:03:07 0160 The add-in registration process is completed with HRESULT = 0.




Add-in Express Loader Log File: 03/01/2013 09:06:04:014

Startup directory: C:UsersBidtracerMBAppDataRoamingBidTacher
Loader version: 7.1.4050.0
Operating System: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 32-bit
Process Owner: Administrator
Command Line: "C:Program FilesMicrosoft OfficeOffice12OUTLOOK.EXE" 
Run 'As Administrator': No
Process Elevated: No
Integrity Level: Medium
UAC (User Account Control): On
------------------------------------------------------------------------
09:06:04:015 15376 7892 Starting the add-in registration process.
09:06:04:016 15376 7892 Loading mscoree.dll
09:06:04:016 15376 7892 Getting the latest CLR version.
09:06:04:016 15376 7892 The latest CLR version is 'v4.0.30319'.
09:06:04:016 15376 7892 Loading CLR: v4.0.30319.
09:06:04:016 15376 7892 Calling CLRCreateInstance method.
09:06:04:016 15376 7892 Success.
09:06:04:017 15376 7892 Calling GetRuntime method.
09:06:04:017 15376 7892 Success.
09:06:04:017 15376 7892 Checking if the hosting API of .NET Framework v4.0 beta is installed.
09:06:04:022 15376 7892 The hosting API is up to date.
09:06:04:022 15376 7892 Calling GetInterface method for the CorRuntimeHost interface.
09:06:04:022 15376 7892 Success.
09:06:04:022 15376 7892 Starting CLR...
09:06:04:041 15376 7892 Success.
09:06:04:041 15376 7892 Getting the CLR version.
09:06:04:041 15376 7892 The CLR v4.0.30319 has been initialized successfully.
09:06:04:041 15376 7892 Creating a new domain setup.
09:06:04:044 15376 7892 Success.
09:06:04:044 15376 7892 Getting the add-in directory.
09:06:04:044 15376 7892 Success. The directory is 'C:UsersBidtracerMBAppDataRoamingBidTacher'
09:06:04:044 15376 7892 The 'shadow copy' is disabled.
09:06:04:044 15376 7892 Creating a new application domain.
09:06:04:059 15376 7892 Success.
09:06:04:059 15376 7892 Getting the base directory for the domain.
09:06:04:059 15376 7892 Success. The directory is 'C:UsersBidtracerMBAppDataRoamingBidTacher'.
09:06:04:059 15376 7892 Searching for the Add-in Express core library.
09:06:04:059 15376 7892 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
09:06:04:060 15376 7892 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
09:06:04:060 15376 7892 Assembly identity is 'AddinExpress.MSO.2005'.
09:06:04:079 15376 7892 Success.
09:06:04:079 15376 7892 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
09:06:04:082 15376 7892 Success.
09:06:04:082 15376 7892 Creating an instance of the XML parser class.
09:06:04:082 15376 7892 Success.
09:06:04:082 15376 7892 Loading the manifest file (C:UsersBidtracerMBAppDataRoamingBidTacherdxloader.dll.manifest).
09:06:04:082 15376 7892 Success.
09:06:04:082 15376 7892 Getting the root element of the manifest (C:UsersBidtracerMBAppDataRoamingBidTacherdxloader.dll.manifest).
09:06:04:082 15376 7892 Success.
09:06:04:082 15376 7892 Getting the 'assemblyIdentity' element of the manifest (C:UsersBidtracerMBAppDataRoamingBidTacherdxloader.dll.manifest).
09:06:04:082 15376 7892 Success.
09:06:04:082 15376 7892 Searching for the 'name' attribute of the 'assemblyIdentity' element.
09:06:04:082 15376 7892 Success. The name is 'BidTacher, PublicKeyToken=02f9309ae0dcb7c6'.
09:06:04:082 15376 7892 Calling the managed procedure to register the 'BidTacher, PublicKeyToken=02f9309ae0dcb7c6' assembly.
09:06:04 15508 7892 Connecting to the application domain of the Add-in Express loader.
09:06:04 15508 7892 Success.
09:06:04 15508 7892 Loading the 'BidTacher, PublicKeyToken=02f9309ae0dcb7c6' assembly.
09:06:04 15508 7892 Success.
09:06:04 15508 7892 Registering the 'BidTacher, PublicKeyToken=02f9309ae0dcb7c6' assembly (administrator).
09:06:04 15508 7892 The ' BidTacher, PublicKeyToken=02f9309ae0dcb7c6' assembly has been registered successfully.
09:06:04 15508 7892 The managed registration process is complete with HRESULT = 0.
09:06:04:502 15376 7892 The add-in registration process is completed with HRESULT = 0.
Posted 01 Mar, 2013 12:53:03 Top
Andrei Smolin


Add-in Express team


Posts: 18825
 Joined: 2006-05-11
Hello Samir,

Thank you for posting the log files. In the registrator's log I see this line:


Command Line: "C:\Users\BidtracerMB\AppData\Roaming\BidTacher\adxregistrator.exe" /install="BidTacher.dll" /privileges=admin


That is, you install your add-in to the user's profile but you register the add-in as per-machine.

Please check the section Determining Privileges in the manual, see {Add-in Express}\Docs\adxnet.pdf on your PC. Please let me know if fixing this solves the problem.


Andrei Smolin
Add-in Express Team Leader
Posted 04 Mar, 2013 03:07:00 Top
Samir Gulrajani


Guest


Thank you, that was it. I changed the AddinModule's RegisterForAllUsers to False; and updated the installer project's adxregistrator to "privileges=user". And it all works fine now.
Posted 04 Mar, 2013 13:18:16 Top