Chuck wrote:
> Why is it not recommended and what about it is difficult to get right?
>
You have to extract the files securely; an insecure extraction for a
per-machine install is a security vulnerability, as it can be used to
execute arbitrary code as the local system account (MSI when eleva
Bob,
Thanx for your quick response...
Why is it not recommended and what about it is difficult to get right?
Cheers
Chuck
Bob Arnson wrote:
> Chuck wrote:
>> Is it possible to call a third party dll, included in my installer as
>> a binary file only, from a custom action that is in a C++ dll?
Chuck wrote:
> Is it possible to call a third party dll, included in my installer as a
> binary file only, from a custom action that is in a C++ dll?
>
No. MSI extracts one file at a time as needed to execute a CA.
> If that isn't possible is that anyway to access a 3rd party dll from my
> cu
Is it possible to call a third party dll, included in my installer as a
binary file only, from a custom action that is in a C++ dll?
If that isn't possible is that anyway to access a 3rd party dll from my
custom action prior to the installation of files?
Thanx
Chuck
---
4 matches
Mail list logo
