Re: [WiX-users] Build speed, suggestions?
I haven't spent a huge amount of time on this topic because we are generally happy with our build time, but I can imagine merge modules are disk i/o intensive not cpu / memory intensive. There is a lot of copying going on to get the files, create the cabinet and stream it into storage. Then again to copy the msm, extract the cabs, extract the files, rebuild the new cab and put it back into storage of the msi. I'd suggest building in a ramdisk but these days windows is pretty darn effecient at it's disk caching as long as you give it plenty of memory. Maybe try giving it more first. Otherwise look at how you set your storage up on the Hyper-V. I don't know if you snapshot and rollback your vm's ( we have a build farm of around 100+ VM's that we do this to ) but if you don't you can consider setting up a direct disk for the VM. Of course there is always more expensive disk solutions. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Bill Packard To: wix-users@lists.sourceforge.net Sent: Fri, October 8, 2010 1:26:18 PM Subject: [WiX-users] Build speed, suggestions? I have recently migrated from Wise to WiX. I have approximately 150 merge modules (at some point in the future I may be able to implement libs instead of merge modules, but for now .) and several installs that include some subset of the merge modules. I have implemented a VS solution for all the merge modules and for each MSI project. I am wondering if amyone has any insight or suggestions as to how I might reduce the compilation time for the merge module solution? I have attempted simply loading the solution with devenv and sending each wixproj to msbuild seperately. Both take basically the same amount of time. I also attempted to parallelize the calls to msbuild, both using the maxcpu switch and by starting each process as a background process (under cygwin), neither approach succeeded in reducing the build time. The system CPU seems to idle at about 20% and the memory footprint is ~ 0.5GB. The machine is a Quad core with 4GB, running Windows Server 2003 R2 (32bit). On real hardware the merge module solution takes about 30 minutes. But we recently virtualized our build machines and on the virtual systems the same solution takes about 90 minutes. Virtual servers are running Microsoft's Hyper-V Platform, each virtual server currently has 4 processors allocated, 4GB, running Server 2003 R2. Suggestions would be welcome. Thanks, Bill -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installer appears very slow
Thanks very much to all who answered. My installer takes only 10 seconds total now on Win7. -Original Message- From: Alexander Kozlenko [mailto:alexander.kozle...@hotmail.com] Sent: Friday, October 08, 2010 11:33 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Installer appears very slow Yes, you can safely specify code (as sample) for enabling this option. This property will be ignored for Windows Installer prior to 5.0 and will be used under installer 5.0. This code will not override MSIFASTINSTALL property, this code will set value for this property for your install session. -Original Message- From: Lena Vinogradov [mailto:lena.vinogra...@quest.com] Sent: Friday, October 08, 2010 6:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installer appears very slow Thank you, I see in the log that it is in fact spending 9 seconds out of 20 of total for creating restore point. Is there a way to specify this MSIFASTINSTALL property value from within Wix? I mean something like: Would it overwrite the built-in MSI property when install is running on Windows 7? Thanks! -Original Message- From: Alexander Kozlenko [mailto:alexander.kozle...@hotmail.com] Sent: Thursday, October 07, 2010 5:00 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Installer appears very slow Creating Restore Point. You can use MSIFASTINSTALL (http://msdn.microsoft.com/en-us/library/dd408005(VS.85).aspx) property for disabling this and some other things, but this will work only for Windows Installer 5.0 (Windows 7 only, no redist). -Original Message- From: Lena Vinogradov [mailto:lena.vinogra...@quest.com] Sent: Thursday, October 07, 2010 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Installer appears very slow Hi , I wrote a very small installer - copies about 20 files, starts service, adds entry to firewall exception list. I originally used WixUI_Minimal then had to switch to WixUI_InstallDir with one dialog skipped. Even when I used WixUIMininal the installer seems to be very slow - it takes up to 10 sec on a good machine after you click install (or next ) button until it actually reports copying files/starting service, etc. It's even worse on slow machines. Is there any way to troubleshoot it? What could installer be doing during this time? Thanks in advance, Elena -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Build speed, suggestions?
I have recently migrated from Wise to WiX. I have approximately 150 merge modules (at some point in the future I may be able to implement libs instead of merge modules, but for now .) and several installs that include some subset of the merge modules. I have implemented a VS solution for all the merge modules and for each MSI project. I am wondering if amyone has any insight or suggestions as to how I might reduce the compilation time for the merge module solution? I have attempted simply loading the solution with devenv and sending each wixproj to msbuild seperately. Both take basically the same amount of time. I also attempted to parallelize the calls to msbuild, both using the maxcpu switch and by starting each process as a background process (under cygwin), neither approach succeeded in reducing the build time. The system CPU seems to idle at about 20% and the memory footprint is ~ 0.5GB. The machine is a Quad core with 4GB, running Windows Server 2003 R2 (32bit). On real hardware the merge module solution takes about 30 minutes. But we recently virtualized our build machines and on the virtual systems the same solution takes about 90 minutes. Virtual servers are running Microsoft's Hyper-V Platform, each virtual server currently has 4 processors allocated, 4GB, running Server 2003 R2. Suggestions would be welcome. Thanks, Bill -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using a Custom Action dll in another solution
Hi, since you didn't include how your includeing the CA it it's hard to help. This is how I include mine. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-a-Custom-Action-dll-in-another-solution-tp5614711p5615386.html Sent from the wix-users mailing list archive at Nabble.com. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installer appears very slow
Yes, you can safely specify code (as sample) for enabling this option. This property will be ignored for Windows Installer prior to 5.0 and will be used under installer 5.0. This code will not override MSIFASTINSTALL property, this code will set value for this property for your install session. -Original Message- From: Lena Vinogradov [mailto:lena.vinogra...@quest.com] Sent: Friday, October 08, 2010 6:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installer appears very slow Thank you, I see in the log that it is in fact spending 9 seconds out of 20 of total for creating restore point. Is there a way to specify this MSIFASTINSTALL property value from within Wix? I mean something like: Would it overwrite the built-in MSI property when install is running on Windows 7? Thanks! -Original Message- From: Alexander Kozlenko [mailto:alexander.kozle...@hotmail.com] Sent: Thursday, October 07, 2010 5:00 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Installer appears very slow Creating Restore Point. You can use MSIFASTINSTALL (http://msdn.microsoft.com/en-us/library/dd408005(VS.85).aspx) property for disabling this and some other things, but this will work only for Windows Installer 5.0 (Windows 7 only, no redist). -Original Message- From: Lena Vinogradov [mailto:lena.vinogra...@quest.com] Sent: Thursday, October 07, 2010 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Installer appears very slow Hi , I wrote a very small installer - copies about 20 files, starts service, adds entry to firewall exception list. I originally used WixUI_Minimal then had to switch to WixUI_InstallDir with one dialog skipped. Even when I used WixUIMininal the installer seems to be very slow - it takes up to 10 sec on a good machine after you click install (or next ) button until it actually reports copying files/starting service, etc. It's even worse on slow machines. Is there any way to troubleshoot it? What could installer be doing during this time? Thanks in advance, Elena -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installer appears very slow
Thank you, I see in the log that it is in fact spending 9 seconds out of 20 of total for creating restore point. Is there a way to specify this MSIFASTINSTALL property value from within Wix? I mean something like: Would it overwrite the built-in MSI property when install is running on Windows 7? Thanks! -Original Message- From: Alexander Kozlenko [mailto:alexander.kozle...@hotmail.com] Sent: Thursday, October 07, 2010 5:00 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Installer appears very slow Creating Restore Point. You can use MSIFASTINSTALL (http://msdn.microsoft.com/en-us/library/dd408005(VS.85).aspx) property for disabling this and some other things, but this will work only for Windows Installer 5.0 (Windows 7 only, no redist). -Original Message- From: Lena Vinogradov [mailto:lena.vinogra...@quest.com] Sent: Thursday, October 07, 2010 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Installer appears very slow Hi , I wrote a very small installer - copies about 20 files, starts service, adds entry to firewall exception list. I originally used WixUI_Minimal then had to switch to WixUI_InstallDir with one dialog skipped. Even when I used WixUIMininal the installer seems to be very slow - it takes up to 10 sec on a good machine after you click install (or next ) button until it actually reports copying files/starting service, etc. It's even worse on slow machines. Is there any way to troubleshoot it? What could installer be doing during this time? Thanks in advance, Elena -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] registry key change on radio button selection
Hi, Hard to guess without a code sample but have you made declared your property secure? See http://wix.sourceforge.net/manual-wix3/wix_xsd_property.htm Dave -Original Message- From: David Amey [mailto:da...@creative-engine.co.uk] Sent: 08 October 2010 12:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] registry key change on radio button selection Hi all, I once again require you expertise; I have a registry key that I need stored [ok so far], the value is set to a property which changes on a radio button selection. However the key value only ever takes the default value of the property, it doesn't pick up the change when a different button is selected? Any assistance will be greatly appreciated! Thanks in advance! David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ 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. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Application registry keys best practise
That problem can be mitigated: http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Property-pattern Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Bruce Cran To: wix-users@lists.sourceforge.net Sent: Fri, October 8, 2010 6:26:29 AM Subject: Re: [WiX-users] Application registry keys best practise On Friday 08 October 2010 10:36:12 Mark Simonetti wrote: > Is it best practise for the installer to create all the registry keys > that the application itself might create? I imagine the biggest pros to > that would be that the installer controls the default settings, also > making them configurable on the installer command line, and also the > keys will be removed if the application is uninstalled keeping it clean. The potential problem with having the installer create and remove them is that users probably expect to be able to reinstall the application and have their data still be accessible. -- Bruce Cran -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using a Custom Action dll in another solution
Hi All, I created a Custom Action dll (.NET) for a test solution. In this solution I have the CA project, a simple test app project and a WiX setup project. This works fine. I'm now trying to take the CA dll produced by this test solution into our live project. I've copied both dlls (the Deploy.dll and Deploy.CA.dll) in the live projects Libs folder and tried to add a reference to it in the WiX project in this solution. It just errors with the following message: "A reference to [path to Dll] could not be added. Please make sure that the file is accessible, and that it is a valid WiX reference." There isn't any reason it won't be accessible so I can only assume that there is something wrong with the dll and it's not being recognised as a WiX reference. What should I be doing to fix this? And why would it work fine when used from within the same solution but fail when added to a different solution? Very confusing ... Thanks in advance, James LalPac Limited registered in England No: 4211747 Partner in Licensing to over 120 UK local government authorities. Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK. Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 (0)1249 462542 Web: www.lalpac.com - Email: i...@lalpac.com This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this e-mail. Opinions advice, conclusions and other information in this message that do not relate to the official business of LalPac Ltd shall be understood as neither given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall bear no responsibility whatsoever in respect thereof. This e-mail and any attachments have been checked by anti-virus software and are believed to be free of viruses but it is your responsibility to carry out all necessary virus checks and LalPac Ltd accepts no liability in connection therewith. The Company actively monitors all incoming and outgoing e-mails to ensure a satisfactory level of customer service is maintained, to maintain Company security, and to prevent abuse of the Company systems. Please do not print this e-mail unless absolutely necessary - SAVE PAPER -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Application registry keys best practise
Additionally, you may get upgrades, patches and automatic repairs recreating the keys and values, depending on what you do with them and if they are keypaths. -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: 08 October 2010 12:26 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Application registry keys best practise On Friday 08 October 2010 10:36:12 Mark Simonetti wrote: > Is it best practise for the installer to create all the registry keys > that the application itself might create? I imagine the biggest pros to > that would be that the installer controls the default settings, also > making them configurable on the installer command line, and also the > keys will be removed if the application is uninstalled keeping it clean. The potential problem with having the installer create and remove them is that users probably expect to be able to reinstall the application and have their data still be accessible. -- Bruce Cran -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ 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. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] registry key change on radio button selection
Hi all, I once again require you expertise; I have a registry key that I need stored [ok so far], the value is set to a property which changes on a radio button selection. However the key value only ever takes the default value of the property, it doesn't pick up the change when a different button is selected? Any assistance will be greatly appreciated! Thanks in advance! David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Application registry keys best practise
On Friday 08 October 2010 10:36:12 Mark Simonetti wrote: > Is it best practise for the installer to create all the registry keys > that the application itself might create? I imagine the biggest pros to > that would be that the installer controls the default settings, also > making them configurable on the installer command line, and also the > keys will be removed if the application is uninstalled keeping it clean. The potential problem with having the installer create and remove them is that users probably expect to be able to reinstall the application and have their data still be accessible. -- Bruce Cran -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Application registry keys best practise
Is it best practise for the installer to create all the registry keys that the application itself might create? I imagine the biggest pros to that would be that the installer controls the default settings, also making them configurable on the installer command line, and also the keys will be removed if the application is uninstalled keeping it clean. Thanks, Mark. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installer appears very slow
You can get a log of the install and each entry will contain a time stamp. To get a full log run "msiexec /l*vx log.txt". I usually find that just using "msiexec /leavx log.txt" gets me most of the information I need. Rob On 07/10/2010 21:21, Lena Vinogradov wrote: > Hi , > I wrote a very small installer - copies about 20 files, starts service, adds > entry to firewall exception list. I originally used WixUI_Minimal then had to > switch to WixUI_InstallDir with one dialog skipped. > > Even when I used WixUIMininal the installer seems to be very slow - it takes > up to 10 sec on a good machine after you click install (or next ) button > until it actually reports copying files/starting service, etc. It's even > worse on slow machines. > > Is there any way to troubleshoot it? What could installer be doing during > this time? > > Thanks in advance, > Elena > -- > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2& L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
