Re: [WiX-users] Managed Custom Action using InstallUtilLib.dll

I have been using managec C++ CA's coded in Visual Studio 2003 for installs. You create a .NET dll and use unmanaged exports .e.g __declspec(dllexport) int __stdcall MyCustomAction(MSIHANDLE hInstall); All your logic is in the installation package and you don't have to leave a carcass behind with

Re: [WiX-users] Easy WiX way for a custom action to call multiple utility DLLs?

In regards to Rob Mensching's comment, > >Statically link. That's what all the WiX CustomActions do and while it >makes the DLLs a bit bigger it totally minimizes the number of >dependencies (especially nasty ones like the Win32 SxS CRT junk). Static linking definitely seems like the right thing

Re: [WiX-users] Easy WiX way for a custom action to call multiple utility DLLs?

Try embedding the other DLL as a custom resource using the .rc file. Extract the DLL first thing when the CA is called. Use delayload linker option or LoadLibrary to call the function in the extracted DLL. I've done this before. A question, how do VC 2005 CA's requiring the C++ CRT Dll work on V