Hello,
I'm trying to find a reliable way to get the path to the running MSI.
Once I have the path, I'd like to spawn an executable that is relative
to the MSI in a custom action. I'd like to try and do this as early as
possible in the execute sequence. I've tried using SOURCEDIR to mixed
results, and I've tried using C++ functions like GetModuleFileName, and
I've tried using the CURRENTDIRECTORY property. What is complicating my
approach is that this has to happen during Group Policy assignment so
most of these functions return C:\Windows\system32, which is where the
main msiexec is running from.
Any ideas?
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
