Installation Program Problems

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

Installation Program Problems
Creating setup.exe fails after changing to VS2005 
Fred Balkenende




Posts: 29
 Joined: 2007-07-05
Hello

I've converted my project from VS2003 to VS2005, and want to use .NET 2.0 now. So I've replaced AddinExpress.MSO.dll with AddinExpress.MSO.2005.dll.
Everything compiles as it should.

When trying to make an installationprogram using InstallShield I get the following warning:
"ISEXP : warning -6248: Could not find dependent file xlcall32.dll, or one of its dependencies of component AddinExpress.MSO.2005.dll"

When running the installation a window pops up: "../adxloader could not be registered. HRESULT -2147220473..."

The adxloader logfile contains the following:
Add-in Express Loader Log File: 09/09/2008 15:22:11

Startup directory: Loader version: 4.3.1910 C:\Programmer\Office Reports\OfficeAddin\
------------------
15:22:11 444 Starting the add-in registration process.
15:22:11 444 Loading the latest CLR version.
15:22:11 444 The CLR v2.0.50727 has been initialized successfully.
15:22:11 444 Creating a new domain setup.
15:22:11 444 Success.
15:22:11 444 Getting the add-in directory.
15:22:11 444 Success. The directory is 'C:\Programmer\Office Reports\OfficeAddin\'
15:22:11 444 The configuration file is '(null)'
15:22:11 444 The 'shadow copy' is disabled.
15:22:11 444 Creating a new application domain.
15:22:11 444 Success.
15:22:11 444 Getting the base directory for the domain.
15:22:11 444 Success. The directory is 'C:\Programmer\Office Reports\OfficeAddin\'.
15:22:11 444 Seaching for the Add-in Express core library.
15:22:11 444 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
15:22:11 444 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
15:22:11 444 Assembly identity is 'AddinExpress.MSO.2005'.
15:22:11 444 Success.
15:22:11 444 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
15:22:11 444 Success.
15:22:11 444 Test 'C:\Programmer\Office Reports\OfficeAddin\adxloader.dll.manifest'.
15:22:11 444 Test 'C:\Programmer\Office Reports\OfficeAddin\adxloader.dll.manifest'.
15:22:11 444 Creating an instance of the XML parser class.
15:22:11 444 Success.
15:22:11 444 Loading the manifest file (C:\Programmer\Office Reports\OfficeAddin\adxloader.dll.manifest).
15:22:11 444 Success.
15:22:11 444 Getting the root element of the manifest (C:\Programmer\Office Reports\OfficeAddin\adxloader.dll.manifest).
15:22:11 444 Success.
15:22:11 444 Getting the 'assemblyIdentity' element of the manifest (C:\Programmer\Office Reports\OfficeAddin\adxloader.dll.manifest).
15:22:11 444 Success.
15:22:11 444 Seraching fo the 'name' attribute of the 'assemblyIdentity' element.
15:22:11 444 Success. The name is 'ORAddin, PublicKeyToken=b7be42689b0c2660'.
15:22:11 444 Calling the managed procedure to register the 'ORAddin, PublicKeyToken=b7be42689b0c2660' assembly.
15:22:11 1084 Connecting to the application domain of the Add-in Express loader.
15:22:11 1084 Success.
15:22:11 1084 Loading the 'ORAddin, PublicKeyToken=b7be42689b0c2660' assembly.
15:22:11 1084 Error: The Add-in Express Loader can't resolve the 'ORAddin, PublicKeyToken=b7be42689b0c2660' assembly. Please check if the assembly exists in the application directory or in the GAC.
15:22:11 1084 Error: Filen eller assemblyen 'ORAddin, PublicKeyToken=b7be42689b0c2660' eller en af dens afhængigheder kunne ikke indlæses. Den fundne assemblys manifestdefinition svarer ikke til assemblyens reference. (Undtagelse fra HRESULT: 0x80131040)
15:22:11 1084 The managed registration process is complete with HRESULT = 2.
15:22:11 444 The add-in registration process is complete with HRESULT = 2.


I'm working on Windows XP using Office2007.

Whats wrong??

Best Regards
Fred Balkenende
Posted 09 Sep, 2008 10:30:24 Top
Eugene Astafiev


Guest


Hello Fred,

The Add-in Express Loader can't find the ORAddin.dll. Please make sure that the assembly exists in the application directory or in the GAC.
Posted 09 Sep, 2008 13:45:47 Top
Fred Balkenende




Posts: 29
 Joined: 2007-07-05
Hi Eugene

Thanks for your response. The ORAddin.dll assembly exists in the application directory. The problem was that I didn't sign the assembly with a strong name key file. Didn't know you had to do that, and removed it from the project after it told me to use /keyfile on the commandline. Now I've checked "sign the assembly" in the project properties, and it works again.

Thanks for the help anyway!

Best Regards
Fred
Posted 11 Sep, 2008 05:58:00 Top
Eugene Astafiev


Guest


Hi Fred,

Good news!

Thank you for letting me know.
Posted 11 Sep, 2008 06:05:57 Top