I see you've already gone down the exe path somewhat, but I would like
to point out that you can debug MSI DLLs - just not via the debugger
(albeit maybe you can, as the links below made mention of info in
MSI.chm, but I believe it is meant to be a lot of effort). You need to
rely on other debugging methods such as logging. You could do this by
just using message boxes if you don't require too much, or you could
write a simple log file system, or finally you could output logging
information to the normal msiexec.exe log mechanism. The last is my
preference so here are some links for future reference:
http://community.macrovision.com/archive/index.php?t-97544.html
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1665655&SiteID=1
http://www.codeproject.com/install/msicustomaction.asp?df=100&forumid=31
59&exp=0&select=2114040
Anyway, if you search for MsiRecordSetString and logging you should be
well on your way. I've got a function that does exactly this in one of
my custom action dlls, and it proved invaluable.
As for you how to pass command line options dynamically for your exe in
WiX, I've not done that. I wonder if you can just use [PROPERTYNAME] for
the command line arguments and it interpolates them.
Good luck,
Ian.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of srinivas
nomu
Sent: Wednesday, 18 July 2007 7:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to call an exe
I really fed up working with .dll as there is no debug available. Now I
created an .exe with the same code.
<snip>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
