I thought a patch installer (.MSP) did not have a UI. You might have a more controlled environment, but without a UI we couldn't prompt for SQL credentials and thus couldn't run SQL Scripts in a patch. If you can hard code credentials or there actually is some way to display a dialog to the user for their credentials during a patch then I might revisit. So, we use minor updates instead of patches here.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colin Law Sent: Wednesday, July 16, 2008 7:48 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] SqlScript, XmlFile, Pyro and patching Hi, I'm trying to create a patch using Pyro (Version 3.0.4227.0). Our product installer performs various functions, installs executables/services, runs SqlServer scripts, configures settings files based upon user settings etc. I now wish to create a patch to update installed files, but also executes addition sql on a SqlServer database and add to existing config files. I'm failing to understand how patching a database or updating these configuration files fits into the MSI patching scenario. Naively, I assumed I could update the product installer to include a new component containing the new sql to be run, via a SqlScript element. Then, using Pyro to produce the patch, I'd get this new component as a difference between the baseline product installer and the current installer. The resulting patch might then be used to execute the new sql script during the patching process. This fails giving the following error in the log. Action start 11:04:08: InstallSqlData. InstallSqlData: Error 0x80070006: failed to get size of stream InstallSqlData: Error 0x80070006: failed to read SqlScripts table On a related point, I use XmlFile to configure properties within various xml config files, this works fine during the installation of the product, however now I wish to patch those files, specifically adding new options. Again, I naively update the sourcefile adding the new options, build a new installer and use Pyro to create the patch. When I look at the results I expected to see the changed file with the new options, I don't, instead I see the original, unpatched file. If I omit the XmlFile elements that are update the file during the install, I then see the newly added options in the installed config file once patched (with the install time updates from XmlFile removed). Alternatively if I add additional XmlFile elements to the current installer, that specifically add the new options (i.e. util:XmlFile Action='createElement'...) I see the new config options in the resulting, patched file. However, the sourcefile is now out of sync with the what is actually installed, whic h feels wrong. Does anyone have any experience with either of these two patching scenarios? Thanks for any info, ~Colin. _________________________________________________________________ Invite your Facebook friends to chat on Messenger http://clk.atdmt.com/UKM/go/101719649/direct/01/ ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
