Re: [WiX-users] WCF server cannot connect to the remote database.
Too much drama in this group for me. See ya all :) Sent by Android via Nexus One On Feb 14, 2011 9:09 PM, Christopher Painter chr...@deploymentengineering.com wrote: Well, Evil Genius, you clearly no more about installs then myself and Rob Mensching combined so knock yourself. --- 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: Rune Moberg jjfl...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, February 14, 2011 7:44:06 AM Subject: Re: [WiX-users] WCF server cannot connect to the remote database. On Mon, Feb 14, 2011 at 1:10 PM, Christopher Painter chr...@deploymentengineering.com wrote: For #4, you are right, it is simple. I can do it in one line of XML in WiX and let MSI handle the details. For developers I can do it in 1 line of .BAT using the SC command.And, no, your InstallUtil code will not be better. Using batch files, adding yet another way of registering your services? Which is exactly the solution I'm replacing. Why not use srvany.exe while you're at it..? Code duplication is frowned upon. Having service registration information residing in batch files means you've done just that. Not to mention that admins familiar with the '-i' command line switch have to deal with your services in yet a different way. Cristopher, I am not saying that my solution is the optimal. What I am saying is that ServiceInstall does not fully satisfy the KISS principle. Adding batchfiles to handle the other cases is a big clue as to why it isn't satisfactory. Some improvements here would be most helpful, at least to me! It is useful with a unified way of registering an executable as a service. _Currently_, the .Net platform offers the Installer framework. It has its downsides as you point out, but... It is still the lesser of the evils presented so far! A more metainfo-based replacement could perhaps solve the remaining issues? -- Rune -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Folder permissions - change on upgrade/reinstall
Hiya,
I am currently setting permissions using:
Component Id=CreateFolderX Guid={7F6E8A54-A7BA-4065-BB4A-672E12719F9C}
CreateFolder Directory=XDIRECTORY
Permission User=Everyone ChangePermission=yes
GenericAll=yes /
/CreateFolder
/Component
Now... This code sets the permissions when the folder is created, but that
only happens on a fresh install. For current users, the folder already
exists and is not deleted with the RemoveExistingProducts code as there are
files that persist across installs.
I need a way to make the installer check and repair the permissions if
necessary during a reinstall/upgrade, but can't seem to find anything in the
docs to help... Anyone got a idea?
Thanks much,
Dave
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters
Ok guys, I found my issue, and its fixed. I took the tutorials too literally it seems. In every tutorial I have seen the Product Code was set to * I read in one that doing do automatically generated a new product code on each build. Apparently that is not the case, as when I manually added and changed the product code to a new GUID for each build the problem was fixed. I found that by reading the link Pally added to this thread... so thank you very much! Hopefully I will learn enough about Windows Installer to be as helpful to someone later :) Dave On Tue, Jan 25, 2011 at 2:44 PM, Blair os...@live.com wrote: Make sure the line that is used to detect older versions is NOT marked OnlyDetect. I've seen people do that. -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Monday, January 24, 2011 3:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters If David is getting multiple entries in ARP then the upgrade is not finding the previous version. All other things being equal (and implemented correctly), a cross-context upgrade won't work, per-user install upgrading to per-system or vice versa. Phil Wilson -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Monday, January 24, 2011 4:03 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters This works pretty well for me when shipping internal beta builds http://blogs.msdn.com/b/johnls/archive/2006/11/13/how-to-upgrade-software-wi th-a-windows-installer-package.aspx No bootstrapper required. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** 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: David Borneman [mailto:d...@servingtulsa.com] Sent: 24 January 2011 07:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters Actually, let me back up a second. The whole reason I created this question is that the RemoveExistingProducts action is just not working. The upgrade succeeds, but it leaves multiple entries in the Add/Remove Programs CP. I went thru literally dozens of attempts with different settings for Upgrade/RemoveExisting from information I found on various help websites, with the result most of the time being the dreaded Another version of this program is already installed..., and the others that succeeded leaving multiple entries in the control panel. I am pretty sure there is something very simple wrong, I just can't seem to find it. :/ Dave On Mon, Jan 24, 2011 at 2:21 PM, Blair os...@live.com wrote: That requires a bootstrapper that knows something about Windows Installer. Even for minor changes a Major Upgrade is often the simplest option. If you are trying to minimize the changes during upgrades, consider a Major Upgrade with late scheduling of RemoveExistingProducts. -Blair -Original Message- From: David Borneman [mailto:d...@servingtulsa.com] Sent: Saturday, January 22, 2011 5:24 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters Hiya all, Hope this messages goes thru... Tis my very first mailing list message :) I am getting the dreaded Another version of this application is already installed blah when trying to install a newer version of our software. Its a minor upgrade, but it is in Beta so we prefer a reinstall, at least for now, like a Major Install. I found a suggestion that I create a bootstrapper for this, which I did (and took the opportunity to add in some pre-requisites), but currently the bootstrapper is simply executing the MSI as it was downloaded, without any other parameters (as is correct since I have not configured it otherwise lol). What i need to know how to do, and cant figure out for the life of me, is how to instead execute the following: msiexec /i OurInstallerApp.msi REINSTALL=ALL REINSTALLMODE=vomus Any kick in the right direction would be greatly appreciated! David Borneman Senior Developer -- -- -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev
Re: [WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters
Actually, let me back up a second. The whole reason I created this question is that the RemoveExistingProducts action is just not working. The upgrade succeeds, but it leaves multiple entries in the Add/Remove Programs CP. I went thru literally dozens of attempts with different settings for Upgrade/RemoveExisting from information I found on various help websites, with the result most of the time being the dreaded Another version of this program is already installed..., and the others that succeeded leaving multiple entries in the control panel. I am pretty sure there is something very simple wrong, I just can't seem to find it. :/ Dave On Mon, Jan 24, 2011 at 2:21 PM, Blair os...@live.com wrote: That requires a bootstrapper that knows something about Windows Installer. Even for minor changes a Major Upgrade is often the simplest option. If you are trying to minimize the changes during upgrades, consider a Major Upgrade with late scheduling of RemoveExistingProducts. -Blair -Original Message- From: David Borneman [mailto:d...@servingtulsa.com] Sent: Saturday, January 22, 2011 5:24 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters Hiya all, Hope this messages goes thru... Tis my very first mailing list message :) I am getting the dreaded Another version of this application is already installed blah when trying to install a newer version of our software. Its a minor upgrade, but it is in Beta so we prefer a reinstall, at least for now, like a Major Install. I found a suggestion that I create a bootstrapper for this, which I did (and took the opportunity to add in some pre-requisites), but currently the bootstrapper is simply executing the MSI as it was downloaded, without any other parameters (as is correct since I have not configured it otherwise lol). What i need to know how to do, and cant figure out for the life of me, is how to instead execute the following: msiexec /i OurInstallerApp.msi REINSTALL=ALL REINSTALLMODE=vomus Any kick in the right direction would be greatly appreciated! David Borneman Senior Developer -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question about creating a bootstrap to launch the MSI with Reinstall parameters
Hiya all, Hope this messages goes thru... Tis my very first mailing list message :) I am getting the dreaded Another version of this application is already installed blah when trying to install a newer version of our software. Its a minor upgrade, but it is in Beta so we prefer a reinstall, at least for now, like a Major Install. I found a suggestion that I create a bootstrapper for this, which I did (and took the opportunity to add in some pre-requisites), but currently the bootstrapper is simply executing the MSI as it was downloaded, without any other parameters (as is correct since I have not configured it otherwise lol). What i need to know how to do, and cant figure out for the life of me, is how to instead execute the following: msiexec /i OurInstallerApp.msi REINSTALL=ALL REINSTALLMODE=vomus Any kick in the right direction would be greatly appreciated! David Borneman Senior Developer -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question about executing a reinstall parameter to the MSI thru a bootstrapper
Hiya all, Hope this messages goes thru... Tis my very first mailing list message :) I am getting the dreaded Another version of this application is already installed blah when trying to install a newer version of our software. Its a minor upgrade, but it is in Beta so we prefer a reinstall, at least for now, like a Major Upgrade. I found a suggestion that I create a bootstrapper for this, which I did (and took the opportunity to add in some pre-requisites), but currently the bootstrapper is simply executing the MSI as it was downloaded, without any other parameters (as is correct since I have not configured it otherwise lol). What i need to know how to do, and cant figure out for the life of me, is how to instead execute the following: msiexec /i OurInstallerApp.msi REINSTALL=ALL REINSTALLMODE=vomus Any kick in the right direction would be greatly appreciated! David Borneman Senior Developer -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
