By two transaction cycle I mean perform two transactions, first a remove, and then an install, which can't be combined, requiring twice the time and the effort of some sort of bootstrapper (used in an atypical fashion).
-----Original Message----- From: Scharp, Craig [mailto:craig.sch...@zytax.com] Sent: Tuesday, October 27, 2009 7:39 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Features Hi Blair, Thanks for the response and the information. You understand correctly. I'm using different entries in the directory table with different id's, but they are different physical paths. In hind-site, that was probably a mistake that I will correct in future releases. Not sure what you mean by two-transaction cycle and multi-instancing, but I will look that up and figure it out. Thanks again for your time. I will possibly re-address this after I have worked with the multi-instancing and/or two-transaction cycle. -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Monday, October 26, 2009 7:47 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Features >From your description you have one package that installs both website and database and you use two features, one for database and the other for website? If you use the same "installation directory" for both the components of both features they will use that same directory on maintenance transactions (you will need either a major upgrade or a remove/install two-transaction cycle to change directories). The first order solution is to use different entries in the directory table for your database scripts and your website files. They don't have to be different physical directories, but they do need to have different IDs. However, you still have the issue that all directories are set on the first installation of the product, meaning you have to set both the website and the database script directories no matter what features you are installing if you intend to allow the other feature to be added later. You could work around that by multi-instancing your installation, but that may become more complex than you want your installation to be. -----Original Message----- From: Scharp, Craig [mailto:craig.sch...@zytax.com] Sent: Monday, October 26, 2009 6:06 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Features Hi wix users, My install allows the users to install a website and/or database using typical or custom features. Currently, if the user installs the database first, I put the database scripts in a temp folder, but the product is registered with add/remove programs. For the database install, I have suppressed the IIS actions. When the user installs the website, after the database-only install, the website content is being installed into the temp folder that was used for the database-only install instead of where the user said to put the website content (C:\Inetpub\wwwroot\mywebsite). Looking at the logs, the installer is changing the value of installdir from what the dialog sets it to the temp folder used in the previous database-only install. I have tried to only register the product for the website feature, so the database feature does not register, but I'm having difficulty doing that conditionally. Installer appears to be ignoring the condition and not registering for either option. Has anyone run into this or know of a way to get around this? Ultimately, I would like the installer to register for both, but then use the installdir path that the user selected for the website. By the way, that control on the dialog is mapped to the directory, and in the log it is getting change properly, but installer is re-changing that. However, if that's impossible, I would settle for only registering the product conditionally when the website feature is selected. Thanks in advance for any suggestions! ------------------------------------------------------------------------ ---- -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
