1. Making dual-purpose packages was difficult in MSI before version 5. At my company, we still need to support Windows prior to Windows 7/Server 2008 so MSI 5 isn't an option yet and we create per-machine installers. With MSI 5, dual purpose packages are easier to create: http://msdn.microsoft.com/en-gb/library/windows/desktop/dd408068%28v=vs.85%29 .aspx You must use per-machine installations if you install anything to shared locations, such as HKLM, Program Files folder, Windows folder, etc. Otherwise the choice may be down to whether you must support users who don't have administrative privileges to install - that would force you to create a per-user package.
2. The ProductState property might help. If you choose to support only per-machine or only per-user, then you don't need to worry about cross-context upgrades from then on. There are API's that can detect all installation contexts of a product, but they require admin privileges. 3. MSI redistributables are preferred over merge modules so that they can be serviced by Windows Update, rather than you having to update your installer. To install multiple MSIs, you'll need a chainer. -----Original Message----- From: Mihajlo Cvetanovic [mailto:mcvetano...@gmail.com] Sent: 23 November 2012 13:47 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Best common practices and migration from VSdeployment project I've found me an answer to fourth question. Still hoping for answers to other questions. If I'm asking the wrong questions please tell me. On Sat, Nov 17, 2012 at 1:29 PM, <wix-users-requ...@lists.sourceforge.net> wrote: > Date: Fri, 16 Nov 2012 17:54:45 +0100 > From: Mihajlo Cvetanovi? <mcvetano...@gmail.com> > Subject: [WiX-users] Best common practices and migration from VS > deployment project > To: wix-users@lists.sourceforge.net > Message-ID: > > <CACBW+BEWg=1fhn2q0pa-os75emzrghjvd_syzschxf2pxr2...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, first time here for me. Assume I know only the very basics > (particularly not the lingo), but willing to read from any link you > throw at me. > > I used to have a very simple Visual Studio's .vdproj project, with one > app written in C++ and a few Microsoft's dll's (CRT and MFC) manually > added in the same folder as plain files (not as merge modules). I want > to move to WiX, and need some guidelines and best common practices. > Major points: > > - I want to use MS redistributables instead of adding dll files manually. > - Previous setup allowed for everyone/"just me" option. > - Application writes some bits of information in HKCU registry during > work, but not during setup. > - The setup (and application) are written in my native language (not > English). I'm handling that fine for now. > - Application is used by various users and in various environments, so > I need to cover > > Questions: > > 1. Should I still allow for everyone/"just me" option? I've found > suggestions to always install for everyone. > 2. How can I handle the problem when previous and new setup differ in > this option? Currently I see two installations in control panel if > this option is different, and new setup does not remove old files from > installation folder. > 3. I guess I should include MS redistributables as merge modules. > Also, I'm guessing that merge modules should be part of the core > feature (Absent="disallow")? Is this correct? > 4. Additionally, how can I install some CA certificates during setup? ----------------------------------------------------------------------------- - Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
