Hi,
I'm assuming your are using managed dll's. I think the caller dll is
expanded to a temporary directory (due MSI not handling managed code). Is
your called dll also expanded or existing there? You can
add System.Diagnostics.Debugger.Launch(); to the beginning of your caller
CA and check if your
ies.
Phil W
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Thursday, August 15, 2013 4:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dependent DLLs of a Custom Action Binary are not
getting loaded properly
When is this action
When is this action scheduled?
Generally it is recommended that custom actions be DLLs in the Binary table
compiled to "statically" include their runtime environment.
Suryadeep Biswal wrote:
Hi,
I have a Type 17 Custom
Action in my wxs file. The Custom Action dll depends on another dll tha
Hi,
I have a Type 17 Custom
Action in my wxs file. The Custom Action dll depends on another dll that is in
the same directory. However, i see that runtime does not load the dependent dll
and as a result loading of the Custom Action fails with error 1157 (One of the
library files needed to run
4 matches
Mail list logo