|
Kelvin Box
Posts: 77
Joined: 2009-08-30
|
Hi,
I've followed through the guide on how to build and deploy my outlook add-in but the installer keeps failing at the very last moment and the proceeds to uninstall itself.
My add-in references 2 custom dll's both of which are signed, as is my add-in.
The following is the loader log file but I'm not sure what it's telling me. Can anyone suggest how to fix this problem?
Cheers
Kelvin
Add-in Express Loader Log File: 09/22/2009 17:13:20
Startup directory: C:\program files\enabling\noddy\
Loader version: 5.1.2022
------------------
17:13:20 376 3376 Starting the add-in unregistration process.
17:13:20 376 3376 Getting the latest CLR version.
17:13:20 376 3376 The latest CLR version is 'v2.0.50727'.
17:13:20 376 3376 Loading CLR: v2.0.50727.
17:13:20 376 3376 The CLR v2.0.50727 has been initialized successfully.
17:13:20 376 3376 Creating a new domain setup.
17:13:20 376 3376 Success.
17:13:20 376 3376 Getting the add-in directory.
17:13:20 376 3376 Success. The directory is 'C:\program files\enabling\noddy\'
17:13:20 376 3376 The configuration file is 'C:\program files\enabling\noddy\app.config'
17:13:20 376 3376 The 'shadow copy' is disabled.
17:13:20 376 3376 Creating a new application domain.
17:13:20 376 3376 Success.
17:13:20 376 3376 Getting the base directory for the domain.
17:13:20 376 3376 Success. The directory is 'C:\program files\enabling\noddy\'.
17:13:20 376 3376 Searching for the Add-in Express core library.
17:13:20 376 3376 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
17:13:20 376 3376 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
17:13:20 376 3376 Assembly identity is 'AddinExpress.MSO.2005'.
17:13:20 376 3376 Success.
17:13:20 376 3376 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
17:13:20 376 3376 Success.
17:13:20 376 3376 Creating an instance of the XML parser class.
17:13:20 376 3376 Success.
17:13:20 376 3376 Loading the manifest file (C:\program files\enabling\noddy\adxloader.dll.manifest).
17:13:20 376 3376 Success.
17:13:20 376 3376 Getting the root element of the manifest (C:\program files\enabling\noddy\adxloader.dll.manifest).
17:13:20 376 3376 Success.
17:13:20 376 3376 Getting the 'assemblyIdentity' element of the manifest (C:\program files\enabling\noddy\adxloader.dll.manifest).
17:13:20 376 3376 Success.
17:13:20 376 3376 Searching for the 'name' attribute of the 'assemblyIdentity' element.
17:13:20 376 3376 Success. The name is 'DCCTimesheets, PublicKeyToken=a01aad42d513691e'.
17:13:20 376 3376 Calling the managed procedure to unregister the 'DCCTimesheets, PublicKeyToken=a01aad42d513691e' assembly.
17:13:20 1072 Connecting to the application domain of the Add-in Express loader.
17:13:20 1072 Success.
17:13:20 1072 Loading the 'DCCTimesheets, PublicKeyToken=a01aad42d513691e' assembly.
17:13:20 1072 Error: The Add-in Express Loader can't resolve the 'DCCTimesheets, PublicKeyToken=a01aad42d513691e' assembly. Please check if the assembly exists in the application directory or in the GAC.
17:13:20 1072 Error: Could not load file or assembly 'DCCTimesheets, PublicKeyToken=a01aad42d513691e' or one of its dependencies. The system cannot find the file specified.
17:13:20 1072 The managed unregistration process is complete with HRESULT = 2.
17:13:20 376 3376 The system cannot find the file specified. |
|
|
Andrei Smolin
Add-in Express team
Posts: 18828
Joined: 2006-05-11
|
Hello Kelvin,
The log above describes the unregistration process. Note the following line:
17:13:20 1072 Error: Could not load file or assembly 'DCCTimesheets, PublicKeyToken=a01aad42d513691e' or one of its dependencies. The system cannot find the file specified.
It looks like you don't supply all assemblies required for your add-in. Also I suggest that you have the same PublicKeyToken in adxloader.dll.manifest and in your assembly. To find the PublicKeyToken of your assembly, use the following info:
How do I find the PublicKeyToken of my add-in?
You can find it in the setup project, which must be already built. Click on your add-in primary output in the setup project and, in the Properties window, expand the KeyOutput property and see the PublicKeyToken property value.
Anyway, you'll need to remove your add-in from the registry. Try doing this in the COM Add-ins dialog. Please let me know if this works for you.
PS. I'm still working on the code returning the e-mail address of the calendar user.
Andrei Smolin
Add-in Express Team Leader |
|
|
Kelvin Box
Posts: 77
Joined: 2009-08-30
|
I'm not sure what I did differently but I ended up getting it working.
I created a new project with default installer and slowly copied my code in testing the installer as I went and it worked! No idea why but happy anyways!
Looking forward to the email address code for the calendar user :-) |
|
|
Andrei Smolin
Add-in Express team
Posts: 18828
Joined: 2006-05-11
|
|
Forums
Topics
Search
Help
Login
Register