What Blair suggests is working fine:
"C:\Program Files (x86)\WiX Toolset v3.7\SDK\MakeSfxCA.exe"
$(TargetDir)MBACAs.dll "C:\Program Files (x86)\WiX Toolset
v3.7\SDK\x86\SfxCA.dll" $(TargetDir)CustomActions.dll
$(SolutionDir)Libs\MY_NATIVE_WIN32.DLL $(TargetDir)CustomAction.config
"C:\Program Fi
or Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Actions that need to call unmanaged DLL
In managed CAs using DTF you can include unmanaged DLLs in much the same way
you can include dependent assemblies and they will be extracted alongside your
CA's main assembly.
Blair
&g
ourceforge.net
> Date: Tue, 2 Jul 2013 04:33:27 +
> Subject: Re: [WiX-users] Custom Actions that need to call unmanaged DLL
>
> 1) yes
> 2) you could
> 3) yes, you could but you would need to manually extract the dll in you
> managed ca (after embedding it in the msi)
1) yes
2) you could
3) yes, you could but you would need to manually extract the dll in you managed
ca (after embedding it in the msi) and then pinvoke that dll. Fairly certain
.net requires the native libs to exist as its loading your assembly, so you
would need to build the reference to the n
I would like do something like this:
CustomActions.cs:
[CustomAction]
Public static ActionResults MyCustomAction(Session session)
{
...
NativeMethod.XYZ xyz = new NativeMethod.XYZ();
}
NativeMethods.cs:
internal static class NativeMethods
{
Intern
5 matches
Mail list logo