[wix-users] Wix managed custom action DLL is not working in deployable system

[Edwin Castro]

This certainly smells like a dependency problem.

I don't have experience with *managed* C++ custom actions so I'm going to
miss something here or there, but for native C++ custom actions you really
want to statically link all your dependencies to avoid this problem. The
difficulty with dependencies is that the Windows Installer will *only*
extract the binary associated with the custom action DLL. This means that
any dependencies *must* be "installed" prior to custom action use. If your
dependency is used only in your custom action, then you are installing code
that is only used during setup.

I vaguely remember there being a way to document which dependencies are
required for managed custom actions so that they can be packaged and
automatically extracted and used during setup *but* I don't know how to do
this. Perhaps I'm just imaging this and there really is no way to do this.

If you are already writing your custom action in C++ then is it possible to
make it a native C++ custom action and statically link all your
dependencies?

--
Edwin G. Castro


On Wed, May 8, 2019 at 4:31 AM Sebastian, ChinchuX via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> Hi All,
> Could you please help us to solve the below mentioned issue
> We have tried the Wix managed custom action C++ method and created a
> Customaction.dll and passed the input parameters from product.wxs and
> created a product.msi
>
> Issues
> Build msi is working on our system but it is not working on another
> system(deployable system).
> Is that because of missing dependencies? We have copied all supporting DLL
> with the msi. Still not working.
> Does it have any dotnet dependencies?
>
>
>
> Thanks & Regards,
> Chinchu
>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>