Re: [WiX-users] WixExitEarlyWithSuccess not working for me
Well I'm having some new problems. This is my current code: http://pastie.org/4002610 http://pastie.org/4001980 1- To do a minor upgrade I'm just changing just the version last digit: *?define ProductVersion = 1.0.6.1?* * *to *?define ProductVersion = 1.0.6.2?* but doing just that, when i run the new installer i get that error: http://img526.imageshack.us/img526/8471/screenshot20120523at457.png so i suppose I'm missing something or this update is pointless. 2- To do a major upgrade, I changed both version second digit and product guid *?define ProductVersion = 1.0.5.0? ... Product Name='My Update' Id='e986a90a-d4a6-4cf2-9545-efdbfa55a39f' UpgradeCode=$(var.ProductUpgradeCode) Language='1033' Codepage='1252' Version=$(var.ProductVersion) Manufacturer='International Syst'?* to *?define ProductVersion = 1.0.6.0? ... Product Name='My Update' Id='aa5594c7-bd55-4ab3-a213-84bc39b1d827' UpgradeCode=$(var.ProductUpgradeCode) Language='1033' Codepage='1252' Version=$(var.ProductVersion) Manufacturer='International Syst'?* but on the new installation, it doesn't offer to close the running application anymore. When i accept to launch on the end of the installation, i have 2 instances of the app running at once. (I'm using *DialogRef Id=FilesInUse /* for that) 3- How can i ask to launch the application after a Repair? It asks to close it but doesn't launch it automatically. 4- I changed the code that was using *WixExitEarlyWithSuccess* with *MajorUpgrade DowngradeErrorMessage=Can’t downgrade. / *as they seem to have the same effect. Can i use that to prevent reinstalling the same version? Any other way to do that? Thanks in advance 2012/5/30 Luis Tiago C Eterovick lu...@syst.com.br Well, i couldn't make it work the way i wanted. Can anyone help me with this? I want the application to simply end with success as soon as possible with a custom message, if it finds the same or newer version. In my context, this is the best practice, even though it sounds strange. 2012/5/24 Luis Tiago C Eterovick lu...@syst.com.br Thanks! I'll give it a try. About the condition, this update app is coming together with other different apps, so this installer is probably going to run more than once, if the user has 2 or more of these apps. I want to avoid even the repair/unninstall screen because the user doesn't know about this and it would be better if this process was invisible to him since I can't assure if he's able to guess whats happening, that's why i need to exit with success as soon as possible when the same version is already installed. 2012/5/23 Heath Stewart clubs...@gmail.com Having the same UpgradeCode (upgrade ID) isn't actually a requirement - just that your new version has the older version's UpgradeCode in the Upgrade table (Upgrade element). That's key - having the same UpgradeCode doesn't mean you have an upgrade. In fact, if you don't schedule RemoveExistingProducts you don't really have an upgrade either - just related packages. But you're on the right track: the ProductVersion and ProductCode have to change for your UpgradeVersion/@ActionProperty to be set, which in turn triggers the custom action. On Wed, May 23, 2012 at 3:36 PM, Chris Lord chris.l...@atterotech.com wrote: Hi Luis (1) Are you attempting a major upgrade or a minor one? If its a major upgrade then your upgrade MSI should have an identical upgrade ID but a different product ID and a different version from the original MSI. I cant tell if the product code has changed or not as you have only posted one set of code. However, if you dont change the product ID and the system tries a major upgrade, you will get this. Also, check your version number. In your WXS it's listed as 1.0.0.58. When FindRelatedProducts is called to look for versions to upgrade, it only checks the first 3 parts of the version number and the fourth number is ALWAYS ignored. If you have only bumped the version from say from 1.0.0.57 in the original MSI to 1.0.0.58 in the upgrade MSI, FindRelatedProducts still sees these as being the same. (2) I dont know the answer to this one but as a guess, I think you may need to digitally sign your MSI for the publisher to be shown. (3) I am not sure what your intention was by including the condition but Windows Installer will detect if your application is already installed and prevent a re-install by itself. The third screen shot shows this happening with the only option to repair or remove. Was there a reason for trying to stop the user installing the update again? Chris Lord Attero Tech, LLC 1315 Directors Row, Suite 107 Fort Wayne, IN 46808 Ph: 260-496-9668 ext. 377, Fax 260-496-9879 email: chris.l...@atterotech.com Confidentiality Notice: This message is intended solely for the use of the addressees shown above. It may contain information that is privileged, confidential and/or exempt from disclosure under applicable
Re: [WiX-users] WixExitEarlyWithSuccess not working for me
Well, i couldn't make it work the way i wanted. Can anyone help me with this? I want the application to simply end with success as soon as possible with a custom message, if it finds the same or newer version. In my context, this is the best practice, even though it sounds strange. 2012/5/24 Luis Tiago C Eterovick lu...@syst.com.br Thanks! I'll give it a try. About the condition, this update app is coming together with other different apps, so this installer is probably going to run more than once, if the user has 2 or more of these apps. I want to avoid even the repair/unninstall screen because the user doesn't know about this and it would be better if this process was invisible to him since I can't assure if he's able to guess whats happening, that's why i need to exit with success as soon as possible when the same version is already installed. 2012/5/23 Heath Stewart clubs...@gmail.com Having the same UpgradeCode (upgrade ID) isn't actually a requirement - just that your new version has the older version's UpgradeCode in the Upgrade table (Upgrade element). That's key - having the same UpgradeCode doesn't mean you have an upgrade. In fact, if you don't schedule RemoveExistingProducts you don't really have an upgrade either - just related packages. But you're on the right track: the ProductVersion and ProductCode have to change for your UpgradeVersion/@ActionProperty to be set, which in turn triggers the custom action. On Wed, May 23, 2012 at 3:36 PM, Chris Lord chris.l...@atterotech.com wrote: Hi Luis (1) Are you attempting a major upgrade or a minor one? If its a major upgrade then your upgrade MSI should have an identical upgrade ID but a different product ID and a different version from the original MSI. I cant tell if the product code has changed or not as you have only posted one set of code. However, if you dont change the product ID and the system tries a major upgrade, you will get this. Also, check your version number. In your WXS it's listed as 1.0.0.58. When FindRelatedProducts is called to look for versions to upgrade, it only checks the first 3 parts of the version number and the fourth number is ALWAYS ignored. If you have only bumped the version from say from 1.0.0.57 in the original MSI to 1.0.0.58 in the upgrade MSI, FindRelatedProducts still sees these as being the same. (2) I dont know the answer to this one but as a guess, I think you may need to digitally sign your MSI for the publisher to be shown. (3) I am not sure what your intention was by including the condition but Windows Installer will detect if your application is already installed and prevent a re-install by itself. The third screen shot shows this happening with the only option to repair or remove. Was there a reason for trying to stop the user installing the update again? Chris Lord Attero Tech, LLC 1315 Directors Row, Suite 107 Fort Wayne, IN 46808 Ph: 260-496-9668 ext. 377, Fax 260-496-9879 email: chris.l...@atterotech.com Confidentiality Notice: This message is intended solely for the use of the addressees shown above. It may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are hereby notified that the copying, use or distribution of any information or materials transmitted in or with this message is strictly prohibited. If you received this message by mistake, please immediately contact me at (260) 496-9668 x 377 or chris.l...@atterotech.com and destroy the original message. Thank you. -Original Message- From: Luis Tiago C Eterovick [mailto:lu...@syst.com.br] Sent: Wednesday, May 23, 2012 4:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WixExitEarlyWithSuccess not working for me Hello, I have 3 problems that i need some help. 1- Considering my App is installed and i generate a new installer with a newer version, if i open it i get this screen: http://img526.imageshack.us/img526/8471/screenshot20120523at457.png 2- After removing the installed App in Control Panel, i run the new installer. It installs everything smoothly but when asking for permission, it doesn't show the manufacturer name. Do i have to set it more than once? Because it's set on Product and Package fields: http://img96.imageshack.us/img96/4702/screenshot20120523at458.png 3- After the new version is installed, i run the installer again, and it was supposed to find the same version installed and exit with success, but it doesn't seem to do anything different from the regular proceeding: http://img23.imageshack.us/img23/4702/screenshot20120523at458.png I'm currently using: CustomActionRef Id=WixExitEarlyWithSuccess / Upgrade Id=$(var.ProductUpgradeCode) UpgradeVersion Minimum=$(var.ProductVersion) OnlyDetect=yes Property
[WiX-users] WixExitEarlyWithSuccess not working for me
Hello, I have 3 problems that i need some help. 1- Considering my App is installed and i generate a new installer with a newer version, if i open it i get this screen: http://img526.imageshack.us/img526/8471/screenshot20120523at457.png 2- After removing the installed App in Control Panel, i run the new installer. It installs everything smoothly but when asking for permission, it doesn't show the manufacturer name. Do i have to set it more than once? Because it's set on Product and Package fields: http://img96.imageshack.us/img96/4702/screenshot20120523at458.png 3- After the new version is installed, i run the installer again, and it was supposed to find the same version installed and exit with success, but it doesn't seem to do anything different from the regular proceeding: http://img23.imageshack.us/img23/4702/screenshot20120523at458.png I'm currently using: CustomActionRef Id=WixExitEarlyWithSuccess / Upgrade Id=$(var.ProductUpgradeCode) UpgradeVersion Minimum=$(var.ProductVersion) OnlyDetect=yes Property=NEWERVERSIONDETECTED / /Upgrade Condition Message=Metasys Update is already installed. This installation is being skipped.NOT NEWERVERSIONDETECTED/Condition and this is the full code: http://pastie.org/3957432 Can anyone help me on these points? Any other hint is appreciated. It's my first time using WiX. Thanks in advance -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] File language and CreateFolder usage
Hello, I've just started with WiX and I'm building my first installer. 1- My first problem is about the .dll being installed with: *Component Id='HelperLibrary1' Guid='fbb3fdc0-0682-48a9-8486-631a1e426e47' * * File Id='HelperDLL1' Name='QtCore4.dll' DiskId='1' Source='C:\Qt\2010.05\qt\bin\QtCore4.dll' KeyPath='yes' /* */Component* which gives me warning: *C:\Users\luist\Desktop\musetup\musetup.wxs(34) : warning LGHT1076 : ICE60: The file HelperDLL1 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.* * * How can i prevent that? Why would i need a language for a .dll file? 2- I also need to know the correct way to create the folder that one of my files is being installed, with: *Directory Id=TARGETDIR Name=SourceDir* * ...* * Directory Id=MyDir Name=MyDir/* */Directory* * * *...* * * *DirectoryRef Id=MyDir* * Component Id='Info' Guid='2dcf7776-e5b9-4d1c-ae9c-78e392efec56'* *File Id='InfoFile' Name='myfile.info' DiskId='1' Source='C:\Users\luist\Desktop\MUInstaller\myfile.info' KeyPath='yes' /* * /Component* */DirectoryRef* I tried using CreateFolder but i guess i didn't use it correctly. Can anyone help me? Thanks in advance -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Moving to another installer
Hello, I'm currently using another installer and having some problems when running it twice (yes it's going to run 2 or more times). Looking for a new one. Can i configure WiX to: - Check if I'm installed the same version, or a higher version? - Give options to force reinstall, skip/exit installer (preferred) when it's the same version? - Ask for user to close a running app (or force close it) so the exe can be replaced for a new one (in case of a higher version)? Thanks in advance -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
