In article <[EMAIL PROTECTED]>,
"Kalvagadda, SivaKrishna \(MLX Technology\)" <[EMAIL PROTECTED]> writes:
> I have requirement of executing the .reg, .msi, .bat as a part of
> installation of WIX MSI. Could someone help how to execute these kind of
> files from WIX v3
Let's take them one at a time:
.reg: Don't use the .reg file; instead put the registry values in the
.reg file into a component and install the component.
.bat: Usually running a batch file at install time is a bad idea. It
looks lame to see DOS boxes flash up during install time -- although
many people do it, I always think "man, these guys must suck" every
time I watch an installer do it. It creates a bad first impression.
If you absolutely must do it, run cmd.exe /c <bat file>. Even better
is to run it in a way that hides the window.
.msi: Windows Installer packages are transaction based. You can't
start a new transaction inside another transaction. So you can't
execute an MSI from inside another MSI. If you have dependent
products that your application requires, you should handle this in a
bootstrapper that sequences the two transactions (dependent product,
then your application) one after the other.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
