ent: Thursday, December 06, 2007 6:16 PM
> Cc: wix-users@lists.sourceforge.net;
> [EMAIL PROTECTED]
>
> Subject: Re: [WiX-users] Multi-file assembly problem
>
> Yes, I'm creating the manifests myself. Or rather I'm taking the
> automatically generated manifests, modifying th
: Re: [WiX-users] Multi-file assembly problem
Yes, I'm creating the manifests myself. Or rather I'm taking the
automatically generated manifests, modifying them if necessary, and
signing them "by hand" using mt.exe, makecat and signtool.
I started out with manifest dependencies
L PROTECTED]>
>
> Sent by: [EMAIL PROTECTED]
>
> 12/06/2007 04:29 PM
>
> To wix-users@lists.sourceforge.net, [EMAIL PROTECTED]
>
> cc
>
> Subject Re: [WiX-users] Multi-file assembly problem
>
>
>
>
>
>
> The problem is that if I installed everythin
ger" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
12/06/2007 04:29 PM
To
wix-users@lists.sourceforge.net, [EMAIL PROTECTED]
cc
Subject
Re: [WiX-users] Multi-file assembly problem
The problem is that if I installed everything via the old method (each
of the three files set u
The problem is that if I installed everything via the old method (each
of the three files set up as its own assembly with its own WinSxS
folder) and then copied the DLL2 and DLL3 files from their WinSxS
folders into the WinSxS folder for DLL1 then everything ran correctly.
If i can just recreate t
> Or it _does_ cause them to get copied over to the DLL1 side-by-side
> folder, but then my program can't find DLL1 anymore for reasons I
> can't figure out.
Uhh... I think I can explain this one. Consider the following case:
DLL1 in folder
DLL2 in folder
DLL1 loads DLL2 using LoadLibrary (a
6 matches
Mail list logo
