>From wcautil.h (which includes dutil.h)
#define ExitTrace WcaLogError
#define ExitTrace1 WcaLogError
#define ExitTrace2 WcaLogError
#define ExitTrace3 WcaLogError
>From dutil.h:
#define ExitOnFailure(x, s) if (FAILED(x)) { ExitTrace(x, s); goto
LExit; }
#define ExitOnFailure1(x, f, s) if (F
Bill, I'm trying to use the functions that you provided, and I'm just
curious as to where the ExitOnFailure logs are saved? I've placed my
own logs around the function, and I know it's failing somewhere in
there. Thanks.
On 1/3/2012 4:28 PM, Bill Tutt wrote:
> On Tue, Jan 3, 2012 at 5:26 PM,
On Tue, Jan 3, 2012 at 5:26 PM, Bill Tutt wrote:
>
> Something like this:
>
> // Extract files to temp directory.
> hr = PathCreateTempDirectory(NULL, L"HRCAAxeda%03x", 999, &pwszTempDir);
> ExitOnFailure(hr, "Failed to load create temp directory for DLL
> extraction.");
> extractedFiles = tr
On Tue, Jan 3, 2012 at 4:57 PM, Kevin Hebert
wrote:
> The question is though, how do I extract it? I'd thought I was going
> about it the right way, but apparently I'm not.
>
>
I did it by using these two C++ helper functions at the end of the email.
For each file I needed to be extracted I calle
; From: Kevin Hebert [mailto:ke...@legendary-immersion.com]
>>> Sent: Tuesday, January 03, 2012 11:14 AM
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] Accessing file in MSI before it's installed
>>>
>>> This mig
nt before printing this e-mail
>
>> -Original Message-
>> From: Kevin Hebert [mailto:ke...@legendary-immersion.com]
>> Sent: Tuesday, January 03, 2012 11:14 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Accessing fi
In my Product.wxs, I have the following:
*other stuff*
The idea we'd had to was to use SUPPORTDIR as a sort of temp directory
just to install the pem files, and then delete the SUPPORTDIR after it's
purpose has been fulfilled. I'm including this, as it might also be
useful in trying t
Re: [WiX-users] Accessing file in MSI before it's installed
>
> This might sound incredibly silly, but can a custom action have more than one
> BinaryKey? I currently have:
>
> DllEntry="CheckEmailExists" />
>
> Currently, the BinaryKey here is the file that
--Original Message-
From: Adam Kadzban
Sent: Tuesday, January 03, 2012 8:41 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Accessing file in MSI before it's installed
I'm not sure of a way to do it in WIX. I've used Custom Actions like this
b
I'm not sure of a way to do it in WIX. I've used Custom Actions like this
before, but always after I had put down the files they need.
Maybe you can add the pem files as resources inside the DLL? Someone else
might have a better solution though.
-Adam
On Tue, Jan 3, 2012 at 1:14 PM, Kevin Hebe
This might sound incredibly silly, but can a custom action have more
than one BinaryKey? I currently have:
Currently, the BinaryKey here is the file that holds the custom action.
But I'm wanting to access a server and root pem file. Thanks.
On 1/3/2012 12:35 PM, Kevin Hebert wrote:
> Thank
Thanks. I'll take a look into that. The function I'm writing that is
calling the sslConnect function is a custom action in itself. So this
shouldn't be too difficult. Hopefully.
On 1/3/2012 12:24 PM, Adam Kadzban wrote:
> You could include the file as a Binary, then have a custom action call
You could include the file as a Binary, then have a custom action call it:
-Adam
On Tue, Jan 3, 2012 at 12:06 PM, Kevin Hebert wrote:
> I have an sslConnect function which requires a file that is normally
> installed before the function is called. However, due to a change in
> what the clie
13 matches
Mail list logo
