And don’t forget that once you’re done building your MSI, you should then run it through the MSI->APPX converter so that you can deploy via the Windows Store (ducks and runs for cover before being laughed off the mailing list for suggesting the Windows Store).
Nick Randolph | Built to Roam Pty Ltd | Microsoft MVP – Windows Platform Development | +61 412 413 425 | @thenickrandolph | skype:nick_randolph The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of mike smith Sent: Monday, 23 January 2017 11:44 AM To: Glen Harvy <g...@aquarius.com.au>; ozDotNet <ozdotnet@ozdotnet.com> Subject: Re: Friday Rant (today!) We use it to generate fairly complex MSIs, and MSPs for patches and hotfixes. The WXS and WXI files make your eyes bleed, but once you get over that, it's ok. It's almost unavoidable to use it if you have customers that want to use enterprise policy setups. Mike On Sun, Jan 22, 2017 at 6:37 PM, Glen Harvy <g...@aquarius.com.au<mailto:g...@aquarius.com.au>> wrote: For what it's worth, I agree with you wholeheartedly :-( On 22/01/2017 3:20 PM, Greg Keogh wrote: So overall, either I'm really missing something, or nothing much has changed and WiX is still just a huge XML file with a jumbled set of command line tools. GK -- Meski http://courteous.ly/aAOZcv "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
