The log file should show you the command being passed to the executable. Maybe try that exact command outside of Burn?
On Tue, Apr 24, 2012 at 8:57 AM, Miss Parker <caisa.westl...@gmail.com>wrote: > Alright, I tried that (/msiexec /qn /i exePath/) and it worked. That can't > be > good... > > Can you (or anyone else) see any obvious errors with my ExePackage > definition? > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Help-with-silent-install-ExePackage-tp7496163p7496409.html > Sent from the wix-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
