barry wrote:
>
>
> Hi There,
> After another long day trying to isolate this problem I think I am making
> some progress..
>
> I changed the Addin GUID to a new guid and regenerated the wix fragment
> and reinstalled on my development box. The Addin installs correctly and
> gets loaded in wor
Wilson, Phil wrote:
>
> A couple of things:
>
> 1, It looks like your versions are 1.0.* and the compiler will generate a
> new one every time you build. If you heat once and then rebuild your
> add-in you're going to have a mismatch. I recommend setting a complete
> version. If you haven't sp
Hi Phil,
Some more info...
I turned on Fusion in the registry for logging assembly load errors and the
following error is logged when Word loads and then disables the AddIn.
-
*** Assembly Binder Log Entry (01/05/2009 @ 12
Wilson, Phil wrote:
>
> A couple of things:
>
> 1, It looks like your versions are 1.0.* and the compiler will generate a
> new one every time you build. If you heat once and then rebuild your
> add-in you're going to have a mismatch. I recommend setting a complete
> version. If you haven't sp
our MSI file, so install with a log and see what's
going on.
Phil Wilson
-Original Message-
From: barry [mailto:barrylar...@gmail.com]
Sent: Thursday, April 30, 2009 9:29 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] registering a .net com assembly
barry wrote:
&
Hi there,
I am having some problems registering my com assembly. This assembly is a
dot net office addin dll.
I used the following command to generate the registry keys:
>heat file DTIOfficeAddIn.dll -out MyComExposedLibrary.wxs -scom
This generated the registry keys and values keys which I add
barry wrote:
>
> Hi there,
> I am having some problems registering my com assembly. This assembly is a
> dot net office addin dll.
>
> I used the following command to generate the registry keys:
>
>>heat file DTIOfficeAddIn.dll -out MyComExposedLibrary.wxs -scom
>
> This generated the regist
7 matches
Mail list logo
