Re: [WiX-users] Bootstrap conditioned on OSbittage
Gotcha, thanks for the advice. 'Remember installation doesn't just mean install forget”’ - but it’s just glorified xcopy, we all know that! On 10 Jul 2015, at 10:45, Pally Sandher pally.sand...@iesve.com wrote: You can if you want but I'd advise against it. It's still installed so if a user removes some or all of the individual parts of your package then tries to re-run the package to install again, the package will show up with Uninstall. If you haven't already, I would suggest trying things out on a VM so you can see the behaviour for yourself customise it accordingly. Remember installation doesn't just mean install forget (unless you really like dealing with support enquiries from all your users). Palbinder Sandher Software Platform Engineer T: +44 (0)141 945 8500 F: +44 (0)141 945 8501 http://www.iesve.com Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 15:22 To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Ah that's great, and I can hide the bundle ARP itself as well? On 09/07/2015 11:51, Pally Sandher wrote: Unless the 3rd party installer is an MSI (which from your previous e-mails, it appears they're executables), Burn won't do that regardless. If it is an MSI you can set the Visible attribute on the MsiPackage element to yes it won't do it either. Palbinder Sandher Software Platform Engineer T: +44 (0)141 945 8500 F: +44 (0)141 945 8501 http://www.iesve.com Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 11:33 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Thank David yes I agree with what your saying. I am a bit concerned the 3rd party wouldn't like our bundle 'wrapping' and hiding their ARP entry. Is it possible to only hide the bundles entry? dotNetInstaller looks good. (I was worried it was C# but the bootstrapper element is C++) . Ta On 09/07/2015 10:44, David Watson wrote: Hi, Experience has taught that the best experience for the user and for the developer and the support organisation is to follow the way that the burn bundle works, it has been very carefully designed. Fire and forget bootstrappers are an alternative (I used to use this many years ago http://dblock.github.io/dotnetinstaller/) and are still widely used. A single point of entry in ARP that allows your user to control the contents of the bundle is much simpler to support than a whole array of packages. [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014. p ng] www.sdl.com/ www.sdl.com 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. -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 10:06 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to know how. But am also looking for alternatives to WiX's current offering and thought this would be an ok place to ask, since the experience level here is so high!. Thanks for your help on this. On 09/07/2015 02:16, Hoover, Jacob wrote: My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free
Re: [WiX-users] Bootstrap conditioned on OSbittage
You can if you want but I'd advise against it. It's still installed so if a user removes some or all of the individual parts of your package then tries to re-run the package to install again, the package will show up with Uninstall. If you haven't already, I would suggest trying things out on a VM so you can see the behaviour for yourself customise it accordingly. Remember installation doesn't just mean install forget (unless you really like dealing with support enquiries from all your users). Palbinder Sandher Software Platform Engineer T: +44 (0)141 945 8500 F: +44 (0)141 945 8501 http://www.iesve.com Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 15:22 To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Ah that's great, and I can hide the bundle ARP itself as well? On 09/07/2015 11:51, Pally Sandher wrote: Unless the 3rd party installer is an MSI (which from your previous e-mails, it appears they're executables), Burn won't do that regardless. If it is an MSI you can set the Visible attribute on the MsiPackage element to yes it won't do it either. Palbinder Sandher Software Platform Engineer T: +44 (0)141 945 8500 F: +44 (0)141 945 8501 http://www.iesve.com Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 11:33 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Thank David yes I agree with what your saying. I am a bit concerned the 3rd party wouldn't like our bundle 'wrapping' and hiding their ARP entry. Is it possible to only hide the bundles entry? dotNetInstaller looks good. (I was worried it was C# but the bootstrapper element is C++) . Ta On 09/07/2015 10:44, David Watson wrote: Hi, Experience has taught that the best experience for the user and for the developer and the support organisation is to follow the way that the burn bundle works, it has been very carefully designed. Fire and forget bootstrappers are an alternative (I used to use this many years ago http://dblock.github.io/dotnetinstaller/) and are still widely used. A single point of entry in ARP that allows your user to control the contents of the bundle is much simpler to support than a whole array of packages. [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014. p ng] www.sdl.com/ www.sdl.com 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. -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 10:06 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to know how. But am also looking for alternatives to WiX's current offering and thought this would be an ok place to ask, since the experience level here is so high!. Thanks for your help on this. On 09/07/2015 02:16, Hoover, Jacob wrote: My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair
Re: [WiX-users] Bootstrap conditioned on OSbittage
Thank David yes I agree with what your saying. I am a bit concerned the 3rd party wouldn't like our bundle 'wrapping' and hiding their ARP entry. Is it possible to only hide the bundles entry? dotNetInstaller looks good. (I was worried it was C# but the bootstrapper element is C++) . Ta On 09/07/2015 10:44, David Watson wrote: Hi, Experience has taught that the best experience for the user and for the developer and the support organisation is to follow the way that the burn bundle works, it has been very carefully designed. Fire and forget bootstrappers are an alternative (I used to use this many years ago http://dblock.github.io/dotnetinstaller/) and are still widely used. A single point of entry in ARP that allows your user to control the contents of the bundle is much simpler to support than a whole array of packages. [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] www.sdl.com/ www.sdl.com 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. -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 10:06 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to know how. But am also looking for alternatives to WiX's current offering and thought this would be an ok place to ask, since the experience level here is so high!. Thanks for your help on this. On 09/07/2015 02:16, Hoover, Jacob wrote: My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair/uninstall so it effectively wouldn't appear that the package had been 'bundled'? Many Thanks On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com wrote: I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-boo t strapper-project-itself What would you guys recommend for this use case? -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today
Re: [WiX-users] Bootstrap conditioned on OSbittage
Unless the 3rd party installer is an MSI (which from your previous e-mails, it appears they're executables), Burn won't do that regardless. If it is an MSI you can set the Visible attribute on the MsiPackage element to yes it won't do it either. Palbinder Sandher Software Platform Engineer T: +44 (0)141 945 8500 F: +44 (0)141 945 8501 http://www.iesve.com Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 11:33 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Thank David yes I agree with what your saying. I am a bit concerned the 3rd party wouldn't like our bundle 'wrapping' and hiding their ARP entry. Is it possible to only hide the bundles entry? dotNetInstaller looks good. (I was worried it was C# but the bootstrapper element is C++) . Ta On 09/07/2015 10:44, David Watson wrote: Hi, Experience has taught that the best experience for the user and for the developer and the support organisation is to follow the way that the burn bundle works, it has been very carefully designed. Fire and forget bootstrappers are an alternative (I used to use this many years ago http://dblock.github.io/dotnetinstaller/) and are still widely used. A single point of entry in ARP that allows your user to control the contents of the bundle is much simpler to support than a whole array of packages. [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.p ng] www.sdl.com/ www.sdl.com 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. -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 10:06 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to know how. But am also looking for alternatives to WiX's current offering and thought this would be an ok place to ask, since the experience level here is so high!. Thanks for your help on this. On 09/07/2015 02:16, Hoover, Jacob wrote: My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair/uninstall so it effectively wouldn't appear that the package had been 'bundled'? Many Thanks On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com wrote: I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-bo o t strapper-project-itself What would you guys recommend for this use case? - - Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrap conditioned on OSbittage
Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to know how. But am also looking for alternatives to WiX's current offering and thought this would be an ok place to ask, since the experience level here is so high!. Thanks for your help on this. On 09/07/2015 02:16, Hoover, Jacob wrote: My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair/uninstall so it effectively wouldn't appear that the package had been 'bundled'? Many Thanks On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com wrote: I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-boot strapper-project-itself What would you guys recommend for this use case? -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrap conditioned on OSbittage
Hi, Experience has taught that the best experience for the user and for the developer and the support organisation is to follow the way that the burn bundle works, it has been very carefully designed. Fire and forget bootstrappers are an alternative (I used to use this many years ago http://dblock.github.io/dotnetinstaller/) and are still widely used. A single point of entry in ARP that allows your user to control the contents of the bundle is much simpler to support than a whole array of packages. [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] www.sdl.com/ www.sdl.com 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. -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 10:06 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to know how. But am also looking for alternatives to WiX's current offering and thought this would be an ok place to ask, since the experience level here is so high!. Thanks for your help on this. On 09/07/2015 02:16, Hoover, Jacob wrote: My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair/uninstall so it effectively wouldn't appear that the package had been 'bundled'? Many Thanks On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com wrote: I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-boo t strapper-project-itself What would you guys recommend for this use case? -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been scanned for malware by Websense. www.websense.com -- Don't Limit Your Business. Reach
Re: [WiX-users] Bootstrap conditioned on OSbittage
Ah that's great, and I can hide the bundle ARP itself as well? On 09/07/2015 11:51, Pally Sandher wrote: Unless the 3rd party installer is an MSI (which from your previous e-mails, it appears they're executables), Burn won't do that regardless. If it is an MSI you can set the Visible attribute on the MsiPackage element to yes it won't do it either. Palbinder Sandher Software Platform Engineer T: +44 (0)141 945 8500 F: +44 (0)141 945 8501 http://www.iesve.com Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 11:33 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Thank David yes I agree with what your saying. I am a bit concerned the 3rd party wouldn't like our bundle 'wrapping' and hiding their ARP entry. Is it possible to only hide the bundles entry? dotNetInstaller looks good. (I was worried it was C# but the bootstrapper element is C++) . Ta On 09/07/2015 10:44, David Watson wrote: Hi, Experience has taught that the best experience for the user and for the developer and the support organisation is to follow the way that the burn bundle works, it has been very carefully designed. Fire and forget bootstrappers are an alternative (I used to use this many years ago http://dblock.github.io/dotnetinstaller/) and are still widely used. A single point of entry in ARP that allows your user to control the contents of the bundle is much simpler to support than a whole array of packages. [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.p ng] www.sdl.com/ www.sdl.com 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. -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: 09 July 2015 10:06 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to know how. But am also looking for alternatives to WiX's current offering and thought this would be an ok place to ask, since the experience level here is so high!. Thanks for your help on this. On 09/07/2015 02:16, Hoover, Jacob wrote: My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair/uninstall so it effectively wouldn't appear that the package had been 'bundled'? Many Thanks On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com wrote: I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-bo o t strapper-project-itself What would you guys recommend for this use case? - - Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https
Re: [WiX-users] Bootstrap conditioned on OSbittage
My first question would be why. What do you need to do that you can't at least allow your bundle be in the chain and let burn do its work before deferring to your final exe installer? -Original Message- From: Matt O'Connell [mailto:techsupport...@gmail.com] Sent: Wednesday, July 08, 2015 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair/uninstall so it effectively wouldn't appear that the package had been 'bundled'? Many Thanks On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com wrote: I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-boot strapper-project-itself What would you guys recommend for this use case? -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrap conditioned on OSbittage
Sorry guys can I get some advise on this one please? I realise burn can't 'fire and forget' see http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ but what (free) methods are there available to do this? Can anyone reccommend something? Alternatively is it possible to bundle (and conditionalise) the exes but hide the bundle's ARP entry and expose the third party exes ARP entries? If so could the user could use that to repair/uninstall so it effectively wouldn't appear that the package had been 'bundled'? Many Thanks On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com wrote: I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-bootstrapper-project-itself What would you guys recommend for this use case? -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrap conditioned on OSbittage
I've got a third party exe with 2 versions to bootstrap based on OS bittage, our current setup code only does this for MSIs. I've found how to do this with burn bundle but don't need the bundleness of it as per this http://stackoverflow.com/questions/30010837/i-dont-want-install-a-bootstrapper-project-itself What would you guys recommend for this use case? -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
