Re: [WiX-users] WiX force copy file.
How do I mark a file 'versioned' so it will overwrite? Of course other than inserting the RemoveFile as suggested by Chad Petersen. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Umeshj [mailto:umesh_jogle...@hotmail.com] Sent: Thursday, April 14, 2011 2:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Rule for unversioned files is that if a file is modified after creation then it will not be overwritten. This is with the rationale that if a user has modified it then it should be left undisturbed. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-force-copy-file-tp6270161p6271858.html Sent from the wix-users mailing list archive at Nabble.com. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX force copy file.
But won't that affect all files? I just want to overwrite this one file. -Original Message- From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com] Sent: Thursday, April 14, 2011 7:40 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Change REINSTALLMODE property. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, April 14, 2011 4:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. How do I mark a file 'versioned' so it will overwrite? Of course other than inserting the RemoveFile as suggested by Chad Petersen. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Umeshj [mailto:umesh_jogle...@hotmail.com] Sent: Thursday, April 14, 2011 2:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Rule for unversioned files is that if a file is modified after creation then it will not be overwritten. This is with the rationale that if a user has modified it then it should be left undisturbed. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-force-copy-file-tp6270161p6271858.html Sent from the wix-users mailing list archive at Nabble.com. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX force copy file.
From the documentation it seems that DefaultVersion is an arbitrary string. If I set it to 1.0 then somehow WiX keeps track of this version and always overwrites versions that are 1.0? And if in the future I change it to 2.0 it will not overwrite 1.0 with 2.0? Is that how it works? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Thursday, April 14, 2011 8:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. You can version lie, buts its usually not a good idea as the file will get replaced every time the installation is run (it's what installshield does when you click always overwrite). If you really need to do it then you set File@DefaultVersion to a valid file version. Dave -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 14 April 2011 14:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. But won't that affect all files? I just want to overwrite this one file. -Original Message- From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com] Sent: Thursday, April 14, 2011 7:40 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Change REINSTALLMODE property. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, April 14, 2011 4:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. How do I mark a file 'versioned' so it will overwrite? Of course other than inserting the RemoveFile as suggested by Chad Petersen. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Umeshj [mailto:umesh_jogle...@hotmail.com] Sent: Thursday, April 14, 2011 2:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Rule for unversioned files is that if a file is modified after creation then it will not be overwritten. This is with the rationale that if a user has modified it then it should be left undisturbed. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-force-copy- file-tp6270161p6271858.html Sent from the wix-users mailing list archive at Nabble.com. - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ 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
Re: [WiX-users] WiX force copy file.
Part of the problem I believe is that because after the file is installed it is changed with XmlFile tasks so WiX doesn't remove this file on uninstall. The other files (assemblies, etc.) get removed on uninstall so I always get what is in the .msi file. Right now RemoveFile works and maybe that is the solution. Basically I want to change the file and still have it removed as all the other files on uninstall. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Thursday, April 14, 2011 8:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. You can version lie, buts its usually not a good idea as the file will get replaced every time the installation is run (it's what installshield does when you click always overwrite). If you really need to do it then you set File@DefaultVersion to a valid file version. Dave -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 14 April 2011 14:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. But won't that affect all files? I just want to overwrite this one file. -Original Message- From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com] Sent: Thursday, April 14, 2011 7:40 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Change REINSTALLMODE property. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, April 14, 2011 4:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. How do I mark a file 'versioned' so it will overwrite? Of course other than inserting the RemoveFile as suggested by Chad Petersen. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Umeshj [mailto:umesh_jogle...@hotmail.com] Sent: Thursday, April 14, 2011 2:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Rule for unversioned files is that if a file is modified after creation then it will not be overwritten. This is with the rationale that if a user has modified it then it should be left undisturbed. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-force-copy- file-tp6270161p6271858.html Sent from the wix-users mailing list archive at Nabble.com. - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists
Re: [WiX-users] WiX force copy file.
That is a good suggestion. I will try that. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Thursday, April 14, 2011 9:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. Can't you just use XMLFile@PreserveModifiedDate in that case? -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 14 April 2011 15:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. Part of the problem I believe is that because after the file is installed it is changed with XmlFile tasks so WiX doesn't remove this file on uninstall. The other files (assemblies, etc.) get removed on uninstall so I always get what is in the .msi file. Right now RemoveFile works and maybe that is the solution. Basically I want to change the file and still have it removed as all the other files on uninstall. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Thursday, April 14, 2011 8:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. You can version lie, buts its usually not a good idea as the file will get replaced every time the installation is run (it's what installshield does when you click always overwrite). If you really need to do it then you set File@DefaultVersion to a valid file version. Dave -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 14 April 2011 14:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. But won't that affect all files? I just want to overwrite this one file. -Original Message- From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com] Sent: Thursday, April 14, 2011 7:40 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Change REINSTALLMODE property. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, April 14, 2011 4:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. How do I mark a file 'versioned' so it will overwrite? Of course other than inserting the RemoveFile as suggested by Chad Petersen. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Umeshj [mailto:umesh_jogle...@hotmail.com] Sent: Thursday, April 14, 2011 2:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX force copy file. Rule for unversioned files is that if a file is modified after creation then it will not be overwritten. This is with the rationale that if a user has modified it then it should be left undisturbed. 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. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX force copy file.
Here is the situation. I have a configuration file that on installation in release mode I use the XmlFile task to remove a section of the file. In debug I also use XmlFile to modify one of the elements in the file. Is what I am finding is that if I do a release installation followed by a debug installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX force copy file.
The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceAppConfig,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,,VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config;Won't Overwrite;Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. Check a verbose log file and it should say why it is not replacing that file. Typically because it is newer than the file you hope to replace it with. The RemoveFile element can be handy for some of these types of issues. Not positive it's what you'll want, but maybe. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 11:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX force copy file. Here is the situation. I have a configuration file that on installation in release mode I use the XmlFile task to remove a section of the file. In debug I also use XmlFile to modify one of the elements in the file. Is what I am finding is that if I do a release installation followed by a debug installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
Re: [WiX-users] WiX force copy file.
I add RemoveFile but on uninstall. This gave me the same error do you usually specify both for this kind of situation? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. Yes. I run into this with text files (xml mostly) a lot. RemoveFile can go under the same Component as the File element. That's the way I always use it. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,, VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522 490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config; Won't Overwrite; Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. Check a verbose log file and it should say why it is not replacing that file. Typically because it is newer than the file you hope to replace it with. The RemoveFile element can be handy for some of these types of issues. Not positive it's what you'll want, but maybe. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 11:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX force copy file. Here is the situation. I have a configuration file that on installation in release mode I use the XmlFile task to remove a section of the file. In debug I also use XmlFile to modify one of the elements in the file. Is what I am finding is that if I do a release installation followed by a debug installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010
Re: [WiX-users] WiX force copy file.
I cannot seem to get RemoveFile to work. Here is my latest attempt: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ RemoveFile Id=WpfAppConfig0 Name=[WPFINSTALLDIR]app.Config On=both/ . !-- -- ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? . /Component I still get the error message in the log below. The error message indicates that the file is unversioned but modified. Hopefullly applying RemoveFile correctly will let me essentially overwrite the file. Thank you. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,, VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522 490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config; Won't Overwrite; Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Light OutOfMemory?
I am using 3.5. Where is the .pbs? I was not able to find a file with that suffix in the installation directory. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 30, 2011 9:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Light OutOfMemory? What version of the WiX toolset are you running? If its a recent build, can you drop the .pdbs next to light and get a full callstack? On Tue, Mar 29, 2011 at 9:38 AM, Kevin Burton kev...@buyseasons.com wrote: I have WiX integrated with Visual Studio so the installer is built when the solution is built. Right now I consistently run into the error from light: Error 1 Exception of type 'System.OutOfMemoryException' was thrown.light.exe 0 1 BsiServices I saw back in 2006 there was a suggestion to split the project into multiple .wxs files. I have done some splitting but I still get this error. Any other suggestions? -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Light OutOfMemory?
OK. You meant .pdb's. Is there a distribution of those or do I need to build WiX from source? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 30, 2011 9:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Light OutOfMemory? What version of the WiX toolset are you running? If its a recent build, can you drop the .pdbs next to light and get a full callstack? On Tue, Mar 29, 2011 at 9:38 AM, Kevin Burton kev...@buyseasons.com wrote: I have WiX integrated with Visual Studio so the installer is built when the solution is built. Right now I consistently run into the error from light: Error 1 Exception of type 'System.OutOfMemoryException' was thrown.light.exe 0 1 BsiServices I saw back in 2006 there was a suggestion to split the project into multiple .wxs files. I have done some splitting but I still get this error. Any other suggestions? -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Light OutOfMemory?
I issue the build from Visual Studio and it is undoubtedly calling MSBuild under the covers but I am not sure how to coerce Visual Studio to give up more information than the information about the exception. Also it doesn't happen all the time. I could get this exception with Visual Studio and then go to a command prompt and invoke MSBuild manually and it would work. Most of the time just restarting Visual Studio causes it to work. It is one of those intermittent errors that when they happen you wish you had the debug information available because repeating it does not cause the error. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, March 31, 2011 9:09 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Light OutOfMemory? Which version of WiX v3.5? We didn't start dropping .pdbs until WiX v3.6. However, actually, I don't think we need them. Is there more information available about the crash? There should be a callstack. If you're running from MSBuild, turn logging on, the stack trace should be in there. On Thu, Mar 31, 2011 at 6:00 AM, Kevin Burton kev...@buyseasons.com wrote: I am using 3.5. Where is the .pbs? I was not able to find a file with that suffix in the installation directory. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 30, 2011 9:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Light OutOfMemory? What version of the WiX toolset are you running? If its a recent build, can you drop the .pdbs next to light and get a full callstack? On Tue, Mar 29, 2011 at 9:38 AM, Kevin Burton kev...@buyseasons.com wrote: I have WiX integrated with Visual Studio so the installer is built when the solution is built. Right now I consistently run into the error from light: Error 1 Exception of type 'System.OutOfMemoryException' was thrown.light.exe 0 1 BsiServices I saw back in 2006 there was a suggestion to split the project into multiple .wxs files. I have done some splitting but I still get this error. Any other suggestions? -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users
Re: [WiX-users] Light OutOfMemory?
Thank you I will try this.
Two questions. What is the 'verbosity' needed to show a 'light' stack trace?
What is the difference between output verbosity and log file verbosity?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, March 31, 2011 10:12 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Light OutOfMemory?
I'm using Visual Studio 2010. Your mileage may vary with other versions of
Visual Studio.
1. Click the Tools menu
2. Select the Options... menu item
3. Expand the Projects and Solutions category in the left pane 4. Select the
Build and Run option
The right side of the Options dialog should now contain two options at the
bottom:
* MSBuild project build output verbosity: Minimal
* MSBuild project build log file verbosity: Minimal
Try setting these options to Detailed. There is a Diagnostic verbosity but in
my opinion the formatting makes it difficult to follow what's going on.
I don't know where Visual Studio put the build log file or whether there's
another setting to make Visual Studio create one so changing the MSBuild
project build log file verbosity setting might not provide any value.
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 31, 2011 7:32 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Light OutOfMemory?
I issue the build from Visual Studio and it is undoubtedly calling
MSBuild under the covers but I am not sure how to coerce Visual Studio
to give up more information than the information about the exception.
Also it doesn't happen all the time. I could get this exception with
Visual Studio and then go to a command prompt and invoke MSBuild
manually and it would work. Most of the time just restarting Visual
Studio causes it to work. It is one of those intermittent errors that
when they happen you wish you had the debug information available because
repeating it does not cause the error.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, March 31, 2011 9:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Light OutOfMemory?
Which version of WiX v3.5? We didn't start dropping .pdbs until WiX v3.6.
However, actually, I don't think we need them. Is there more
information available about the crash? There should be a callstack. If
you're running from MSBuild, turn logging on, the stack trace should be in
there.
On Thu, Mar 31, 2011 at 6:00 AM, Kevin Burton kev...@buyseasons.com
wrote:
I am using 3.5. Where is the .pbs? I was not able to find a file
with that suffix in the installation directory.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, March 30, 2011 9:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Light OutOfMemory?
What version of the WiX toolset are you running? If its a recent
build, can you drop the .pdbs next to light and get a full callstack?
On Tue, Mar 29, 2011 at 9:38 AM, Kevin Burton
kev...@buyseasons.com
wrote:
I have WiX integrated with Visual Studio so the installer is built
when the solution is built. Right now I consistently run into the
error
from light:
Error 1 Exception of type 'System.OutOfMemoryException'
was thrown.light.exe 0 1
BsiServices
I saw back in 2006 there was a suggestion to split the project
into multiple .wxs files. I have done some splitting but I still
get this
error.
Any other suggestions?
--
--
--
Enable your software for Intel(R) Active Management
Technology to meet the growing manageability and security demands
of your customers. Businesses are taking advantage of Intel(R)
vPro
(TM) technology - will your software be a part of the solution?
Download the Intel(R) Manageability Checker today!
http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
virtually, Rob Mensching - http://RobMensching.com LLC
[WiX-users] Light OutOfMemory?
I have WiX integrated with Visual Studio so the installer is built when the solution is built. Right now I consistently run into the error from light: Error 1 Exception of type 'System.OutOfMemoryException' was thrown.light.exe 0 1 BsiServices I saw back in 2006 there was a suggestion to split the project into multiple .wxs files. I have done some splitting but I still get this error. Any other suggestions? -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installer for version 3.6.1511.0 fails.
This doesn't help you with your problem but I have had a lot of weird problems
since installing IE9. I am not sure how to rollback but I think I need to.
-Original Message-
From: du...@doutel.com [mailto:du...@doutel.com]
Sent: Thursday, March 17, 2011 12:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installer for version 3.6.1511.0 fails.
I note that someone is having the same problem with the 1504 build. I'm
wondering if perhaps the IE9 RTW is the culprit. These are the relevant lines
from the log file (I've attached the full log file, as well):
[1F08:18C4][2011-03-16T12:43:31.835-05:00]: Caching executable from:
C:\Users\Duane\Desktop\Wix36.exe to: C:\ProgramData\Package
Cache\{25c5ee84-5c84-498b-bfe1-381a2bc52edd}\WiX36.exe
[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Download engine HTTP 200 HEAD to
http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi
http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi
[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Error 0x80072f76: Failed to get
size of download.
[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Error 0x80072f76: Failed to get
size and time for URL:
http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi
http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi
[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Error 0x80072f76: Failed to
download URL using wininet.
[1990:0B0C][2011-03-16T12:43:31.966-05:00]: Error 0x80072f76: Failed to
download payload.
[1990:0B0C][2011-03-16T12:43:31.966-05:00]: Error 0x80072f76: Failed to acquire
payload.
[1990:0B0C][2011-03-16T12:43:31.967-05:00]: Error 0x80072f76: Failed to cache
packages.
[1F08:18C4][2011-03-16T12:43:31.967-05:00]: Removing cached bundle:
{25c5ee84-5c84-498b-bfe1-381a2bc52edd}, from path: C:\ProgramData\Package
Cache\{25c5ee84-5c84-498b-bfe1-381a2bc52edd}
[1990:0B0C][2011-03-16T12:43:31.970-05:00]: Apply complete, result:
0x80072f76 restart: No
[1990:0B0C][2011-03-16T12:43:35.830-05:00]: Shutting down, exit code: 0x0
Best!
Duane T. Doutel
Doutel Software Services, LLC
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ServiceInstall failure?
I have an open ticket with Microsoft. They pointed me to http://support.microsoft.com/kb/264678/EN-US/ I have been unable to get to this link with IE 9. They also said: When AD calls are made with a UPN name(username@Domainname) with a bad password, an initial attempt is made with Kerberos, and when that fails, an additional attempt is made with NTLM. That is why we are seeing the badpwdcount attribute being incremented twice. When the same attempt is made with a SAM account name (domain\username), only one attempt with Kerberos is made, and consequentially the badpwdcount attribute is being incremented once. My experience with our domain controller is that the count gets bumped to 3 when using UPN and 2 when using SAM. Anyway apparently the way a user name is specified does matter and using UPN formatted user name can more readily cause an account lockout. The link mentions this as a problem with Windows 2000 server domain controllers. I am using a Windows 2008 server R2 domain controller which seems to exhibit different characteristics and it hasn’t been fixed there yet. Just FYI. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 3:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? There are no builtin facilities in Windows Installer nor WiX for checking credentials. You'll need to write a custom action to perform this type of check but beware that this check will likely count against the lockout count if the credentials are incorrect. In other words, if you use the custom action as part of the UI and the user tries to validate wrong credentials enough times, then they will still lockout the account. If the MSI does not have a UI then you'll have to run the installer multiple times with invalid credentials to lockout the account with a validation custom action. In other words, I don’t think you can truly avoid the problem as it depends on how many times a user specifies invalid credentials. I have never seen a single installation attempt lockout an account. In my experience the service fails to start and causes the installation to fail initiating a rollback. No lockout. If I attempt the installation enough times with invalid credentials, then I'll see a lockout which is the same as above. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.comhttp://www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 09, 2011 4:58 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? I consistently get an account lockout when I install and start a service with the wrong credentials. Everything works fine when the proper credentials are supplied. I know it is probably an FAQ but I am just beginning. What facilities are available for checking the credentials and rolling back the installation *before* starting the service? I see recently, someone else queried about conditionally installing/starting a service but I was not able to follow the conclusion. Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- 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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re
Re: [WiX-users] C# Custom Action questions
It is currently set to 'Any CPU'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 8:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I think I hit something like that. Try building the CA with AnyCPU as the
platform rather than 32/64
I have got that error when I forgot the public on the class, though
Regards
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 12:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Thank you Michael,
I tried
public class CustomActions
{
private static int checkCount = 1;
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
With the same error in the log file. It seems more related to the assembly than
the scope of the method. The error indicates that the DLL could not be run. I
don't think the process has even gotten to the point of looking for the member.
Something is wrong with the DLL that is produced by the custom action project
that is integrated with Visual Studio.
I think the issue that the .msi is compiled and built (and the CA project) in a
32 bit environment and the .msi is installing to a 64-bit environment may be
more of the problem. Although I am not sure how to tackle it if this is indeed
the problem. So the binary element that makes the DLL part of the .msi maybe
needs to know about the bited-ness: of the source and target. All of this is
just supposition as I am a relative beginner with WiX.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 5:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Hi Kevin
I think your error that it can't find the CA is in the call
private static bool CheckCredentials
Should be something like:
[CustomAction]
public static ActionResult CheckCredentials(Session session)
The class it is a member of also needs to be public.
Note you need to get the credentials out of properties.
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I hear you. Where I work there is already considerable skepticism on the
installation package and anything that goes wrong is blamed on the installation
so when the installation locks the account (because of bad credentials) there
is a call to not use any deployment and go to copy deployment because of
similar mysteries. If I can avoid the account lockout with a CA that would
sweep the problem under the rug at least for now.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Thursday, March 10, 2011 4:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
When I was at Continental Airlines we had an application that I had to
distribute where the service used a service account. For reasons never
determined ( aka damn service account ) something out there would periodically
lock the account and group policy would have it unlocked 10 minutes later.
One of the worst dependencies I ever had to take. It wasn't fun.
---
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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thu, March 10, 2011 4:11:13 PM
Subject: Re: [WiX-users] C# Custom Action questions
Phil and I both mentioned the potential problem. Run your code for invalid
credentials more than once. Try it about 4-12 times (as suggested by Phil). The
flow for the custom action is the following:
User enters credentials in dialog.
Dialog asks custom action to validate.
Dialog checks validation result property letting the user know if the password
was valid or invalid.
Suppose that a user incorrect enters invalid credentials enough times... At my
work you only get 3 tries! On the third validation the account is locked out
and the fourth and future attempts all fail regardless of whether the
credentials were valid or not.
Running it once is not enough to verify that this is not the case.
Now, to address the CA running to begin with... Check that the CA
Re: [WiX-users] C# Custom Action questions
Along these same lines I tried building the CA project setting the target as
x64 just to see if this made a difference. I did get a different error message
but it still didn't work:
MSI (s) (60:B0) [08:07:23:200]: Doing action: CA_CheckCredentials
MSI (s) (60:B0) [08:07:23:200]: Note: 1: 2205 2: 3: ActionText
Action ended 8:07:23: InstallInitialize. Return value 1.
MSI (s) (60:4C) [08:07:23:215]: Invoking remote custom action. DLL:
D:\WINDOWS\Installer\MSI463.tmp, Entrypoint: CheckCredentials
MSI (s) (60:80) [08:07:23:215]: Generating random cookie.
MSI (s) (60:80) [08:07:23:231]: Created Custom Action Server with PID 5428
(0x1534).
MSI (s) (60:C0) [08:07:23:278]: Running as a service.
MSI (s) (60:C0) [08:07:23:278]: Hello, I'm your 32bit Impersonated custom
action server.
Action start 8:07:23: CA_CheckCredentials.
SFXCA: Extracting custom action to temporary directory:
D:\WINDOWS\Installer\MSI463.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action
BrainCustomActions!BuySeasons.BsiServices.Install.CustomActions.CheckCredentials
Error: could not load custom action class
BuySeasons.BsiServices.Install.CustomActions from assembly: BrainCustomActions
System.BadImageFormatException: Could not load file or assembly
'BrainCustomActions' or one of its dependencies. An attempt was made to load a
program with an incorrect format.
File name: 'BrainCustomActions'
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String
codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint,
StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean
forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String
codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint,
StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean
forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName
assemblyRef, Evidence assemblySecurity, StackCrawlMark stackMark, Boolean
forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString,
Evidence assemblySecurity, StackCrawlMark stackMark, Boolean forIntrospection)
at System.AppDomain.Load(String assemblyString)
at
Microsoft.Deployment.WindowsInstaller.CustomActionProxy.GetCustomActionMethod(Session
session, String assemblyName, String className, String methodName)
When I specify x86 as the target I get the familiar error:
MSI (s) (2C:74) [08:24:38:753]: Doing action: CA_CheckCredentials
MSI (s) (2C:74) [08:24:38:753]: Note: 1: 2205 2: 3: ActionText
Action ended 8:24:38: InstallInitialize. Return value 1.
MSI (s) (2C:90) [08:24:38:753]: Invoking remote custom action. DLL:
D:\WINDOWS\Installer\MSI465.tmp, Entrypoint: CheckCredentials
MSI (s) (2C:88) [08:24:38:753]: Generating random cookie.
MSI (s) (2C:88) [08:24:38:768]: Created Custom Action Server with PID 5368
(0x14F8).
MSI (s) (2C:F4) [08:24:38:815]: Running as a service.
MSI (s) (2C:F4) [08:24:38:815]: Hello, I'm your 32bit Impersonated custom
action server.
MSI (s) (2C:74) [08:24:38:878]: Note: 1: 1723 2: CA_CheckCredentials 3:
CheckCredentials 4: D:\WINDOWS\Installer\MSI465.tmp
Action start 8:24:38: CA_CheckCredentials.
MSI (s) (2C:74) [08:24:38:878]: Product: Bsi WebServices -- Error 1723. There
is a problem with this Windows Installer package. A DLL required for this
install to complete could not be run. Contact your support personnel or package
vendor. Action CA_CheckCredentials, entry: CheckCredentials, library:
D:\WINDOWS\Installer\MSI465.tmp
Error 1723. There is a problem with this Windows Installer package. A DLL
required for this install to complete could not be run. Contact your support
personnel or package vendor. Action CA_CheckCredentials, entry:
CheckCredentials, library: D:\WINDOWS\Installer\MSI465.tmp
MSI (s) (2C:74) [08:24:38:878]: Machine policy value 'DisableRollback' is 0
MSI (s) (2C:74) [08:24:38:878]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
3: 2
Action ended 8:24:38: CA_CheckCredentials. Return value 3.
MSI (s) (2C:74) [08:24:38:878]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
3: 2
MSI (s) (2C:74) [08:24:38:878]: No System Restore sequence number for this
installation.
MSI (s) (2C:74) [08:24:38:878]: Unlocking Server
Action ended 8:24:38: INSTALL. Return value 3.
Property(S): UpgradeCode = {529189FE-FD0E-44FF-8DA6-B4FB5CC7A78B}
Property(S): COMMERCESERVERINSTALLDIR = D:\Program Files (x86)\Microsoft
Commerce Server 2007\
Property(S): NETFRAMEWORK35 = #1
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 8:49 PM
To: General
Re: [WiX-users] C# Custom Action questions
I am sorry I had inadvertently set the binary tag to the DLL *not* the CA.dll
so with the compile target of the CA specifically set to x86 (*not* Any CPU)
the CA is called correctly. Thank you.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 8:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I think I hit something like that. Try building the CA with AnyCPU as the
platform rather than 32/64
I have got that error when I forgot the public on the class, though
Regards
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 12:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Thank you Michael,
I tried
public class CustomActions
{
private static int checkCount = 1;
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
With the same error in the log file. It seems more related to the assembly than
the scope of the method. The error indicates that the DLL could not be run. I
don't think the process has even gotten to the point of looking for the member.
Something is wrong with the DLL that is produced by the custom action project
that is integrated with Visual Studio.
I think the issue that the .msi is compiled and built (and the CA project) in a
32 bit environment and the .msi is installing to a 64-bit environment may be
more of the problem. Although I am not sure how to tackle it if this is indeed
the problem. So the binary element that makes the DLL part of the .msi maybe
needs to know about the bited-ness: of the source and target. All of this is
just supposition as I am a relative beginner with WiX.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 5:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Hi Kevin
I think your error that it can't find the CA is in the call
private static bool CheckCredentials
Should be something like:
[CustomAction]
public static ActionResult CheckCredentials(Session session)
The class it is a member of also needs to be public.
Note you need to get the credentials out of properties.
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I hear you. Where I work there is already considerable skepticism on the
installation package and anything that goes wrong is blamed on the installation
so when the installation locks the account (because of bad credentials) there
is a call to not use any deployment and go to copy deployment because of
similar mysteries. If I can avoid the account lockout with a CA that would
sweep the problem under the rug at least for now.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Thursday, March 10, 2011 4:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
When I was at Continental Airlines we had an application that I had to
distribute where the service used a service account. For reasons never
determined ( aka damn service account ) something out there would periodically
lock the account and group policy would have it unlocked 10 minutes later.
One of the worst dependencies I ever had to take. It wasn't fun.
---
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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thu, March 10, 2011 4:11:13 PM
Subject: Re: [WiX-users] C# Custom Action questions
Phil and I both mentioned the potential problem. Run your code for invalid
credentials more than once. Try it about 4-12 times (as suggested by Phil). The
flow for the custom action is the following:
User enters credentials in dialog.
Dialog asks custom action to validate.
Dialog checks validation result property letting the user know if the password
was valid or invalid.
Suppose that a user incorrect enters invalid credentials enough times... At my
work you only get 3 tries! On the third validation the account is locked out
and the fourth and future attempts all fail regardless of whether
Re: [WiX-users] C# Custom Action questions
Actually I had to specifically compile to x86 before it would work even though
the target machine was x64. If I specifically compiled to x64 I received a
warning on the build machine what I am compiling to something different than
the current machine but when it came to running on the target machine that was
actually x64 I ran into another error but it didn't work. The takeaway is that
no matter what the target machine is you have to set x86 when building the .NET
CA. Any CPU doesn't work and x64 doesn't seem to work either.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Friday, March 11, 2011 10:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
FYI: The DLL is a .NET assembly. The CA.dll is a native C++ assembly that
is responsible for setting up the .NET environment needed to run the .NET
DLL. As you found out, you need the bitness of the CA.dll to match the
target machine.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, March 11, 2011 6:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I am sorry I had inadvertently set the binary tag to the DLL *not*
the CA.dll so with the compile target of the CA specifically set to
x86 (*not* Any CPU) the CA is called correctly. Thank you.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 8:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I think I hit something like that. Try building the CA with AnyCPU as
the platform rather than 32/64
I have got that error when I forgot the public on the class, though
Regards
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 12:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Thank you Michael,
I tried
public class CustomActions
{
private static int checkCount = 1;
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
With the same error in the log file. It seems more related to the
assembly than the scope of the method. The error indicates that the
DLL could not be run. I don't think the process has even gotten to
the point of looking for the member. Something is wrong with the DLL
that is produced by the custom action project that is integrated with Visual
Studio.
I think the issue that the .msi is compiled and built (and the CA
project) in a
32 bit environment and the .msi is installing to a 64-bit environment
may be more of the problem. Although I am not sure how to tackle it if
this is indeed the problem. So the binary element that makes the DLL
part of the .msi maybe needs to know about the bited-ness: of the
source and target. All of this is just supposition as I am a relative
beginner with WiX.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 5:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Hi Kevin
I think your error that it can't find the CA is in the call
private static bool CheckCredentials
Should be something like:
[CustomAction]
public static ActionResult CheckCredentials(Session session)
The class it is a member of also needs to be public.
Note you need to get the credentials out of properties.
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I hear you. Where I work there is already considerable skepticism on
the installation package and anything that goes wrong is blamed on the
installation so when the installation locks the account (because of
bad
credentials) there is a call to not use any deployment and go to copy
deployment because of similar mysteries. If I can avoid the account
lockout with a CA that would sweep the problem under the rug at least for now.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From
Re: [WiX-users] C# Custom Action questions
It looks like the only difference is the fact that I am compiling on an x86
platform. Have you tried 'Any CPU'? When I specify 'Any CPU' the CA will not
run with the afore mentioned errors in the log.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Friday, March 11, 2011 1:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I have a custom action library written in C# with Debug and Release
configurations and only x64 platform. I manually removed the x86 platform. Here
are snippets from the .csproj:
PropertyGroup
Configuration Condition= '$(Configuration)' == '' Debug/Configuration
Platform Condition= '$(Platform)' == '' x64/Platform
...
/PropertyGroup
PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Debug|x64'
...
/PropertyGroup
PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Release|x64'
...
/PropertyGroup
This builds fine without problems (no warnings and no errors) but I am building
on a x64 machine. I have not built this project on a x86 machine. The custom
action dll also performs flawlessly when used in an installer.
The toolset works for me as I would expect it to work. If you are targeting
x64, then you should build x64 custom actions. The project templates provided
by the toolset work pretty good. There's really no need to write your own build
scripts (I have a feeling you might be writing your own build scripts).
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, March 11, 2011 10:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Actually I had to specifically compile to x86 before it would work
even though the target machine was x64. If I specifically compiled to
x64 I received a warning on the build machine what I am compiling to
something different than the current machine but when it came to
running on the target machine that was actually x64 I ran into another
error but it didn't work. The takeaway is that no matter what the
target machine is you have to set x86 when building the .NET CA. Any
CPU doesn't work and x64 doesn't seem to work either.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Friday, March 11, 2011 10:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
FYI: The DLL is a .NET assembly. The CA.dll is a native C++
assembly that is responsible for setting up the .NET environment
needed to run the .NET DLL. As you found out, you need the bitness
of the CA.dll to match the target machine.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, March 11, 2011 6:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I am sorry I had inadvertently set the binary tag to the DLL *not*
the CA.dll so with the compile target of the CA specifically set to
x86 (*not* Any CPU) the CA is called correctly. Thank you.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 8:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I think I hit something like that. Try building the CA with AnyCPU
as the platform rather than 32/64
I have got that error when I forgot the public on the class, though
Regards
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 12:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Thank you Michael,
I tried
public class CustomActions
{
private static int checkCount = 1;
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
With the same error in the log file. It seems more related to the
assembly than the scope of the method
Re: [WiX-users] C# Custom Action questions
So cross-compile fails (trying to compile x64 on a x86 machine) but running x86 on an x64 platform works and 'Any CPU' fails. At least that has been my experience. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, March 11, 2011 2:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions I have not tried AnyCPU as that only makes sense if the C++ CA dll is written in C++/CLI. The native C++ CA dll is very likely not written in C++/CLI because we are trying to avoid loading up a .NET assembly to begin with. So... we need to specify an actual platform (x86 or x64). I have not built my project on a 32-bit machine so I don't know if there are any warnings generated but I would not expect to see any errors. My psychic guess is that any warnings generated are trying to tell you that the DLL was cross compiled and will not work on the build machine. Such a warning would make sense and be expected. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, March 11, 2011 11:29 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions It looks like the only difference is the fact that I am compiling on an x86 platform. Have you tried 'Any CPU'? When I specify 'Any CPU' the CA will not run with the afore mentioned errors in the log. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, March 11, 2011 1:00 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions I have a custom action library written in C# with Debug and Release configurations and only x64 platform. I manually removed the x86 platform. Here are snippets from the .csproj: PropertyGroup Configuration Condition= '$(Configuration)' == '' Debug/Configuration Platform Condition= '$(Platform)' == '' x64/Platform ... /PropertyGroup PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Debug|x64' ... /PropertyGroup PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Release|x64' ... /PropertyGroup This builds fine without problems (no warnings and no errors) but I am building on a x64 machine. I have not built this project on a x86 machine. The custom action dll also performs flawlessly when used in an installer. The toolset works for me as I would expect it to work. If you are targeting x64, then you should build x64 custom actions. The project templates provided by the toolset work pretty good. There's really no need to write your own build scripts (I have a feeling you might be writing your own build scripts). Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, March 11, 2011 10:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions Actually I had to specifically compile to x86 before it would work even though the target machine was x64. If I specifically compiled to x64 I received a warning on the build machine what I am compiling to something different than the current machine but when it came to running on the target machine that was actually x64 I ran into another error but it didn't work. The takeaway is that no matter what the target machine is you have to set x86 when building the .NET CA. Any CPU doesn't work and x64 doesn't seem to work either. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, March 11, 2011 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions FYI: The DLL is a .NET assembly. The CA.dll is a native C++ assembly that is responsible for setting up the .NET environment needed to run the .NET DLL. As you found out, you need the bitness of the CA.dll to match the target machine. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com
[WiX-users] Tracker.exe??
I am getting a warning WixUI_Mondo.wxs WpfComponents.wxs Product.Generated.wxs Link: C:\Program Files\Windows Installer XML v3.5\bin\Light.exe -cultures:null -ext C:\Program Files\Windows Installer XML v3.5\bin\\WixNetFxExtension.dll -ex t C:\Program Files\Windows Installer XML v3.5\bin\\WixUIExtension.dll -ext C:\Program Files\Windows Installer XML v3.5\bin\\WixUtilExtension.dll -out C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServices\bi n\Release\BsiServices.msi -pdbout C:\Projects\BuySeasonsIT\Source\Brain\Trunk \BuyseasonsServices\BsiServices\bin\Release\BsiServices.wixpdb obj\Release\Fo lders.wixobj obj\Release\Product.wixobj obj\Release\ProductSetup.wixobj obj\R elease\Properties.wixobj obj\Release\ServiceComponents.wixobj obj\Release\Wix UI_Mondo.wixobj obj\Release\WpfComponents.wixobj obj\Release\Product.Generate d.wixobj Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ I have never seen this before. Any one see errors related to 'Tracker.exe'? -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Tracker.exe??
So what have I done wrong that causes this error? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, March 11, 2011 4:13 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Tracker.exe?? http://lmgtfy.com/?q=wix+tracker.exe Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, March 11, 2011 1:33 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Tracker.exe?? I am getting a warning WixUI_Mondo.wxs WpfComponents.wxs Product.Generated.wxs Link: C:\Program Files\Windows Installer XML v3.5\bin\Light.exe -cultures:null - ext C:\Program Files\Windows Installer XML v3.5\bin\\WixNetFxExtension.dll -ex t C:\Program Files\Windows Installer XML v3.5\bin\\WixUIExtension.dll - ext C:\Program Files\Windows Installer XML v3.5\bin\\WixUtilExtension.dll - out C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServ i ces\bi n\Release\BsiServices.msi -pdbout C:\Projects\BuySeasonsIT\Source\Brain\Trunk \BuyseasonsServices\BsiServices\bin\Release\BsiServices.wixpdb obj\Release\Fo lders.wixobj obj\Release\Product.wixobj obj\Release\ProductSetup.wixobj obj\R elease\Properties.wixobj obj\Release\ServiceComponents.wixobj obj\Release\Wix UI_Mondo.wixobj obj\Release\WpfComponents.wixobj obj\Release\Product.Generate d.wixobj Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ I have never seen this before. Any one see errors related to 'Tracker.exe'? -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Tracker.exe??
I tried linking and it gave me this error on Tracker.exe not finding a response file. I was hoping that someone on this list has seen this error and as a reasonable workaround. The first link had responses like: Sometimes A/V has been known to interfere with build tools. Have you tried exempting the C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp directory from real-time scanning? I don't even know what A/V is an I am certainly not doing any real-time scanning. The second link was a duplicate of the first. The third link was a different format for the first but a duplicate. The fourth link was still another duplicate of the first. The fifth link ended in the conclusion from Microsoft Thanks for reporting the issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided. After that I stopped reading. I don't have forever to look through all these links. Just an I don't know or haven't seen it would be fine. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, March 11, 2011 4:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Tracker.exe?? *SIGH* Did you read any of the links that showed up in the search? ... Really, I would expect more from a Senior Software Engineer. I'm not a senior anything... but I know how to search and read. If you can post additional information as to what you learned, what you tried, and how it worked or didn't work, then I'll consider helping again. This has gotten quite ridiculous. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, March 11, 2011 2:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Tracker.exe?? So what have I done wrong that causes this error? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, March 11, 2011 4:13 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Tracker.exe?? http://lmgtfy.com/?q=wix+tracker.exe Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, March 11, 2011 1:33 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Tracker.exe?? I am getting a warning WixUI_Mondo.wxs WpfComponents.wxs Product.Generated.wxs Link: C:\Program Files\Windows Installer XML v3.5\bin\Light.exe -cultures:null - ext C:\Program Files\Windows Installer XML v3.5\bin\\WixNetFxExtension.dll -ex t C:\Program Files\Windows Installer XML v3.5\bin\\WixUIExtension.dll - ext C:\Program Files\Windows Installer XML v3.5\bin\\WixUtilExtension.dll - out C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServ i ces\bi n\Release\BsiServices.msi -pdbout C:\Projects\BuySeasonsIT\Source\Brain\Trunk \BuyseasonsServices\BsiServices\bin\Release\BsiServices.wixpdb obj\Release\Fo lders.wixobj obj\Release\Product.wixobj obj\Release\ProductSetup.wixobj obj\R elease\Properties.wixobj obj\Release\ServiceComponents.wixobj obj\Release\Wix UI_Mondo.wixobj obj\Release\WpfComponents.wixobj obj\Release\Product.Generate d.wixobj Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ I have never seen this before. Any one see errors related to 'Tracker.exe'? -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d
[WiX-users] msiexec returning before it is done?
This isn't a WiX question directly but hopefully someone will have some experience they would be willing to share. I am using PowerShell to run msiexec on a remote machine. Right after I zip up the files that were installed. But PowerShell is too quick because by the time I get to executing the zip command the files have not been copied. I don't see any arguments to msiexec that say wait until you are done. Is there any indicator that tells me that msiexec is done? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Tracker.exe??
Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Michael_A [mailto:mcl...@fullarmor.com] Sent: Friday, March 11, 2011 4:50 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Tracker.exe?? Try this Go to VS2010 - Team Explorer - Builds - EDIT BUILD DEFINITION - PROCESS - ADVANCED - MS BUILD ARGUMENTS and add /p:TrackFileAccess=false - then SAVE. Kevin Burton wrote: I am getting a warning WixUI_Mondo.wxs WpfComponents.wxs Product.Generated.wxs Link: C:\Program Files\Windows Installer XML v3.5\bin\Light.exe -cultures:null -ext C:\Program Files\Windows Installer XML v3.5\bin\\WixNetFxExtension.dll -ex t C:\Program Files\Windows Installer XML v3.5\bin\\WixUIExtension.dll -ext C:\Program Files\Windows Installer XML v3.5\bin\\WixUtilExtension.dll -out C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServices\bi n\Release\BsiServices.msi -pdbout C:\Projects\BuySeasonsIT\Source\Brain\Trunk \BuyseasonsServices\BsiServices\bin\Release\BsiServices.wixpdb obj\Release\Fo lders.wixobj obj\Release\Product.wixobj obj\Release\ProductSetup.wixobj obj\R elease\Properties.wixobj obj\Release\ServiceComponents.wixobj obj\Release\Wix UI_Mondo.wixobj obj\Release\WpfComponents.wixobj obj\Release\Product.Generate d.wixobj Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ 03b94238f4844598baddb8c2c1a53fc5.rsp not found. Tracker.exe: Response file C:\Documents and Settings\kevinb\Local Settings\Temp\ I have never seen this before. Any one see errors related to 'Tracker.exe'? -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Tracker-exe-tp6162943p6163168.html Sent from the wix-users mailing list archive at Nabble.com. -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] C# Custom Action questions
How does the custom action indicate that the credentials are incorrect? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com] Sent: Wednesday, March 09, 2011 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You shouldn't return failure if the credentials are incorrect, if you do so you will get this error. been there, done that... On Mar 10, 2011 6:34 AM, Kevin Burton kev...@buyseasons.com wrote: I read that. Which of the four rules is this violating? I made the warning go away by making the C# CA 'immediate' thus I don't have to have another custom action to remember the property. So I have CustomAction Id=CA_CheckCredentials Return=check Execute=immediate BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And the schedule InstallExecuteSequence Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence But in the verbose log I get: MSI (s) (B8:9C) [22:04:26:415]: Note: 1: 1723 2: CA_CheckCredentials 3: CheckCredentials 4: D:\WINDOWS\Installer\MSI410.tmp Action start 22:04:26: CA_CheckCredentials. MSI (s) (B8:9C) [22:04:26:415]: Product: Bsi WebServices -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp The error says that the DLL cannot be run. Why? I believe I have followed the instructions for writing a managed CA to the tee (though there seems to be some disagreement between the online tutorial http://www.tramontana.co.hu/wix/ and this book). -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 5:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions ICE63 - http://msdn.microsoft.com/en-us/library/aa369008.aspx Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 09, 2011 2:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions I think I have solved this problem. The CA was scheduled in the InstallExecuteSequence and was marked as 'deferred' so I created the following 'Custom Data'. CustomAction Id=SetProperty Property=CA_CheckCredentials Value=[SERVICEUSER],[SERVICEPASSWORD] / CustomAction Id=CA_CheckCredentials Return=check Execute=deferred BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And scheduled it like (I am trying to follow the instructions on page 133 of 'WiX: A Developer's Guide to Windows Installer XML' by Nick Ramirez) InstallExecuteSequence Custom Action=SetProperty Before=CA_CheckCredentials / Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence Now I get the ICE warning: warning LGHT1076: ICE63: Some action falls between InstallInitialize and RemoveExistingProducts. Is this a bad warning? I don't completely understand why this scheduling is bad. I would like to know that the credentials are bad *before* the existing products are removed. If I look at the .msi generated with Orca I see that in the InstallExecuteSequence table InstallInitialize 1500 SetProperty 1501 CA_CheckCredentials 1502 RemoveExistingProducts 1503 This seems like a valid sequence to me but I am obviously missing something as the warning is there for a purpose. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, March 09, 2011 3:30 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions If I had to guess you calling this CA as a ControlEvent off a Dialog / Control in your UI sequence. Am I correct? If so, it's a known issue that Msi lacks the ability to process messages in this scenario. The workaround is to set a dummy property to see a PROPERTY CHANGED message in the log file where the value is the data you are trying to log. Chris --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves
Re: [WiX-users] C# Custom Action questions
This error occurs when the credentials are correct. I don't get the message that the CA is being called (the first line in the code) so I don't think the CA is even being called. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com] Sent: Wednesday, March 09, 2011 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You shouldn't return failure if the credentials are incorrect, if you do so you will get this error. been there, done that... On Mar 10, 2011 6:34 AM, Kevin Burton kev...@buyseasons.com wrote: I read that. Which of the four rules is this violating? I made the warning go away by making the C# CA 'immediate' thus I don't have to have another custom action to remember the property. So I have CustomAction Id=CA_CheckCredentials Return=check Execute=immediate BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And the schedule InstallExecuteSequence Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence But in the verbose log I get: MSI (s) (B8:9C) [22:04:26:415]: Note: 1: 1723 2: CA_CheckCredentials 3: CheckCredentials 4: D:\WINDOWS\Installer\MSI410.tmp Action start 22:04:26: CA_CheckCredentials. MSI (s) (B8:9C) [22:04:26:415]: Product: Bsi WebServices -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp The error says that the DLL cannot be run. Why? I believe I have followed the instructions for writing a managed CA to the tee (though there seems to be some disagreement between the online tutorial http://www.tramontana.co.hu/wix/ and this book). -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 5:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions ICE63 - http://msdn.microsoft.com/en-us/library/aa369008.aspx Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 09, 2011 2:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions I think I have solved this problem. The CA was scheduled in the InstallExecuteSequence and was marked as 'deferred' so I created the following 'Custom Data'. CustomAction Id=SetProperty Property=CA_CheckCredentials Value=[SERVICEUSER],[SERVICEPASSWORD] / CustomAction Id=CA_CheckCredentials Return=check Execute=deferred BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And scheduled it like (I am trying to follow the instructions on page 133 of 'WiX: A Developer's Guide to Windows Installer XML' by Nick Ramirez) InstallExecuteSequence Custom Action=SetProperty Before=CA_CheckCredentials / Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence Now I get the ICE warning: warning LGHT1076: ICE63: Some action falls between InstallInitialize and RemoveExistingProducts. Is this a bad warning? I don't completely understand why this scheduling is bad. I would like to know that the credentials are bad *before* the existing products are removed. If I look at the .msi generated with Orca I see that in the InstallExecuteSequence table InstallInitialize 1500 SetProperty 1501 CA_CheckCredentials 1502 RemoveExistingProducts 1503 This seems like a valid sequence to me but I am obviously missing something as the warning is there for a purpose. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, March 09, 2011 3:30 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions If I had to guess you calling this CA as a ControlEvent off a Dialog / Control in your UI sequence. Am I correct? If so, it's a known issue that Msi lacks the ability to process messages in this scenario. The workaround is to set a dummy property to see a PROPERTY CHANGED message in the log file where the value is the data you are trying to log. Chris --- Christopher Painter, Author
Re: [WiX-users] C# Custom Action questions
So CA's always return Success. What are the other return values used for? Thank you. For the tip. The problem that I am having now is that it doesn't appear that the CA is getting called. I look in the log and see the message indicated earlier in this thread indicating that the DLL could not be run. Any idea for this? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 10, 2011 12:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You'll want to set a property that can be checked in a condition. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 6:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions How does the custom action indicate that the credentials are incorrect? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com] Sent: Wednesday, March 09, 2011 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You shouldn't return failure if the credentials are incorrect, if you do so you will get this error. been there, done that... On Mar 10, 2011 6:34 AM, Kevin Burton kev...@buyseasons.com wrote: I read that. Which of the four rules is this violating? I made the warning go away by making the C# CA 'immediate' thus I don't have to have another custom action to remember the property. So I have CustomAction Id=CA_CheckCredentials Return=check Execute=immediate BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And the schedule InstallExecuteSequence Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence But in the verbose log I get: MSI (s) (B8:9C) [22:04:26:415]: Note: 1: 1723 2: CA_CheckCredentials 3: CheckCredentials 4: D:\WINDOWS\Installer\MSI410.tmp Action start 22:04:26: CA_CheckCredentials. MSI (s) (B8:9C) [22:04:26:415]: Product: Bsi WebServices -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp The error says that the DLL cannot be run. Why? I believe I have followed the instructions for writing a managed CA to the tee (though there seems to be some disagreement between the online tutorial http://www.tramontana.co.hu/wix/ and this book). -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 5:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions ICE63 - http://msdn.microsoft.com/en-us/library/aa369008.aspx Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 09, 2011 2:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions I think I have solved this problem. The CA was scheduled in the InstallExecuteSequence and was marked as 'deferred' so I created the following 'Custom Data'. CustomAction Id=SetProperty Property=CA_CheckCredentials Value=[SERVICEUSER],[SERVICEPASSWORD] / CustomAction Id=CA_CheckCredentials Return=check Execute=deferred BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And scheduled it like (I am trying to follow the instructions on page 133 of 'WiX: A Developer's Guide to Windows Installer XML' by Nick Ramirez) InstallExecuteSequence Custom Action=SetProperty Before=CA_CheckCredentials / Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence Now I get the ICE warning: warning LGHT1076: ICE63: Some action falls between
Re: [WiX-users] C# Custom Action questions
But I want the install to fail. If it continues with the wrong credentials it will try to start services with the wrong credentials. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Thursday, March 10, 2011 12:32 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions In cases where you checking things like credentials you want the actions to return success so that the install does not fail. As it was said, you set a property if the call succeeded and check if the property is set. You use the other return values in those cases where you want the install to fail and not continue such as when updating configuration files or updating anything that the application requires to function. The basic rule of thumb is when in the UI sequence always have actions return success and set properties use in conditional statements. When the action is called in the Execute sequence and it is critical to the success of the product always have the action return success or failure so that the install can fail and rollback when needed. Mat Skildum -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions So CA's always return Success. What are the other return values used for? Thank you. For the tip. The problem that I am having now is that it doesn't appear that the CA is getting called. I look in the log and see the message indicated earlier in this thread indicating that the DLL could not be run. Any idea for this? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 10, 2011 12:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You'll want to set a property that can be checked in a condition. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 6:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions How does the custom action indicate that the credentials are incorrect? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com] Sent: Wednesday, March 09, 2011 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You shouldn't return failure if the credentials are incorrect, if you do so you will get this error. been there, done that... On Mar 10, 2011 6:34 AM, Kevin Burton kev...@buyseasons.com wrote: I read that. Which of the four rules is this violating? I made the warning go away by making the C# CA 'immediate' thus I don't have to have another custom action to remember the property. So I have CustomAction Id=CA_CheckCredentials Return=check Execute=immediate BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And the schedule InstallExecuteSequence Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence But in the verbose log I get: MSI (s) (B8:9C) [22:04:26:415]: Note: 1: 1723 2: CA_CheckCredentials 3: CheckCredentials 4: D:\WINDOWS\Installer\MSI410.tmp Action start 22:04:26: CA_CheckCredentials. MSI (s) (B8:9C) [22:04:26:415]: Product: Bsi WebServices -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp The error says that the DLL cannot be run. Why? I believe I have followed the instructions for writing a managed CA to the tee (though there seems to be some disagreement between the online tutorial http://www.tramontana.co.hu/wix/ and this book). -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09
Re: [WiX-users] C# Custom Action questions
I am not sure what you mean by square one? Are you saying that the checking of credentials that are invalid will throw an exception that is not caught? First I have to solve the problem that I don't think the CA is being called as evidenced by the snippet of log I posted earlier. Unless the log entry will be suppressed by an exception. But the entry on the log indicates that the DLL could not be run so I don't think I am even getting to that point. Also I get the same error (DLL could not be run) whether I supply the correct credentials or incorrect ones. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Thursday, March 10, 2011 1:55 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions and Kevin, are you sure that attempting to validate will not be treated as a logon failure and put you back to square one? User account validation schemes are often nothing more than an attempt to log on with the supplied credentials. That might be what Context.ValidateCredentials does - I don't know enough about AD and AdsOpenObject() to know if that's what happens. Reflector seems to indicate that's the underlying Win32 call. Phil Wilson -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Thursday, March 10, 2011 10:49 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions This is where you use the property that the action set. You do not allow the user off of the dialog until they enter credentials that work and the property is set to the value you expect. This way it is up to the installer to exit the install if they do not have the needed information, but you give them all the chances they need to get it right. Mat Skildum -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 12:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions But I want the install to fail. If it continues with the wrong credentials it will try to start services with the wrong credentials. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Thursday, March 10, 2011 12:32 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions In cases where you checking things like credentials you want the actions to return success so that the install does not fail. As it was said, you set a property if the call succeeded and check if the property is set. You use the other return values in those cases where you want the install to fail and not continue such as when updating configuration files or updating anything that the application requires to function. The basic rule of thumb is when in the UI sequence always have actions return success and set properties use in conditional statements. When the action is called in the Execute sequence and it is critical to the success of the product always have the action return success or failure so that the install can fail and rollback when needed. Mat Skildum -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions So CA's always return Success. What are the other return values used for? Thank you. For the tip. The problem that I am having now is that it doesn't appear that the CA is getting called. I look in the log and see the message indicated earlier in this thread indicating that the DLL could not be run. Any idea for this? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 10, 2011 12:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You'll want to set a property that can be checked in a condition. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 6:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions How does the custom action indicate that the credentials are incorrect? Kevin Burton Senior Software Engineer BUYSEASONS
Re: [WiX-users] C# Custom Action questions
I can check the credentials with invalid credentials and then I am able to
check the credentials using valid credentials. No lock out. Here is the code:
private static bool CheckCredentials(string userName, string password)
{
bool valid = false;
using(PrincipalContext context = new
PrincipalContext(ContextType.Domain, ASGARD))
{
valid = context.ValidateCredentials(userName, password);
}
return valid;
}
static void Main(string[] args)
{
Debug.WriteLine(string.Format(Credentials are {0},
CheckCredentials(user, invalid)));
Debug.WriteLine(string.Format(Credentials are {0},
CheckCredentials(user, valid)));
}
And the output is:
Credentials are False
Credentials are True
Now my biggest problem is that the CA is not getting called.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, March 10, 2011 3:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
This is nothing to do with exceptions. I'm telling you that the act of
verifying credentials is a flavor of logon, and that a failure to verify may
be treated in exactly the same way as when your service tries to log on with
invalid credentials. In other words you can write a bunch of code that tries to
verify an account and the result is that the account gets locked out, or you
can just go back to what you were doing before and have the service logon
failure cause account lockout. I'm saying that this is what you may end up
with, so all your code gives you very little advantage, if any at all.
You should run your custom action in a program and use an invalid password. Try
it a dozen times and see if the account gets locked out.
Phil Wilson
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 10, 2011 12:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I am not sure what you mean by square one? Are you saying that the checking
of credentials that are invalid will throw an exception that is not caught?
First I have to solve the problem that I don't think the CA is being called as
evidenced by the snippet of log I posted earlier. Unless the log entry will be
suppressed by an exception. But the entry on the log indicates that the DLL
could not be run so I don't think I am even getting to that point. Also I get
the same error (DLL could not be run) whether I supply the correct credentials
or incorrect ones.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, March 10, 2011 1:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
and Kevin, are you sure that attempting to validate will not be
treated as a logon failure and put you back to square one? User account
validation schemes are often nothing more than an attempt to log on with the
supplied credentials. That might be what Context.ValidateCredentials does - I
don't know enough about AD and AdsOpenObject() to know if that's what happens.
Reflector seems to indicate that's the underlying Win32 call.
Phil Wilson
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Thursday, March 10, 2011 10:49 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
This is where you use the property that the action set. You do not allow the
user off of the dialog until they enter credentials that work and the property
is set to the value you expect. This way it is up to the installer to exit the
install if they do not have the needed information, but you give them all the
chances they need to get it right.
Mat Skildum
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 10, 2011 12:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
But I want the install to fail. If it continues with the wrong credentials it
will try to start services with the wrong credentials.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Thursday, March 10, 2011 12:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
In cases where you checking things like credentials you want the actions to
return success
Re: [WiX-users] C# Custom Action questions
The same is true here running the validation with invalid credentials 3 or more
times locks the account out. So the user will not get that many tries I will
fail the installation after the first invalid entry. But this is to avoid the
situation where installing and starting the service just once causes the
account to be locked out if invalid credentials are entered.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, March 10, 2011 4:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Phil and I both mentioned the potential problem. Run your code for invalid
credentials more than once. Try it about 4-12 times (as suggested by Phil). The
flow for the custom action is the following:
User enters credentials in dialog.
Dialog asks custom action to validate.
Dialog checks validation result property letting the user know if the password
was valid or invalid.
Suppose that a user incorrect enters invalid credentials enough times... At my
work you only get 3 tries! On the third validation the account is locked out
and the fourth and future attempts all fail regardless of whether the
credentials were valid or not.
Running it once is not enough to verify that this is not the case.
Now, to address the CA running to begin with... Check that the CA is getting
compiled with the correct bitness as required by the target platform. In other
words, are you compiling a 64-bit CA and trying to call it on a 32-bit machine
or vice versa?
If you can post a minimal reproduction (wix source, CA source, etc) of the CA
running problem I can try to reproduce it on my end.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 10, 2011 1:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I can check the credentials with invalid credentials and then I am
able to check the credentials using valid credentials. No lock out. Here is
the code:
private static bool CheckCredentials(string userName, string password)
{
bool valid = false;
using(PrincipalContext context = new
PrincipalContext(ContextType.Domain, ASGARD))
{
valid = context.ValidateCredentials(userName, password);
}
return valid;
}
static void Main(string[] args)
{
Debug.WriteLine(string.Format(Credentials are {0},
CheckCredentials(user, invalid)));
Debug.WriteLine(string.Format(Credentials are {0},
CheckCredentials(user, valid)));
}
And the output is:
Credentials are False
Credentials are True
Now my biggest problem is that the CA is not getting called.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, March 10, 2011 3:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
This is nothing to do with exceptions. I'm telling you that the act of
verifying credentials is a flavor of logon, and that a failure to
verify may be treated in exactly the same way as when your service
tries to log on with invalid credentials. In other words you can write
a bunch of code that tries to verify an account and the result is that
the account gets locked out, or you can just go back to what you were
doing before and have the service logon failure cause account lockout.
I'm saying that this is what you may end up with, so all your code gives you
very little advantage, if any at all.
You should run your custom action in a program and use an invalid password.
Try it a dozen times and see if the account gets locked out.
Phil Wilson
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 10, 2011 12:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I am not sure what you mean by square one? Are you saying that the
checking of credentials that are invalid will throw an exception that
is not caught?
First I have to solve the problem that I don't think the CA is being
called as evidenced by the snippet of log I posted earlier. Unless the
log entry will be suppressed by an exception. But the entry on the log
indicates that the DLL could not be run so I don't think I am even
getting to that point. Also I get
Re: [WiX-users] C# Custom Action questions
The CA is compile on a 32 bit machine and installed on a 64 bit machine. Is
that a problem? Will not WoW take care of that? It does for the other
assemblies.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, March 10, 2011 4:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Phil and I both mentioned the potential problem. Run your code for invalid
credentials more than once. Try it about 4-12 times (as suggested by Phil). The
flow for the custom action is the following:
User enters credentials in dialog.
Dialog asks custom action to validate.
Dialog checks validation result property letting the user know if the password
was valid or invalid.
Suppose that a user incorrect enters invalid credentials enough times... At my
work you only get 3 tries! On the third validation the account is locked out
and the fourth and future attempts all fail regardless of whether the
credentials were valid or not.
Running it once is not enough to verify that this is not the case.
Now, to address the CA running to begin with... Check that the CA is getting
compiled with the correct bitness as required by the target platform. In other
words, are you compiling a 64-bit CA and trying to call it on a 32-bit machine
or vice versa?
If you can post a minimal reproduction (wix source, CA source, etc) of the CA
running problem I can try to reproduce it on my end.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 10, 2011 1:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I can check the credentials with invalid credentials and then I am
able to check the credentials using valid credentials. No lock out. Here is
the code:
private static bool CheckCredentials(string userName, string password)
{
bool valid = false;
using(PrincipalContext context = new
PrincipalContext(ContextType.Domain, ASGARD))
{
valid = context.ValidateCredentials(userName, password);
}
return valid;
}
static void Main(string[] args)
{
Debug.WriteLine(string.Format(Credentials are {0},
CheckCredentials(user, invalid)));
Debug.WriteLine(string.Format(Credentials are {0},
CheckCredentials(user, valid)));
}
And the output is:
Credentials are False
Credentials are True
Now my biggest problem is that the CA is not getting called.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, March 10, 2011 3:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
This is nothing to do with exceptions. I'm telling you that the act of
verifying credentials is a flavor of logon, and that a failure to
verify may be treated in exactly the same way as when your service
tries to log on with invalid credentials. In other words you can write
a bunch of code that tries to verify an account and the result is that
the account gets locked out, or you can just go back to what you were
doing before and have the service logon failure cause account lockout.
I'm saying that this is what you may end up with, so all your code gives you
very little advantage, if any at all.
You should run your custom action in a program and use an invalid password.
Try it a dozen times and see if the account gets locked out.
Phil Wilson
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 10, 2011 12:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I am not sure what you mean by square one? Are you saying that the
checking of credentials that are invalid will throw an exception that
is not caught?
First I have to solve the problem that I don't think the CA is being
called as evidenced by the snippet of log I posted earlier. Unless the
log entry will be suppressed by an exception. But the entry on the log
indicates that the DLL could not be run so I don't think I am even
getting to that point. Also I get the same error (DLL could not be
run) whether I supply the correct credentials or incorrect ones.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
Re: [WiX-users] C# Custom Action questions
Thank you Michael,
I tried
public class CustomActions
{
private static int checkCount = 1;
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
With the same error in the log file. It seems more related to the assembly than
the scope of the method. The error indicates that the DLL could not be run. I
don't think the process has even gotten to the point of looking for the member.
Something is wrong with the DLL that is produced by the custom action project
that is integrated with Visual Studio.
I think the issue that the .msi is compiled and built (and the CA project) in a
32 bit environment and the .msi is installing to a 64-bit environment may be
more of the problem. Although I am not sure how to tackle it if this is indeed
the problem. So the binary element that makes the DLL part of the .msi maybe
needs to know about the bited-ness: of the source and target. All of this is
just supposition as I am a relative beginner with WiX.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 5:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
Hi Kevin
I think your error that it can't find the CA is in the call
private static bool CheckCredentials
Should be something like:
[CustomAction]
public static ActionResult CheckCredentials(Session session)
The class it is a member of also needs to be public.
Note you need to get the credentials out of properties.
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I hear you. Where I work there is already considerable skepticism on the
installation package and anything that goes wrong is blamed on the installation
so when the installation locks the account (because of bad credentials) there
is a call to not use any deployment and go to copy deployment because of
similar mysteries. If I can avoid the account lockout with a CA that would
sweep the problem under the rug at least for now.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Thursday, March 10, 2011 4:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
When I was at Continental Airlines we had an application that I had to
distribute where the service used a service account. For reasons never
determined ( aka damn service account ) something out there would periodically
lock the account and group policy would have it unlocked 10 minutes later.
One of the worst dependencies I ever had to take. It wasn't fun.
---
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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thu, March 10, 2011 4:11:13 PM
Subject: Re: [WiX-users] C# Custom Action questions
Phil and I both mentioned the potential problem. Run your code for invalid
credentials more than once. Try it about 4-12 times (as suggested by Phil). The
flow for the custom action is the following:
User enters credentials in dialog.
Dialog asks custom action to validate.
Dialog checks validation result property letting the user know if the password
was valid or invalid.
Suppose that a user incorrect enters invalid credentials enough times... At my
work you only get 3 tries! On the third validation the account is locked out
and the fourth and future attempts all fail regardless of whether the
credentials were valid or not.
Running it once is not enough to verify that this is not the case.
Now, to address the CA running to begin with... Check that the CA is getting
compiled with the correct bitness as required by the target platform. In other
words, are you compiling a 64-bit CA and trying to call it on a 32-bit machine
or vice versa?
If you can post a minimal reproduction (wix source, CA source, etc) of the CA
running problem I can try to reproduce it on my end.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, March 10, 2011 1:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
I can check the credentials with invalid
Re: [WiX-users] ServiceInstall failure?
I consistently get an account lockout when I install and start a service with the wrong credentials. Everything works fine when the proper credentials are supplied. I know it is probably an FAQ but I am just beginning. What facilities are available for checking the credentials and rolling back the installation *before* starting the service? I see recently, someone else queried about conditionally installing/starting a service but I was not able to follow the conclusion. Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- 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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, January 28, 2011 10:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? Since it is so basic can you envision a situation where it would cause an account lockout? By basic what is the underlying implementation being used? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, January 28, 2011 7:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? The built in service install of the Windows Installer is pretty basic. One of the few standard actions I've seriously considered replacing with a custom action. On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton kev...@buyseasons.comwrote: It seems that the default behavior for this code ServiceInstall Id=BsiServiceInstall DisplayName=BsiServices Host Name=ServiceExeFile Description=Windows Service host for Bsi Web Services Interactive=no Account=[SERVICEUSER] Password=[SERVICEPASSWORD] ErrorControl=normal Start=demand Type=ownProcess Vital=yes / ServiceControl Id=BsiServiceControl Name=ServiceExeFile Start=install Stop=uninstall Remove=uninstall Wait=yes / Is to repeatedly try, even when the password is invalid, until the account specified is locked out. I was wondering if there was a way to catch the first error and display it to the user. Also I would like to associate some sort of progress bar with the installation and starting of this service. Is there a good reference for this type of function? Thank you. Kevin -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC
[WiX-users] C# Custom Action questions
I have a very simple C# Custom Action that is supposed to verify credentials:
using Microsoft.Deployment.WindowsInstaller;
namespace BuySeasons.BsiServices.Install
{
public class CustomActions
{
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
session.Log(string.Format(Begin CheckCredentials - {0}/{1},
session[SERVICEUSER], session[SERVICEPASSWORD]));
bool valid = false;
using (PrincipalContext context = new
PrincipalContext(ContextType.Domain, ASGARD))
{
valid = context.ValidateCredentials(session[SERVICEUSER],
session[SERVICEPASSWORD]);
}
if(valid)
return ActionResult.Success;
else
return ActionResult.Failure;
}
}
}
It is included in the WiX Product as
Binary Id=CustomActionsDLL
SourceFile=C:\Projects\\bin\$(var.Configuration)\BrainCustomActions.CA.dll
/
CustomAction Id=CA_CheckCredentials
Return=check
Execute=deferred
BinaryKey=CustomActionsDLL
DllEntry=CheckCredentials/
And scheduled as:
InstallExecuteSequence
Custom Action=CA_CheckCredentials After=InstallInitialize /
/InstallExecuteSequence
This all compiles to a .msi without error. I can see CA_CheckCredentials in
Orca just where I want it. But it doesn't seem to be called. I look at the
verbose log and the closest reference I see is:
Action start 14:56:05: InstallInitialize.
MSI (s) (B0:4C) [14:56:06:052]: Doing action: CA_CheckCredentials
MSI (s) (B0:4C) [14:56:06:052]: Note: 1: 2205 2: 3: ActionText
I don't see the string 'Begin CheckCredentials' as in the code above. What do
you think I have done wrong?
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ServiceInstall failure?
It is locking out the account. It is rolling back so nothing is installed but the account is locked out when invalid credentials are supplied. I don't know how to go about debugging this issue. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 3:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? There are no builtin facilities in Windows Installer nor WiX for checking credentials. You'll need to write a custom action to perform this type of check but beware that this check will likely count against the lockout count if the credentials are incorrect. In other words, if you use the custom action as part of the UI and the user tries to validate wrong credentials enough times, then they will still lockout the account. If the MSI does not have a UI then you'll have to run the installer multiple times with invalid credentials to lockout the account with a validation custom action. In other words, I don’t think you can truly avoid the problem as it depends on how many times a user specifies invalid credentials. I have never seen a single installation attempt lockout an account. In my experience the service fails to start and causes the installation to fail initiating a rollback. No lockout. If I attempt the installation enough times with invalid credentials, then I'll see a lockout which is the same as above. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 09, 2011 4:58 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? I consistently get an account lockout when I install and start a service with the wrong credentials. Everything works fine when the proper credentials are supplied. I know it is probably an FAQ but I am just beginning. What facilities are available for checking the credentials and rolling back the installation *before* starting the service? I see recently, someone else queried about conditionally installing/starting a service but I was not able to follow the conclusion. Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- 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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, January 28, 2011 10:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? Since it is so basic can you envision a situation where it would cause an account lockout? By basic what is the underlying implementation being used? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob
Re: [WiX-users] C# Custom Action questions
I think I have solved this problem. The CA was scheduled in the
InstallExecuteSequence and was marked as 'deferred' so I created the following
'Custom Data'.
CustomAction Id=SetProperty Property=CA_CheckCredentials
Value=[SERVICEUSER],[SERVICEPASSWORD] /
CustomAction Id=CA_CheckCredentials
Return=check
Execute=deferred
BinaryKey=CustomActionsDLL
DllEntry=CheckCredentials/
And scheduled it like (I am trying to follow the instructions on page 133 of
'WiX: A Developer's Guide to Windows Installer XML' by Nick Ramirez)
InstallExecuteSequence
Custom Action=SetProperty Before=CA_CheckCredentials /
Custom Action=CA_CheckCredentials After=InstallInitialize /
/InstallExecuteSequence
Now I get the ICE warning:
warning LGHT1076: ICE63: Some action falls between InstallInitialize and
RemoveExistingProducts.
Is this a bad warning? I don't completely understand why this scheduling is
bad. I would like to know that the credentials are bad *before* the existing
products are removed.
If I look at the .msi generated with Orca I see that in the
InstallExecuteSequence table
InstallInitialize 1500
SetProperty 1501
CA_CheckCredentials1502
RemoveExistingProducts 1503
This seems like a valid sequence to me but I am obviously missing something as
the warning is there for a purpose.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Wednesday, March 09, 2011 3:30 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action questions
If I had to guess you calling this CA as a ControlEvent off a Dialog / Control
in your UI sequence. Am I correct? If so, it's a known issue that Msi lacks
the ability to process messages in this scenario. The workaround is to set a
dummy property to see a PROPERTY CHANGED message in the log file where
the value is the data you are trying to log.
Chris
---
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: Kevin Burton kev...@buyseasons.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Wed, March 9, 2011 3:24:17 PM
Subject: [WiX-users] C# Custom Action questions
I have a very simple C# Custom Action that is supposed to verify credentials:
using Microsoft.Deployment.WindowsInstaller;
namespace BuySeasons.BsiServices.Install
{
public class CustomActions
{
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
session.Log(string.Format(Begin CheckCredentials - {0}/{1},
session[SERVICEUSER], session[SERVICEPASSWORD]));
bool valid = false;
using (PrincipalContext context = new
PrincipalContext(ContextType.Domain, ASGARD))
{
valid = context.ValidateCredentials(session[SERVICEUSER],
session[SERVICEPASSWORD]);
}
if(valid)
return ActionResult.Success;
else
return ActionResult.Failure;
}
}
}
It is included in the WiX Product as
Binary Id=CustomActionsDLL
SourceFile=C:\Projects\\bin\$(var.Configuration)\BrainCustomActions.CA.dll
/
CustomAction Id=CA_CheckCredentials
Return=check
Execute=deferred
BinaryKey=CustomActionsDLL
DllEntry=CheckCredentials/
And scheduled as:
InstallExecuteSequence
Custom Action=CA_CheckCredentials After=InstallInitialize /
/InstallExecuteSequence
This all compiles to a .msi without error. I can see CA_CheckCredentials in
Orca
just where I want it. But it doesn't seem to be called. I look at the verbose
log and the closest reference I see is:
Action start 14:56:05: InstallInitialize.
MSI (s) (B0:4C) [14:56:06:052]: Doing action: CA_CheckCredentials
MSI (s) (B0:4C) [14:56:06:052]: Note: 1: 2205 2: 3: ActionText
I don't see the string 'Begin CheckCredentials' as in the code above. What do
you think I have done wrong?
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
Re: [WiX-users] C# Custom Action questions
I read that. Which of the four rules is this violating? I made the warning go away by making the C# CA 'immediate' thus I don't have to have another custom action to remember the property. So I have CustomAction Id=CA_CheckCredentials Return=check Execute=immediate BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And the schedule InstallExecuteSequence Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence But in the verbose log I get: MSI (s) (B8:9C) [22:04:26:415]: Note: 1: 1723 2: CA_CheckCredentials 3: CheckCredentials 4: D:\WINDOWS\Installer\MSI410.tmp Action start 22:04:26: CA_CheckCredentials. MSI (s) (B8:9C) [22:04:26:415]: Product: Bsi WebServices -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp The error says that the DLL cannot be run. Why? I believe I have followed the instructions for writing a managed CA to the tee (though there seems to be some disagreement between the online tutorial http://www.tramontana.co.hu/wix/ and this book). -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 5:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions ICE63 - http://msdn.microsoft.com/en-us/library/aa369008.aspx Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 09, 2011 2:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions I think I have solved this problem. The CA was scheduled in the InstallExecuteSequence and was marked as 'deferred' so I created the following 'Custom Data'. CustomAction Id=SetProperty Property=CA_CheckCredentials Value=[SERVICEUSER],[SERVICEPASSWORD] / CustomAction Id=CA_CheckCredentials Return=check Execute=deferred BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And scheduled it like (I am trying to follow the instructions on page 133 of 'WiX: A Developer's Guide to Windows Installer XML' by Nick Ramirez) InstallExecuteSequence Custom Action=SetProperty Before=CA_CheckCredentials / Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence Now I get the ICE warning: warning LGHT1076: ICE63: Some action falls between InstallInitialize and RemoveExistingProducts. Is this a bad warning? I don't completely understand why this scheduling is bad. I would like to know that the credentials are bad *before* the existing products are removed. If I look at the .msi generated with Orca I see that in the InstallExecuteSequence table InstallInitialize 1500 SetProperty 1501 CA_CheckCredentials1502 RemoveExistingProducts 1503 This seems like a valid sequence to me but I am obviously missing something as the warning is there for a purpose. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, March 09, 2011 3:30 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions If I had to guess you calling this CA as a ControlEvent off a Dialog / Control in your UI sequence. Am I correct? If so, it's a known issue that Msi lacks the ability to process messages in this scenario. The workaround is to set a dummy property to see a PROPERTY CHANGED message in the log file where the value is the data you are trying to log. Chris --- 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: Kevin Burton kev...@buyseasons.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, March 9, 2011 3:24:17 PM Subject: [WiX-users] C# Custom Action questions I have a very simple C# Custom Action that is supposed to verify credentials: using
[WiX-users] Installer question. What does UNKNOWN and Note mean?
This isn't a direct WiX question but there may be something that I am missing
in the WiX code that can avoid this. I notice in the log towards the end if the
installation process it looks like:
MSI (s) (10:E8) [09:03:36:243]: Executing op:
ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (10:E8) [09:03:36:243]: Executing op: CleanupConfigData()
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-484763869-1993962763-1801674531-3563\Products\B83F86C8F37076D4AB308F355B532FE1\Patches
3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op:
RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Products\B83F86C8F37076D4AB308F355B532FE1\Patches 3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op:
ProductPublish(PackageKey={3339230E-FA27-4A24-B887-EF30441391C7})
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op:
UpgradeCodePublish(UpgradeCode={529189FE-FD0E-44FF-8DA6-B4FB5CC7A78B})
MSI (s) (10:E8) [09:03:36:243]: Executing op:
SourceListPublish(NumberOfDisks=1)
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1\SourceList 3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op: ProductPublishClient(,,)
MSI (s) (10:E8) [09:03:36:243]: Executing op:
SourceListRegisterLastUsed(SourceProduct={8C68F38B-073F-4D67-BA03-F853B535F21E},LastUsedSource=C:\Temp\)
MSI (s) (10:E8) [09:03:36:243]: Entering
CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (10:E8) [09:03:36:243]: Specifed source is already in a list.
I looks like the installer is trying to write to a registry path started by
UNKNOWN. Is there something in the WiX code that generates this .msi that would
cause this that I can avoid? Also, how can I interpret the 'Note 1: 1402'? I
see this throughout the install log and I am just curious as to what it means.
--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] UninstallString is incorrect to uninstall the product.
This probably has to do with the fact that I have the element MajorUpgrade in
the .wxs but I notice that in the registry the UninstallString is the same as
the InstallString something like msiexec -I{ABCDE}. The software doesn't
actually get uninstalled with this string I have to use (and the Add/Remove
Program uses) msiexec -X{ABCDE} to uninstall the product. Is there a way
to make the uninstall string something that will really uninstall the product?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Mark Turek [mailto:turekm...@hotmail.com]
Sent: Monday, March 07, 2011 2:21 PM
To: General discussion for Windows Installer XML too
Subject: [WiX-users] Detecting uninstall or minor upgrade
How do I detect uninstall or minor upgrade or first time install. I looked at
the values in the table in the following article
http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi
and I don't think they are correct! Are they? Why do I need (NOT
UPGRADINGPRODUCTCODE) AND (REMOVE=ALL) to detect the uninstall if accoriding
to the table NOT UPGRADINGPRODUCTCODE should be enough?
How do I easily check those values when the installer runs.
--
What You Don't Know About Data Connectivity CAN Hurt You This paper provides an
overview of data connectivity, details its effect on application quality, and
explores various alternative solutions. http://p.sf.net/sfu/progress-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
In the integration with WiX and Visual Studio I notice that a file with the extension .wixpdb is created. The documentation at http://wix.sourceforge.net/manual-wix3/files.htm indicates that this file is A .wixpdb file is created by the linker for each final output. It contains the debugging information.. How is this file used? Or for now should I just ignore it? Kevin -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
The message is clear to you but you are the expert. I doesn't make sense to me.
Let me just try to explain my thought process and you can tell me where I am
misunderstanding. As can be seen from the WiX code below, the version that I am
trying to set my product to is 2.1. The minimum and maximum versions are
minimum of 1.0 and maximum of 3.0. 2.1 seems to fall between these so it is
valid. Older versions of the product would be less than 2.1 (which I am
declaring as the current version)). My thinking is older versions (less or
equal to 2.1) should be removed to make way for the new. This is what I want.
In order to achieve this I set the Upgrade Minimum to be 1.0 and set
IncludeMinimum to 'yes' so that versions less than or equal to the minimum will
be removed (any version that is less than or equal to the current version). As
I understood the 'Maximum' it said that maximum version was 3.0 and if the
product version was greater than the current version but less than the maximum
it was considered a downgrade (again IncludeMaximum is 'no' so it is greater
than the current version and less than the maximum). So when I release a new
version and bump the version number to 2.2 it is still greater than the minimum
and less than the maximum.
Right?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, March 03, 2011 12:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The ICE61 message is pretty clear to me.
This product should remove only older versions of itself. The Maximum version
is not less than the current product.
UpgradeVersion/@Maximum *must* be less than Product/@Version.
Notice I said less than and *not* less than or equal. This is very
important.
You could set UpgradeVersion/@Maximum = Product/@Version _if and only if_
UpgradeVersion/@IncludeMaximum = no.
Of course, the MajorUpgrade element handles all this for you very well.
Product ... Version=2.10 ... UpgradeCode=...
Package ... /
MajorUpgrade DowngradeErrorMessage=A later version of [ProductName] is
already installed. Setup will now exit. /
...
/Product
Can't really get much easier than that.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I am sorry but now I am getting:
\Product.wxs(16,0): warning LGHT1076: ICE61: This product should
remove only older versions of itself. The Maximum version is not less
than the current product. (2.1.0 2.1.0)
\Product.wxs(21,0): warning LGHT1076: ICE61: This product should
remove only older versions of itself. The Maximum version is not less
than the current product. (3.0.0 2.1.0)
The wxs code is:
Product Version=2.1.0
UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND'
Minimum='1.0.0' IncludeMinimum='yes'
Maximum='3.0.0' IncludeMaximum='no' /
/Upgrade
What is this telling me?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE for
use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same
functionality as just not specifying the attribute at all as it is not
required. As the compiler generates a new GUID on each build we meet
the requirements set by Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a different
Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to the
same product family.
The Upgrade table is used
Re: [WiX-users] Uninstall an installed product.
Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between the first and the previous one before the current version will be removed automatically during the installation of the current version. Also note that this same installer works as a first time installer as well: if it founds a previous version, it will remove the previous version and install the current one. If it is run on a clean system, it will simply install the current application; there is no need to create separate upgrade and full installers. This is where I got the idea that the removed versions are from the Minimum to the current (nothing is mentioned about Maximum being less than current). The downgrade idea came as a result of various emails exchanged and the fact that if the version installed is greater than the current version that is replacing it this is by definition a downgrade. Is this out of date? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those references do mention multiple times product versions detected by FindRelatedProducts. FindRelatedProducts Action - http://msdn.microsoft.com/en-us/library/aa368600.aspx The FindRelatedProducts action runs through each record of the Upgrade table in sequence and compares the upgrade code, product version, and language in each row to products installed on the system. When FindRelatedProducts detects a correspondence between the upgrade information and an installed product, it appends the product code to the property specified in the ActionProperty column of the UpgradeTable. The property specified in the UpgradeVersion/@Property gets set when products matching the conditions expressed by the UpgradeVersion element are met. The ICE61 message is telling you what you need to do. If the ICE61 message does not match your expectations then I would trust the ICE61 message and do what it's telling you to do because it is trying to steer you into a correct implementation. The FindRelatedProducts action is responsible for finding installed products matching the conditions specified by the Upgrade table setting one or more properties when it finds matching installed products. You need to schedule FindRelatedProducts for this search to occur otherwise nothing happens. FindRelatedProducts will not uninstall any installed products it finds. That is the job of the RemoveExistingProducts action. To detect products that you want to upgrade you need to specify the minimum and maximum versions you want to detect. You do not want to detect the version of the current product because you don't want to upgrade yourself. To detect newer products you'll need to have a second UpgradeVersion element with a minimum version equal to your current version. This second UpgradeVersion element will set a second property so you can determine that a newer version is installed. Here's some more information that my research assistant (Google) found for me: How To: Implement a Major Upgrade In Your Installer - http://wix.sourceforge.net/manual-wix3/major_upgrade.htm WiX Script for Major Upgrades - http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrades.html Major Upgrades Now Easier Than Ever - http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ I don't mind providing help but I get quite irritated when I'm translating error
Re: [WiX-users] Uninstall an installed product.
I am sorry you feel you are translating error messages but the message is not clear in telling me what to do. I reiterate: \Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) \Product.wxs(21,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (3.0.0 2.1.0) First the statement, this product should remove only older versions of itself.. I agree with that. Why is it a warning? Then it says, The Maximum version is not less than the current product. This is also true but I am not sure why it is a warning. Why are there two warning messages? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those references do mention multiple times product versions detected by FindRelatedProducts. FindRelatedProducts Action - http://msdn.microsoft.com/en-us/library/aa368600.aspx The FindRelatedProducts action runs through each record of the Upgrade table in sequence and compares the upgrade code, product version, and language in each row to products installed on the system. When FindRelatedProducts detects a correspondence between the upgrade information and an installed product, it appends the product code to the property specified in the ActionProperty column of the UpgradeTable. The property specified in the UpgradeVersion/@Property gets set when products matching the conditions expressed by the UpgradeVersion element are met. The ICE61 message is telling you what you need to do. If the ICE61 message does not match your expectations then I would trust the ICE61 message and do what it's telling you to do because it is trying to steer you into a correct implementation. The FindRelatedProducts action is responsible for finding installed products matching the conditions specified by the Upgrade table setting one or more properties when it finds matching installed products. You need to schedule FindRelatedProducts for this search to occur otherwise nothing happens. FindRelatedProducts will not uninstall any installed products it finds. That is the job of the RemoveExistingProducts action. To detect products that you want to upgrade you need to specify the minimum and maximum versions you want to detect. You do not want to detect the version of the current product because you don't want to upgrade yourself. To detect newer products you'll need to have a second UpgradeVersion element with a minimum version equal to your current version. This second UpgradeVersion element will set a second property so you can determine that a newer version is installed. Here's some more information that my research assistant (Google) found for me: How To: Implement a Major Upgrade In Your Installer - http://wix.sourceforge.net/manual-wix3/major_upgrade.htm WiX Script for Major Upgrades - http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrades.html Major Upgrades Now Easier Than Ever - http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ I don't mind providing help but I get quite irritated when I'm translating error and warning messages that are extremely clear. That tells me that the other party is just not trying very hard to learn the domain or the tools. Windows Installer is horribly complex and I understand that... but there is actually a good amount of information out there if you just try to look for it. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 11:11 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The message is clear to you but you are the expert. I doesn't make sense to me. Let me just try to explain my thought process and you can tell me where I am misunderstanding. As can be seen from
Re: [WiX-users] Uninstall an installed product.
Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.1.0' IncludeMaximum='yes' / /Upgrade Do I finally have it? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 3:44 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. Why would Maximum be greater than the current product version? Anything larger than the current version would make the current version obsolete and thus we don't want to upgrade. I'm going to ignore the other stuff about downgrades... I don't have experience to measure how safe and/or complex they are. I generally disallow downgrades, in other words, I use UpgradeVersion to detect a downgrade situation and use a LaunchCondition to prohibit installation. Or more accurately, I let the MajorUpgrade element do it for me since it does a great job in this regard. Use the MajorUpgrade element and let it get it right! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between the first and the previous one before the current version will be removed automatically during the installation of the current version. Also note that this same installer works as a first time installer as well: if it founds a previous version, it will remove the previous version and install the current one. If it is run on a clean system, it will simply install the current application; there is no need to create separate upgrade and full installers. This is where I got the idea that the removed versions are from the Minimum to the current (nothing is mentioned about Maximum being less than current). The downgrade idea came as a result of various emails exchanged and the fact that if the version installed is greater than the current version that is replacing it this is by definition a downgrade. Is this out of date? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those
Re: [WiX-users] Uninstall an installed product.
Thank you. To avoid changing the version to different values in two different places, is the some way to set the 'Maximum' to the equivalent of current version - 1 so it will always work? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 4:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Almost. You want: UpgradeVersion/@IncludeMinimum=yes UpgradeVersion/@IncludeMaximum=no Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 2:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.1.0' IncludeMaximum='yes' / /Upgrade Do I finally have it? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 3:44 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. Why would Maximum be greater than the current product version? Anything larger than the current version would make the current version obsolete and thus we don't want to upgrade. I'm going to ignore the other stuff about downgrades... I don't have experience to measure how safe and/or complex they are. I generally disallow downgrades, in other words, I use UpgradeVersion to detect a downgrade situation and use a LaunchCondition to prohibit installation. Or more accurately, I let the MajorUpgrade element do it for me since it does a great job in this regard. Use the MajorUpgrade element and let it get it right! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between the first and the previous one before the current version will be removed automatically during the installation of the current version. Also note that this same installer works as a first time installer as well: if it founds a previous version, it will remove the previous version and install the current one. If it is run on a clean system, it will simply install the current application; there is no need to create separate upgrade and full installers. This is where I got the idea that the removed versions are from the Minimum to the current (nothing is mentioned about Maximum
Re: [WiX-users] Uninstall an installed product.
Now the code looks like: Product ... Id=* UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Package... / MajorUpgrade AllowDowngrades=no AllowSameVersionUpgrades=yes DowngradeErrorMessage=Downgrading the brain Schedule=afterInstallInitialize/ Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.0.9' IncludeMaximum='yes' / /Upgrade So 2.0.9 is less than 2.1 now I get only one ICE warning C:\... \Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) It looks like it thinks the Maximum is 2.1 when as you can see the Maximum is 2.0.9. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 4:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Almost. You want: UpgradeVersion/@IncludeMinimum=yes UpgradeVersion/@IncludeMaximum=no Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 2:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.1.0' IncludeMaximum='yes' / /Upgrade Do I finally have it? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 3:44 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. Why would Maximum be greater than the current product version? Anything larger than the current version would make the current version obsolete and thus we don't want to upgrade. I'm going to ignore the other stuff about downgrades... I don't have experience to measure how safe and/or complex they are. I generally disallow downgrades, in other words, I use UpgradeVersion to detect a downgrade situation and use a LaunchCondition to prohibit installation. Or more accurately, I let the MajorUpgrade element do it for me since it does a great job in this regard. Use the MajorUpgrade element and let it get it right! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between
Re: [WiX-users] Uninstall an installed product.
Thank you that sounds much easier. Now I have: Product ... Id=* Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Package / MajorUpgrade AllowDowngrades=no AllowSameVersionUpgrades=yes DowngradeErrorMessage=A later version of [ProductName] is already installed. Schedule=afterInstallInitialize/ But I still get the message: C:\...\Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) I am not sure where it is picking up Maximum from. I tried changing the version to make sure I was using the right .wxs file and then the error message is the same but with 2.2.0 substituted for the version so changes in this .wxs are reflected in the error messages. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 5:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. You do not want to include your own Upgrade element (and UpgradeVersion element) if you are using the MajorUpgrade element. The MajorUpgrade element takes care of authoring the Upgrade table for you. Product Id=* UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B ... Package ... / MajorUpgrade ... / !-- Upgrade and UpgradeVersion elements no longer needed -- ... /Product I also want to make another comment. 2.0.9 is indeed less than 2.1.0. 2.0.10 is also less than 2.1.0. The ranges for ProductVersion are 0-255.0-255.0-65535 See http://msdn.microsoft.com/en-us/library/aa370859.aspx *IF* you want to keep your Upgrade and UpgradeVersion elements then I recommend that you set UpgradeVersion/@Maximum to Product/@Version and UpgradeVersion/@IncludeMaximum to no. I recommend that you remove the Upgrade and UpgradeVersion elements all together and keep only the MajorUpgrade element letting it take care of everything for you. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 3:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Now the code looks like: Product ... Id=* UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Package... / MajorUpgrade AllowDowngrades=no AllowSameVersionUpgrades=yes DowngradeErrorMessage=Downgrading the brain Schedule=afterInstallInitialize/ Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.0.9' IncludeMaximum='yes' / /Upgrade So 2.0.9 is less than 2.1 now I get only one ICE warning C:\... \Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) It looks like it thinks the Maximum is 2.1 when as you can see the Maximum is 2.0.9. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 4:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Almost. You want: UpgradeVersion/@IncludeMinimum=yes UpgradeVersion/@IncludeMaximum=no Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 2:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode
Re: [WiX-users] Uninstall an installed product.
When I set it to * I get an error that it is not a GUID format. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, March 01, 2011 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent
Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the Product/@Id to * then how do I change it so that the previous version is uninstalled? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 02, 2011 12:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. What is it? I usually set Product\@Id=* and do not set Package\@Id at all. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 02, 2011 6:27 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. When I set it to * I get an error that it is not a GUID format. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, March 01, 2011 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you
Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the MajorUpgrade.. element
below the Product. I have the namespace for the schema set to
http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column 565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace 'http://schemas.microsoft.com/wix/2006/wi'. List of
possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The AutogenGuid
description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF or
{01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-generated by
setting the value to *. Also allows PUT-GUID-HERE for use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same functionality as
just not specifying the attribute at all as it is not required. As the compiler
generates a new GUID on each build we meet the requirements set by Windows
Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a package
that has a different Package/@Id (by definition), a different Product/@Id, a
different Product/@Version, and the SAME Product/@UpgradeCode as a currently
installed product. The Product/@UpgradeCode is what ties together products that
belong to the same product family.
The Upgrade table is used to detect previously installed products that should
be upgraded and schedules them to be uninstalled. The MajorUpgrade element
makes it really easy to author the Upgrade table correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different Product/@Version on
every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures the
package in your installer is automatically regenerated with a new GUID
each time you build it. This means when uninstalling, the MSI wont be
confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the
Product/@Id to * then how do I change it so that the previous version is
uninstalled?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What is it? I usually set Product\@Id=* and do not set Package\@Id at all.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
When I set it to * I get an error that it is not a GUID format.
Kevin Burton
Re: [WiX-users] Uninstall an installed product.
Thank you.
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm
lists Product as the parent.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 5:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
Assuming you are using WiX 3.5.2519.0, then you need to put the MajorUpgrade
element after the Package element. The Package element must be the first child
of Product. See http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm.
Wix xmlns=
Product ...
Package ... /
...
MajorUpgrade ... /
...
/Product
/Wix
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 3:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What version of WiX do you have?
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 3:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the
MajorUpgrade.. element below the Product. I have the namespace
for the schema set to http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column
565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace
'http://schemas.microsoft.com/wix/2006/wi'.
List of possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-
456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE
for use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each
build.
Windows Installer requires that each and every package has a
different Package/@Id. Explicitly setting Package/@Id to * is the
same functionality as just not specifying the attribute at all as it
is not required. As the compiler generates a new GUID on each build
we meet the requirements set by Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a
different Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to
the same product family.
The Upgrade table is used to detect previously installed products
that should be upgraded and schedules them to be uninstalled. The
MajorUpgrade element makes it really easy to author the Upgrade
table correctly. See http://wix.sourceforge.net/manual-
wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do
the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct
behavior.
* Guarantee that your build process results in a different
Product/@Version on every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject
Re: [WiX-users] Uninstall an installed product.
The error occurs with 'light'
H:\light -?
Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0
Copyright (C) Microsoft Corporation. All rights reserved.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 5:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What version of WiX do you have?
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 3:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the MajorUpgrade..
element below the Product. I have the namespace for the schema set
to http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column
565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace 'http://schemas.microsoft.com/wix/2006/wi'.
List of possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE for
use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same
functionality as just not specifying the attribute at all as it is not
required. As the compiler generates a new GUID on each build we meet
the requirements set by Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a different
Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to the
same product family.
The Upgrade table is used to detect previously installed products that
should be upgraded and schedules them to be uninstalled. The
MajorUpgrade element makes it really easy to author the Upgrade table
correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do
the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different
Product/@Version on every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures
the package in your installer is automatically regenerated with a
new GUID each time you build it. This means when uninstalling, the
MSI wont be confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the
Product/@Id to * then how do I change it so that the previous
version is
uninstalled?
Kevin Burton
Senior
Re: [WiX-users] Uninstall an installed product.
I am sorry but now I am getting:
\Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only
older versions of itself. The Maximum version is not less than the current
product. (2.1.0 2.1.0)
\Product.wxs(21,0): warning LGHT1076: ICE61: This product should remove only
older versions of itself. The Maximum version is not less than the current
product. (3.0.0 2.1.0)
The wxs code is:
Product Version=2.1.0
UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND'
Minimum='1.0.0' IncludeMinimum='yes'
Maximum='3.0.0' IncludeMaximum='no' /
/Upgrade
What is this telling me?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The AutogenGuid
description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF or
{01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-generated by
setting the value to *. Also allows PUT-GUID-HERE for use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same functionality as
just not specifying the attribute at all as it is not required. As the compiler
generates a new GUID on each build we meet the requirements set by Windows
Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a package
that has a different Package/@Id (by definition), a different Product/@Id, a
different Product/@Version, and the SAME Product/@UpgradeCode as a currently
installed product. The Product/@UpgradeCode is what ties together products that
belong to the same product family.
The Upgrade table is used to detect previously installed products that should
be upgraded and schedules them to be uninstalled. The MajorUpgrade element
makes it really easy to author the Upgrade table correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different Product/@Version on
every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures the
package in your installer is automatically regenerated with a new GUID
each time you build it. This means when uninstalling, the MSI wont be
confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the
Product/@Id to * then how do I change it so that the previous version is
uninstalled?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What is it? I usually set Product\@Id=* and do not set Package\@Id at all.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:27 AM
To: General discussion for Windows Installer XML toolset
Re: [WiX-users] Uninstall an installed product.
What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burton kev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs
Re: [WiX-users] Uninstall an installed product.
The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance
[WiX-users] Uninstall an installed product.
I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, February 23, 2011 11:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command line installation? Hi, To set a property from the command line you simply just set the property to be equal to the required value. e.g. Msiexec /i installer.msi FULLYQUALIFIEDCOMPUTERNAME=Kevinspc.buyseasons.com SERVICEUSER=bob etc. Remember to make all your properties public my making them all CAPS to and you may need to set them to be secure, set any password properties to hidden to remove them from logs. You should be able to condition the display of your dialogue based on the properties that you have stated but it is also possible to run the msi without any ui at all by altering the command line with /qn. dave -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 23 February 2011 15:08 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Command line installation? I would like to know what strategies are best to use if I optionally don't want a UI. Right now I have a custom dialog that appears and it sets a number of properties. If any of these properties are set on the command line I would like to skip the dialog. That is one question. The second question is how do I set the properties on the command line? If it helps the dialog is defined as ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment UI Property Id=FULLYQUALIFIEDCOMPUTERNAME Hidden=yesdevbrain03/Property Property Id=SERVICEUSER Hidden=yesuser/Property Property Id=SERVICEPASSWORD Hidden=yestesting/Property Property Id=SQLSERVER Hidden=yescomputer/Property Property Id=TRANSACTIONSSQLSERVER Hidden=yescomputer/Property Property Id=REPLICATEDTRANSACTIONSERVER Hidden=yescomputer/Property Property Id=INVENTORYSERVER Hidden=yescomputer/Property Property Id=SHIPPINGSERVER Hidden=yescomputer/Property Property Id=COMMERCESERVERSITENAME Hidden=yessite/Property Property Id=SMTPSERVERNAME Hidden=yesmail.company.com/Property Property Id=LYRISSQLSERVER Hidden=yesserver/Property Property Id=LYRISUSER Hidden=yesuser/Property Property Id=LYRISPASSWORD Hidden=yestesting/Property Property Id=CYBERSOURCEURL Hidden=yeshttps://myco.ic3.com/ /Property Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes Control Id=Title Type=Text X=15 Y=6 Width=200 Height=15 Transparent=yes NoPrefix=yes Text=Ready to Install / Control Id=ComputerNameLabel Type=Text X=15 Y=26 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Computer Name / Control Id=ComputerNameEdit Type=Edit X=114 Y=22 Width=150 Height=18 Property=FULLYQUALIFIEDCOMPUTERNAME / Control Id=UserLabel Type=Text X=15 Y=46 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=User / Control Id=UserEdit Type=Edit X=114 Y=42 Width=150 Height=18 Property=SERVICEUSER / Control Id=PasswordLabel Type=Text X=15 Y=66 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Password / Control Id=PasswordEdit Type=Edit X=114 Y=62 Width=150 Height=18 Property=SERVICEPASSWORD Password=yes / Control Id=SqlServerLabel Type=Text X=15 Y=86 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=BuySeasons Sql Server / Control Id=SqlServerEdit Type=Edit X=114 Y=82 Width=150 Height=18 Property=SQLSERVER / Control Id=TransactionsSqlServerLabel Type=Text X=15 Y=106 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Transactions Sql Server / Control Id=TransactionsSqlServerEdit Type=Edit X=114 Y=102 Width=150 Height=18 Property=TRANSACTIONSSQLSERVER / Control Id=ShippingSqlServerLabel Type=Text X=15 Y=126 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Shipping Sql Server / Control Id=ShippingSqlServerEdit Type=Edit X=114 Y=122 Width=150 Height=18 Property=SHIPPINGSERVER / Control Id=ReplicatedTransactionsSqlServerLabel Type=Text X=15 Y=146 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Replicated Sql Server / Control Id=ReplicatedTransactionsSqlServerEdit Type=Edit X=114 Y=142 Width=150 Height=18 Property=REPLICATEDTRANSACTIONSERVER / Control Id=InventoryServerLabel Type=Text X=15 Y=166 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Inventory Server / Control Id
Re: [WiX-users] Command line installation?
I have WiX code like: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=2.0.0.0 Maximum=2.0.5.0 Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence I am trying to automatically uninstall any previous versions of the package before this installation proceeds. But even with this code when I run the .msi I get a prompt indicating that I must go to the Control Panel and uninstall a previous version. What am I doing wrong? Kevin -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Command line installation?
=CyberSourceURLEdit Type=Edit X=114 Y=322 Width=150 Height=18 Property=CYBERSOURCEURL / Control Id=OK Type=PushButton X=104 Y=352 Width=56 Height=17 Default=yes Text=OK Publish Event=EndDialog Value=Return/ /Control Control Id=Cancel Type=PushButton X=164 Y=352 Width=56 Height=17 Cancel=yes Text=Cancel Publish Event=EndDialog Value=Exit/ /Control /Dialog AdminUISequence / InstallUISequence / /UI /Fragment /Wix Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, February 16, 2011 9:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element I don't think more disk space should be consumed if things are cabbed and the service executable is identical in the two Components (one Conditioned, the other not) because only one will ever get installed on the machine (due to mutually exclusive Conditions) and smart-cabbing should make sure only one file is in the cabinet. (wow, that's one sentence smile/). On Mon, Feb 14, 2011 at 8:50 AM, Christopher Painter chr...@deploymentengineering.com wrote: Technically it's a violation of the component rules. However, if you can make sure that the two components ( whether they be in two merge modules or no merge modules ) have mutually exclusive component conditions so that only one will ever be installed you can pretty much get away with it. You will still get validation errors as part of the build though I believe. I've done this in the past and my main complaint about it is it doesn't scale well. If dev doesn't want to redo the app, what would be the effect of taking consoleappservice.exe and copying / renaming it to have two files: consoleapp.exe service.exe It's a confusing hack and you'll eat up more disk space then if you factored it out into the shared.dll but you should be able to still do everything I mentioned previously. If this is .NET code it might not be happy but you could give it a try. Personally if it is a .NET service, I can't imagine it taking more then a few hours to factor out, build and test. --- 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: Gregg Swanson gregg.swan...@microsoft.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, February 14, 2011 10:38:26 AM Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element Thanks for the help... I am a WIX rooky. Is this is a valid option - Package the consleappservice.exe in two separate merge modules, the first doesn't invoke ServiceInstall the second does invoke ServiceInstall? The application that I am helping will have to refactor code and they may be reluctant to do so at this point in time. Thanks, Gregg -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Monday, February 14, 2011 10:14 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element The ServiceControl element is a child of the Component which is a child of the Feature element so the condition can be applied at the Feature or Component level. If the component is installed the service will be installed and there's no way around that except to factor your service out of the console app: consleappservice.exe - consoleapp.exe, service.exe, shared.dll Then you can put have Feature A reference the consoleapp.exe and shared.dll components and Feature B referene service.exe and shared.dll components. ( Note: There is only 1 shared.dll component ) If feature B is installed you will get a service. If feature B is not installed you will not get a service but you can still have your console app if feature A is installed. From a SysAdmin's point of view it's silent installs can be: msiexec /i foo.msi ADDLOCAL=A /qn or msiexec /i foo.msi ADDLOCAL=A,B /qn If the service was not previously installed and now desired they can issue the command: msiexec /i foo.msi ADDLOCAL=B /qn If the service was previously installed and no longer desired they can issue the command msiexec /i foo.msi REMOVE=B /qn If they want to uninstall all together they can say: msiexec /x foo.msi /qn or msiexec /i foo.msi REMOVE=ALL /qn --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves
Re: [WiX-users] Command line installation?
Thanks for the tip. -qn will probably solve the problem. What would be the syntax of condition? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, February 23, 2011 11:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command line installation? Hi, To set a property from the command line you simply just set the property to be equal to the required value. e.g. Msiexec /i installer.msi FULLYQUALIFIEDCOMPUTERNAME=Kevinspc.buyseasons.com SERVICEUSER=bob etc. Remember to make all your properties public my making them all CAPS to and you may need to set them to be secure, set any password properties to hidden to remove them from logs. You should be able to condition the display of your dialogue based on the properties that you have stated but it is also possible to run the msi without any ui at all by altering the command line with /qn. dave -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 23 February 2011 15:08 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Command line installation? I would like to know what strategies are best to use if I optionally don't want a UI. Right now I have a custom dialog that appears and it sets a number of properties. If any of these properties are set on the command line I would like to skip the dialog. That is one question. The second question is how do I set the properties on the command line? If it helps the dialog is defined as ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment UI Property Id=FULLYQUALIFIEDCOMPUTERNAME Hidden=yesdevbrain03/Property Property Id=SERVICEUSER Hidden=yesuser/Property Property Id=SERVICEPASSWORD Hidden=yestesting/Property Property Id=SQLSERVER Hidden=yescomputer/Property Property Id=TRANSACTIONSSQLSERVER Hidden=yescomputer/Property Property Id=REPLICATEDTRANSACTIONSERVER Hidden=yescomputer/Property Property Id=INVENTORYSERVER Hidden=yescomputer/Property Property Id=SHIPPINGSERVER Hidden=yescomputer/Property Property Id=COMMERCESERVERSITENAME Hidden=yessite/Property Property Id=SMTPSERVERNAME Hidden=yesmail.company.com/Property Property Id=LYRISSQLSERVER Hidden=yesserver/Property Property Id=LYRISUSER Hidden=yesuser/Property Property Id=LYRISPASSWORD Hidden=yestesting/Property Property Id=CYBERSOURCEURL Hidden=yeshttps://myco.ic3.com/ /Property Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes Control Id=Title Type=Text X=15 Y=6 Width=200 Height=15 Transparent=yes NoPrefix=yes Text=Ready to Install / Control Id=ComputerNameLabel Type=Text X=15 Y=26 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Computer Name / Control Id=ComputerNameEdit Type=Edit X=114 Y=22 Width=150 Height=18 Property=FULLYQUALIFIEDCOMPUTERNAME / Control Id=UserLabel Type=Text X=15 Y=46 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=User / Control Id=UserEdit Type=Edit X=114 Y=42 Width=150 Height=18 Property=SERVICEUSER / Control Id=PasswordLabel Type=Text X=15 Y=66 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Password / Control Id=PasswordEdit Type=Edit X=114 Y=62 Width=150 Height=18 Property=SERVICEPASSWORD Password=yes / Control Id=SqlServerLabel Type=Text X=15 Y=86 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=BuySeasons Sql Server / Control Id=SqlServerEdit Type=Edit X=114 Y=82 Width=150 Height=18 Property=SQLSERVER / Control Id=TransactionsSqlServerLabel Type=Text X=15 Y=106 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Transactions Sql Server / Control Id=TransactionsSqlServerEdit Type=Edit X=114 Y=102 Width=150 Height=18 Property=TRANSACTIONSSQLSERVER / Control Id=ShippingSqlServerLabel Type=Text X=15 Y=126 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Shipping Sql Server / Control Id=ShippingSqlServerEdit Type=Edit X=114 Y=122 Width=150 Height=18 Property=SHIPPINGSERVER / Control Id=ReplicatedTransactionsSqlServerLabel Type=Text X=15 Y=146 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Replicated Sql Server / Control Id=ReplicatedTransactionsSqlServerEdit Type=Edit X=114 Y=142 Width=150 Height=18 Property=REPLICATEDTRANSACTIONSERVER / Control Id=InventoryServerLabel Type=Text X=15 Y=166 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Inventory Server / Control Id=InventoryServerEdit Type=Edit X=114 Y=162 Width=150 Height=18 Property=INVENTORYSERVER / Control Id=LyrisDatabaseSqlServerLabel Type=Text X=15 Y=186 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Lyris Sql Server
Re: [WiX-users] Command line installation?
Since I have set default properties I just need to test BEFORE I set the default to make sure some key required properties are set and if any of these are set then I could safely avoid the dialog UI and take the defaults for the rest. How do I test for the existence of a property and disable the dialog if true? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, February 23, 2011 11:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command line installation? I can offer some help. For the command line you append your PROPERTYNAME followed by an equal sign and then the value you want to assign to that property. Like this. msiexec /L*v c:\log.txt /i my.msi PROPERTYNAME1=value1 PROPERTYNAME2=value2 In my experience it seemed like if you gave it all required properties that correspond to your UI then it breezes through without a hitch. But, if you forget a property it either starts popping up dialog boxes for you to fill in or some other behavior, I can't remember which. I'm not sure if you only give it one or two properties that it's going to know what to do for the remainder. A command line that works for my installer is 623 characters long, but it can install in a test environment where all properties are known quantities without any dialogs showing. Really helps with automation. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, February 23, 2011 7:08 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Command line installation? I would like to know what strategies are best to use if I optionally don't want a UI. Right now I have a custom dialog that appears and it sets a number of properties. If any of these properties are set on the command line I would like to skip the dialog. That is one question. The second question is how do I set the properties on the command line? If it helps the dialog is defined as ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment UI Property Id=FULLYQUALIFIEDCOMPUTERNAME Hidden=yesdevbrain03/Property Property Id=SERVICEUSER Hidden=yesuser/Property Property Id=SERVICEPASSWORD Hidden=yestesting/Property Property Id=SQLSERVER Hidden=yescomputer/Property Property Id=TRANSACTIONSSQLSERVER Hidden=yescomputer/Property Property Id=REPLICATEDTRANSACTIONSERVER Hidden=yescomputer/Property Property Id=INVENTORYSERVER Hidden=yescomputer/Property Property Id=SHIPPINGSERVER Hidden=yescomputer/Property Property Id=COMMERCESERVERSITENAME Hidden=yessite/Property Property Id=SMTPSERVERNAME Hidden=yesmail.company.com/Property Property Id=LYRISSQLSERVER Hidden=yesserver/Property Property Id=LYRISUSER Hidden=yesuser/Property Property Id=LYRISPASSWORD Hidden=yestesting/Property Property Id=CYBERSOURCEURL Hidden=yeshttps://myco.ic3.com/ /Property Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes Control Id=Title Type=Text X=15 Y=6 Width=200 Height=15 Transparent=yes NoPrefix=yes Text=Ready to Install / Control Id=ComputerNameLabel Type=Text X=15 Y=26 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Computer Name / Control Id=ComputerNameEdit Type=Edit X=114 Y=22 Width=150 Height=18 Property=FULLYQUALIFIEDCOMPUTERNAME / Control Id=UserLabel Type=Text X=15 Y=46 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=User / Control Id=UserEdit Type=Edit X=114 Y=42 Width=150 Height=18 Property=SERVICEUSER / Control Id=PasswordLabel Type=Text X=15 Y=66 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Password / Control Id=PasswordEdit Type=Edit X=114 Y=62 Width=150 Height=18 Property=SERVICEPASSWORD Password=yes / Control Id=SqlServerLabel Type=Text X=15 Y=86 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=BuySeasons Sql Server / Control Id=SqlServerEdit Type=Edit X=114 Y=82 Width=150 Height=18 Property=SQLSERVER / Control Id=TransactionsSqlServerLabel Type=Text X=15 Y=106 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Transactions Sql Server / Control Id=TransactionsSqlServerEdit Type=Edit X=114 Y=102 Width=150 Height=18 Property=TRANSACTIONSSQLSERVER / Control Id=ShippingSqlServerLabel Type=Text X=15 Y=126 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Shipping Sql Server / Control Id=ShippingSqlServerEdit Type=Edit X=114 Y=122 Width=150 Height=18 Property=SHIPPINGSERVER / Control Id=ReplicatedTransactionsSqlServerLabel Type=Text X=15 Y=146 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Replicated Sql Server / Control Id
Re: [WiX-users] ServiceInstall failure?
No impersonations myself. This started occurring when there was a problem with my Custom UI which among other things prompted for a password. The UI was not showing up and so the password was not valid. But the install continued. It got to ServiceIntall and ServiceControl and the ServiceControl task failed because of an invalid password but the account (my account) that the service was installed under was locked out. My administrator indicated that something or someone tried and failed too many times so the account was locked out. I hate to try it again because it takes I am guessing the Domain Admin to unlock the account again and I hate to continually asked the admin to unlock my account. Hence the question. If you have suggestions on how I might implement the custom action to validate the credentials I would be very appreciative. That may solve my problem. I have a WiX 2.0 script that works right now so I am reasonably sure that my account has the proper rights. I have subsequently successfully installed and started the service using that installation script. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: MikeR [mailto:michael.ru...@gmail.com] Sent: Tuesday, February 01, 2011 10:52 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ServiceInstall failure? Are you explicitly doing any impersonation of the logon user in custom actions yourself? If you are obtaining logon credentials from the user (via dialog or command line) I would implement a custom action to validate those credentials before you make any system changes and prevent the install from proceeding until you have valid credentials. I would also recommend checking that the account has the ServiceLogonRight policy set so to ensure it can be used to run services. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ServiceInstall-failure-tp5967359p5981755.html Sent from the wix-users mailing list archive at Nabble.com. -- 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
Re: [WiX-users] ServiceInstall failure?
Assuming that I can translate this to C#, what would be the WiX code that needs to be in place to call this function? I am fairly new to 3.x and I remember that with 2.0 there needed to be a fair amount of plumbing in place to call a C# (managed) custom action. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Wednesday, February 02, 2011 2:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? A usual way to validate credentials is to use the LogonUser() Win32 API, but that's a logon that can fail, which is what you don't want. The only other way I'm aware of is SSPLogonUser(), huge C++ example here: http://support.microsoft.com/kb/180548 Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, February 02, 2011 6:55 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? No impersonations myself. This started occurring when there was a problem with my Custom UI which among other things prompted for a password. The UI was not showing up and so the password was not valid. But the install continued. It got to ServiceIntall and ServiceControl and the ServiceControl task failed because of an invalid password but the account (my account) that the service was installed under was locked out. My administrator indicated that something or someone tried and failed too many times so the account was locked out. I hate to try it again because it takes I am guessing the Domain Admin to unlock the account again and I hate to continually asked the admin to unlock my account. Hence the question. If you have suggestions on how I might implement the custom action to validate the credentials I would be very appreciative. That may solve my problem. I have a WiX 2.0 script that works right now so I am reasonably sure that my account has the proper rights. I have subsequently successfully installed and started the service using that installation script. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: MikeR [mailto:michael.ru...@gmail.com] Sent: Tuesday, February 01, 2011 10:52 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ServiceInstall failure? Are you explicitly doing any impersonation of the logon user in custom actions yourself? If you are obtaining logon credentials from the user (via dialog or command line) I would implement a custom action to validate those credentials before you make any system changes and prevent the install from proceeding until you have valid credentials. I would also recommend checking that the account has the ServiceLogonRight policy set so to ensure it can be used to run services. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ServiceInstall-failure-tp5967359p5981755.html Sent from the wix-users mailing list archive at Nabble.com. -- 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 *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW
Re: [WiX-users] ServiceInstall failure?
OK it doesn't cause the lockout *directly* but can this happen? 1) Service fails to start because of bad password. (one bad login attempt) 2) Since service does not start it triggers a rollback which first tries to stop the service (second bad login attempt) 3) To remove the service an impersonation attempt is made (third bad login attempt) I think (I will have to verify with the administrator) that the account lockout occurs after three bad login attempts. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- 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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, January 28, 2011 10:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? Since it is so basic can you envision a situation where it would cause an account lockout? By basic what is the underlying implementation being used? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, January 28, 2011 7:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? The built in service install of the Windows Installer is pretty basic. One of the few standard actions I've seriously considered replacing with a custom action. On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton kev...@buyseasons.comwrote: It seems that the default behavior for this code ServiceInstall Id=BsiServiceInstall DisplayName=BsiServices Host Name=ServiceExeFile Description=Windows Service host for Bsi Web Services Interactive=no Account=[SERVICEUSER] Password=[SERVICEPASSWORD] ErrorControl=normal Start=demand Type=ownProcess Vital=yes / ServiceControl Id=BsiServiceControl Name=ServiceExeFile Start=install Stop=uninstall Remove=uninstall Wait=yes / Is to repeatedly try, even when the password is invalid, until the account specified is locked out. I was wondering if there was a way to catch the first error and display it to the user. Also I would like to associate some sort of progress bar with the installation and starting of this service. Is there a good reference for this type of function? Thank you. Kevin -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC -- Special Offer
Re: [WiX-users] ServiceInstall failure?
I am just trying to imagine scenarios where the lockout could happen. Because it is happening. I realize that the service is not started but I was thinking that somewhere in the code it is not checking that the service is started or not it is just trying to stop the service. I was thinking #3 more or less in the same vein as #2. An impersonation attempt was made without checking whether it was needed or not. Can a failed rollback trigger another rollback and start a cascade? -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Monday, January 31, 2011 8:59 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? #1 could happen. #2 could not happen because a) the service isn't started so there's nothing to stop and b) a login is not required to stop the service. #3 could not happen because a login is not needed to remove the service. The credentials are only needed when attempting to start the service. Even if the account is locked while the service is running you may not notice if the service doesn't do anything to authenticate itself such as connect to another service. It's only when loading the security token would it matter. 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: Kevin Burton kev...@buyseasons.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, January 31, 2011 8:44:01 AM Subject: Re: [WiX-users] ServiceInstall failure? OK it doesn't cause the lockout *directly* but can this happen? 1) Service fails to start because of bad password. (one bad login attempt) 2) Since service does not start it triggers a rollback which first tries to stop the service (second bad login attempt) 3) To remove the service an impersonation attempt is made (third bad login attempt) I think (I will have to verify with the administrator) that the account lockout occurs after three bad login attempts. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- 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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, January 28, 2011 10:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? Since it is so basic can you envision a situation where it would cause an account lockout? By basic what is the underlying implementation being used? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, January 28, 2011 7:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? The built in service install of the Windows Installer is pretty basic. One of the few standard actions I've seriously considered replacing
Re: [WiX-users] ServiceInstall failure?
I am just trying to imagine scenarios where the lockout could happen. Because it is happening. I realize that the service is not started but I was thinking that somewhere in the code it is not checking that the service is started or not it is just trying to stop the service. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Monday, January 31, 2011 8:59 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? #1 could happen. #2 could not happen because a) the service isn't started so there's nothing to stop and b) a login is not required to stop the service. #3 could not happen because a login is not needed to remove the service. The credentials are only needed when attempting to start the service. Even if the account is locked while the service is running you may not notice if the service doesn't do anything to authenticate itself such as connect to another service. It's only when loading the security token would it matter. 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: Kevin Burton kev...@buyseasons.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, January 31, 2011 8:44:01 AM Subject: Re: [WiX-users] ServiceInstall failure? OK it doesn't cause the lockout *directly* but can this happen? 1) Service fails to start because of bad password. (one bad login attempt) 2) Since service does not start it triggers a rollback which first tries to stop the service (second bad login attempt) 3) To remove the service an impersonation attempt is made (third bad login attempt) I think (I will have to verify with the administrator) that the account lockout occurs after three bad login attempts. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- 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: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, January 28, 2011 10:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? Since it is so basic can you envision a situation where it would cause an account lockout? By basic what is the underlying implementation being used? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, January 28, 2011 7:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? The built in service install of the Windows Installer is pretty basic. One of the few standard actions I've seriously considered replacing with a custom action. On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton kev...@buyseasons.comwrote: It seems that the default behavior for this code ServiceInstall Id=BsiServiceInstall DisplayName
Re: [WiX-users] ServiceInstall failure?
Since it is so basic can you envision a situation where it would cause an account lockout? By basic what is the underlying implementation being used? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, January 28, 2011 7:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? The built in service install of the Windows Installer is pretty basic. One of the few standard actions I've seriously considered replacing with a custom action. On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton kev...@buyseasons.comwrote: It seems that the default behavior for this code ServiceInstall Id=BsiServiceInstall DisplayName=BsiServices Host Name=ServiceExeFile Description=Windows Service host for Bsi Web Services Interactive=no Account=[SERVICEUSER] Password=[SERVICEPASSWORD] ErrorControl=normal Start=demand Type=ownProcess Vital=yes / ServiceControl Id=BsiServiceControl Name=ServiceExeFile Start=install Stop=uninstall Remove=uninstall Wait=yes / Is to repeatedly try, even when the password is invalid, until the account specified is locked out. I was wondering if there was a way to catch the first error and display it to the user. Also I would like to associate some sort of progress bar with the installation and starting of this service. Is there a good reference for this type of function? Thank you. Kevin -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC -- 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] Skipped Custom UI?
I have a WiX Custom UI that I have converted from 2.0 source. The problem I am experiencing and would like a little help with is that the Dialog is not showing up when I run the .msi script. I have used Orca and I can see the Dialog in the .msi file but for some reason it is not getting called. I would like to have this Dialog scheduled right after the license agreement (which is what the 2.0 code did). Any hints as to where in the verbose log I could look to start seeing clues as to why this Dialog is not being called? Any hints as to the differences between 2.0 and 3.x that would cause the UI to be skipped? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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
Re: [WiX-users] Skipped Custom UI?
I see 'Doing action: WelcomeEulaDlg' but I don't see anything about LicenseAgreementDlg. Maybe it is changed names and that is why I don't see the dialog. I have code like Fragment UIRef Id=WixUI_Minimal/ UIRef Id=WixUI_ErrorProgressText/ UI DialogRef Id=WelcomeEulaDlg / Property Id=WelcomeEulaDlg_Install Value=PropertiesDlg / Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 27, 2011 9:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? Have you Published the required Control event to show your Custom Dialog to the Next button in the LicenseAgreementDlg? When you click the Next button in the LicenseAgreementDlg the verbose log should tell you what it's actually doing at that point. I'd wager that's a good place to look. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 27 January 2011 15:04 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Skipped Custom UI? I have a WiX Custom UI that I have converted from 2.0 source. The problem I am experiencing and would like a little help with is that the Dialog is not showing up when I run the .msi script. I have used Orca and I can see the Dialog in the .msi file but for some reason it is not getting called. I would like to have this Dialog scheduled right after the license agreement (which is what the 2.0 code did). Any hints as to where in the verbose log I could look to start seeing clues as to why this Dialog is not being called? Any hints as to the differences between 2.0 and 3.x that would cause the UI to be skipped? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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
Re: [WiX-users] Skipped Custom UI?
I don't follow the statement So you're using WiXUI_Minimal also defining the exact same dialogs in your own code? The name of the WelcomeEulaDlg I found via ORCA. The PropertiesDlg is the custom UI that I have defined. With 3.0 is there a Dialog called 'PropertiesDlg' that I am overwriting or redefining? I use WiXUI_Minimal to pull in the name of the WelcomeEulaDlg. Is that not right? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 27, 2011 10:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? So you're using WiXUI_Minimal also defining the exact same dialogs in your own code? That'll work well. I suggest re-reading the links I posted on Tuesday (subject Re: [WiX-users] Build failed?) for the UI. The answers are in the documentation Neil S's blog which you've been supplied with once already. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 27 January 2011 15:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? I see 'Doing action: WelcomeEulaDlg' but I don't see anything about LicenseAgreementDlg. Maybe it is changed names and that is why I don't see the dialog. I have code like Fragment UIRef Id=WixUI_Minimal/ UIRef Id=WixUI_ErrorProgressText/ UI DialogRef Id=WelcomeEulaDlg / Property Id=WelcomeEulaDlg_Install Value=PropertiesDlg / Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 27, 2011 9:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? Have you Published the required Control event to show your Custom Dialog to the Next button in the LicenseAgreementDlg? When you click the Next button in the LicenseAgreementDlg the verbose log should tell you what it's actually doing at that point. I'd wager that's a good place to look. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 27 January 2011 15:04 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Skipped Custom UI? I have a WiX Custom UI that I have converted from 2.0 source. The problem I am experiencing and would like a little help with is that the Dialog is not showing up when I run the .msi script. I have used Orca and I can see the Dialog in the .msi file but for some reason it is not getting called. I would like to have this Dialog scheduled right after the license agreement (which is what the 2.0 code did). Any hints as to where in the verbose log I could look to start seeing clues as to why this Dialog is not being called? Any hints as to the differences between 2.0 and 3.x that would cause the UI to be skipped? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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
Re: [WiX-users] Skipped Custom UI?
Do you have that link? Or how do I get archives? My current problem is that the dialog is getting skipped. I have moved past build failed so that email has been deleted. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 27, 2011 10:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? So you're using WiXUI_Minimal also defining the exact same dialogs in your own code? That'll work well. I suggest re-reading the links I posted on Tuesday (subject Re: [WiX-users] Build failed?) for the UI. The answers are in the documentation Neil S's blog which you've been supplied with once already. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 27 January 2011 15:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? I see 'Doing action: WelcomeEulaDlg' but I don't see anything about LicenseAgreementDlg. Maybe it is changed names and that is why I don't see the dialog. I have code like Fragment UIRef Id=WixUI_Minimal/ UIRef Id=WixUI_ErrorProgressText/ UI DialogRef Id=WelcomeEulaDlg / Property Id=WelcomeEulaDlg_Install Value=PropertiesDlg / Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 27, 2011 9:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? Have you Published the required Control event to show your Custom Dialog to the Next button in the LicenseAgreementDlg? When you click the Next button in the LicenseAgreementDlg the verbose log should tell you what it's actually doing at that point. I'd wager that's a good place to look. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 27 January 2011 15:04 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Skipped Custom UI? I have a WiX Custom UI that I have converted from 2.0 source. The problem I am experiencing and would like a little help with is that the Dialog is not showing up when I run the .msi script. I have used Orca and I can see the Dialog in the .msi file but for some reason it is not getting called. I would like to have this Dialog scheduled right after the license agreement (which is what the 2.0 code did). Any hints as to where in the verbose log I could look to start seeing clues as to why this Dialog is not being called? Any hints as to the differences between 2.0 and 3.x that would cause the UI to be skipped? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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
Re: [WiX-users] Skipped Custom UI?
I am looking at http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm and I see the instructions, Copy the full contents of the Fragment/ defined in WixUI_InstallDir.wxs in the WiX source code to your project.. I am not sure where to get the source all of the source from SourceForge seems to have .n or .txt license agreements but I cannot find any .wxs files. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 27, 2011 10:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? So you're using WiXUI_Minimal also defining the exact same dialogs in your own code? That'll work well. I suggest re-reading the links I posted on Tuesday (subject Re: [WiX-users] Build failed?) for the UI. The answers are in the documentation Neil S's blog which you've been supplied with once already. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 27 January 2011 15:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? I see 'Doing action: WelcomeEulaDlg' but I don't see anything about LicenseAgreementDlg. Maybe it is changed names and that is why I don't see the dialog. I have code like Fragment UIRef Id=WixUI_Minimal/ UIRef Id=WixUI_ErrorProgressText/ UI DialogRef Id=WelcomeEulaDlg / Property Id=WelcomeEulaDlg_Install Value=PropertiesDlg / Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 27, 2011 9:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Skipped Custom UI? Have you Published the required Control event to show your Custom Dialog to the Next button in the LicenseAgreementDlg? When you click the Next button in the LicenseAgreementDlg the verbose log should tell you what it's actually doing at that point. I'd wager that's a good place to look. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 27 January 2011 15:04 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Skipped Custom UI? I have a WiX Custom UI that I have converted from 2.0 source. The problem I am experiencing and would like a little help with is that the Dialog is not showing up when I run the .msi script. I have used Orca and I can see the Dialog in the .msi file but for some reason it is not getting called. I would like to have this Dialog scheduled right after the license agreement (which is what the 2.0 code did). Any hints as to where in the verbose log I could look to start seeing clues as to why this Dialog is not being called? Any hints as to the differences between 2.0 and 3.x that would cause the UI to be skipped? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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] ServiceInstall failure?
It seems that the default behavior for this code ServiceInstall Id=BsiServiceInstall DisplayName=BsiServices Host Name=ServiceExeFile Description=Windows Service host for Bsi Web Services Interactive=no Account=[SERVICEUSER] Password=[SERVICEPASSWORD] ErrorControl=normal Start=demand Type=ownProcess Vital=yes / ServiceControl Id=BsiServiceControl Name=ServiceExeFile Start=install Stop=uninstall Remove=uninstall Wait=yes / Is to repeatedly try, even when the password is invalid, until the account specified is locked out. I was wondering if there was a way to catch the first error and display it to the user. Also I would like to associate some sort of progress bar with the installation and starting of this service. Is there a good reference for this type of function? Thank you. Kevin -- 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
Re: [WiX-users] Where is DesktopFolder?
But that is a DirectoryRef. The way I understood it is this should reference
DesktopFolder not define it.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, January 26, 2011 10:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
Yes you do have a directory with Id=DesktopFolder.
DirectoryRef Id=DesktopFolder
A cursory search for Id=DesktopFolder found that in seconds in your code.
That should be Directory not DirectoryRef which is what the error is telling
you. You're trying to reference something which doesn't exist as far as your
code is concerned.
I would suggest looking into contracting out your installation development if
basic things like this are tripping you up to the extent that you're asking the
list users for help.
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: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: 26 January 2011 15:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
No, I don't have a directory with Id=DesktopFolder. I have included the WiX
source that I am using below (sorry about the length but I it looks like I
cannot attached a file) The applicable source is toward the end.
I still get the error:
C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServic
es\Product.wxs(318,0): error LGHT0094: Unresolved reference to symbol
'Directory:DesktopFolder' in section
'Product:{8D768A77-71B5-432F-86F2-BCD197617A79}'.
Thank you.
Kevin
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, January 26, 2011 1:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
DesktopFolder has been part of the Windows Installer as long as I can remember.
I don't htink this is the problem.
Kevin, do you have a Directory with Id=DesktopFolder?
On Tue, Jan 25, 2011 at 3:38 PM, Chris Lord
chris.l...@atterotech.commailto:chris.l...@atterotech.comwrote:
Kevin,
What version of Windows Installer that is installed on your machine
has absolutely no effect when you are building the MSI. This is not
the version you are targeting but what your machine happens to be
using.
The reason I asked about what version you are targeting is that one
possible reason for the problem is that WiX is trying to create an
Installer based around features for an earlier version of Windows
Installer. If thats the case, the DesktopFolder feature won't exist
as it was introduced in Windows Installer 4 and hence the error.
Unless this installer is purely for you, everyone else who may install
your MSI may not have your version of OS and your version of Windows
Installer and if a users PC has a version of Windows installer that
doesn't support your feature then that will spell trouble.
Your MSI should target a version of windows installer that supports
the feature you are using that means setting the InstallerVersion key
which is part of your package data in WiX.
For version 4, it needs to be at least 400. Be mindful though that
newer versions of Windows Installer may not be supported on older
operating systems so by setting it to a higher version, you may be
limit the OS's the MSI can be installed upon.
Chris
On 01/25/2011 05:32 PM, Kevin Burton wrote:
If I invoke msiexec it says that I am using Windows (r) Installer. V
5.0.7600.16385.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.commailto:kev...@buyseasons.com
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Tuesday, January 25, 2011 2:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
Kevin
What version of windows installer are you targeting. Looks like
this
parameter is only available in Windows Installer 4 and onwards.
http://msdn.microsoft.com/en-us/library/aa368276%28v=vs.85%29.aspx
Chris
On 01/25/2011 03:34 PM, Kevin Burton wrote:
I am trying to reference DesktopFolder and I get the error:
C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServic
es\Product.wxs(318,0):
error LGHT0094: Unresolved reference to symbol
'Directory:DesktopFolder' in section
'Product:{8D768A77-71B5
Re: [WiX-users] Where is DesktopFolder?
When I change the DirectoryRef to Directory I get two errors:
Directory with Id 'DesktopFolder' is not a valid root directory. There may
only be a single root directory per product or module and its Id attribute
value must be 'TARGETDIR' and its Name attribute value must be 'SourceDir'.
The Directory element requires the Name attribute because there is no parent
Directory element.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, January 26, 2011 10:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
Yes you do have a directory with Id=DesktopFolder.
DirectoryRef Id=DesktopFolder
A cursory search for Id=DesktopFolder found that in seconds in your code.
That should be Directory not DirectoryRef which is what the error is telling
you. You're trying to reference something which doesn't exist as far as your
code is concerned.
I would suggest looking into contracting out your installation development if
basic things like this are tripping you up to the extent that you're asking the
list users for help.
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: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: 26 January 2011 15:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
No, I don't have a directory with Id=DesktopFolder. I have included the WiX
source that I am using below (sorry about the length but I it looks like I
cannot attached a file) The applicable source is toward the end.
I still get the error:
C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServic
es\Product.wxs(318,0): error LGHT0094: Unresolved reference to symbol
'Directory:DesktopFolder' in section
'Product:{8D768A77-71B5-432F-86F2-BCD197617A79}'.
Thank you.
Kevin
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, January 26, 2011 1:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
DesktopFolder has been part of the Windows Installer as long as I can remember.
I don't htink this is the problem.
Kevin, do you have a Directory with Id=DesktopFolder?
On Tue, Jan 25, 2011 at 3:38 PM, Chris Lord
chris.l...@atterotech.commailto:chris.l...@atterotech.comwrote:
Kevin,
What version of Windows Installer that is installed on your machine
has absolutely no effect when you are building the MSI. This is not
the version you are targeting but what your machine happens to be
using.
The reason I asked about what version you are targeting is that one
possible reason for the problem is that WiX is trying to create an
Installer based around features for an earlier version of Windows
Installer. If thats the case, the DesktopFolder feature won't exist
as it was introduced in Windows Installer 4 and hence the error.
Unless this installer is purely for you, everyone else who may install
your MSI may not have your version of OS and your version of Windows
Installer and if a users PC has a version of Windows installer that
doesn't support your feature then that will spell trouble.
Your MSI should target a version of windows installer that supports
the feature you are using that means setting the InstallerVersion key
which is part of your package data in WiX.
For version 4, it needs to be at least 400. Be mindful though that
newer versions of Windows Installer may not be supported on older
operating systems so by setting it to a higher version, you may be
limit the OS's the MSI can be installed upon.
Chris
On 01/25/2011 05:32 PM, Kevin Burton wrote:
If I invoke msiexec it says that I am using Windows (r) Installer. V
5.0.7600.16385.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.commailto:kev...@buyseasons.com
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Tuesday, January 25, 2011 2:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
Kevin
What version of windows installer are you targeting. Looks like
this
parameter is only available in Windows Installer 4 and onwards.
http://msdn.microsoft.com/en-us/library/aa368276%28v=vs.85%29.aspx
Chris
On 01/25/2011 03:34 PM, Kevin Burton wrote:
I am trying to reference DesktopFolder and I get the error:
C:\Projects\BuySeasonsIT\Source
Re: [WiX-users] Where is DesktopFolder?
So what does it mean to have DesktopFolder underneath the TARGETDIR. That is
certainly not the hierarchy that is on my computer.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, January 26, 2011 5:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
The first error tells you what you must do.
There may only be a single root directory per product or module and its Id
attribute value must be 'TARGETDIR' and its Name attribute value must be
'SourceDir'.
I assume you already have one of these otherwise you would not be able to
install any files:
Directory Id=TARGETDIR Name=SourceDir
/Directory
You have two options:
1) Add the Directory/ declaration for DesktopFolder in the existing TARGETDIR
Directory/
Directory Id=TARGETDIR Name=SourceDir
Directory Id=DesktopFolder /
/Directory
2) Add the Directory/ declaration for DesktopFolder under a DirectoryRef/
for TARGETDIR
DirectoryRef Id=TARGETDIR
Directory Id=DesktopFolder /
/DirectoryRef
All errors I see already tell you what to do... just read them more carefully.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, January 26, 2011 10:09 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Where is DesktopFolder?
When I change the DirectoryRef to Directory I get two errors:
Directory with Id 'DesktopFolder' is not a valid root directory.
There may only be a single root directory per product or module and
its Id attribute value must be 'TARGETDIR' and its Name attribute value must
be 'SourceDir'.
The Directory element requires the Name attribute because there is no
parent Directory element.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, January 26, 2011 10:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
Yes you do have a directory with Id=DesktopFolder.
DirectoryRef Id=DesktopFolder
A cursory search for Id=DesktopFolder found that in seconds in your code.
That should be Directory not DirectoryRef which is what the error is
telling you. You're trying to reference something which doesn't exist
as far as your code is concerned.
I would suggest looking into contracting out your installation
development if basic things like this are tripping you up to the
extent that you're asking the list users for help.
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: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: 26 January 2011 15:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
No, I don't have a directory with Id=DesktopFolder. I have included
the WiX source that I am using below (sorry about the length but I it
looks like I cannot attached a file) The applicable source is toward the end.
I still get the error:
C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServ
i
c
es\Product.wxs(318,0): error LGHT0094: Unresolved reference to symbol
'Directory:DesktopFolder' in section
'Product:{8D768A77-71B5-432F-86F2-
BCD197617A79}'.
Thank you.
Kevin
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, January 26, 2011 1:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
DesktopFolder has been part of the Windows Installer as long as I can
remember. I don't htink this is the problem.
Kevin, do you have a Directory with Id=DesktopFolder?
On Tue, Jan 25, 2011 at 3:38 PM, Chris Lord
chris.l...@atterotech.commailto:chris.l...@atterotech.comwrote:
Kevin,
What version of Windows Installer that is installed on your machine
has absolutely no effect when you are building the MSI. This is not
the version you are targeting but what your machine happens to be
using.
The reason I asked about what version you are targeting is that one
possible reason for the problem is that WiX is trying to create an
Installer based around features for an earlier version of Windows
Installer. If thats the case, the DesktopFolder feature won't
Re: [WiX-users] Password?
Thank you. I had the installer version set to 100. Changing it to 300 eliminated the warning. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 25, 2011 1:25 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Password? Just guess but what have you got Package/@InstallerVersion set to? I think the password attribute wasn't used until Windows Installer v2 so this would need to be at least 200. Neil -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 07:09 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Password? I have some WiX code that from 2.0 that looks like: Control Id=PasswordEdit Type=Edit X=114 Y=62 Width=150 Height=18 Property=SERVICEPASSWORD Password=yes / This gives me a warning: C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServic es\PropertiesDialog.wxs(30,0): warning LGHT1076: ICE45: Row 'PropertiesDlg.PasswordEdit' in table 'Control' has bits set in the 'Attributes' column that are not used in the schema of the package, but are used in a later schema. Your package can run on systems where this attribute has no effect. If I change it to (removing the Password attribute): Control Id=PasswordEdit Type=Edit X=114 Y=62 Width=150 Height=18 Property=SERVICEPASSWORD/ The warning goes away. What is the warning telling me? I would like a password text field. What is the equivalent syntax for 3.0? Thank you. Kevin -- 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
Re: [WiX-users] WixProj?
I still get an error page. The full text is: An error has been encountered in accessing this page. 1. Server: wix.sourceforge.net 2. URL path: /manual-wix3/authoring_first_msbuild_project.h 3. Error notes: NONE 4. Error type: 404 5. Request method: GET 6. Request query string: NONE 7. Time: 2011-01-25 14:12:28 UTC (1295964748) Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net). If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above): Contact the project via their designated support resources. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page for their usernames) at user-n...@users.sourceforge.net If you are a maintainer of this web content, please refer to the Site Documentation regarding web services for further assistance. NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name .htaccess with this line: Options +Indexes Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 25, 2011 1:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? It is definitely there - the url may have word wrapped, the page end .htm. Same topic is in the help file Creating a .wixproj File. Neil -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 24 January 2011 23:29 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? I tried to access this page and I got: An error has been encountered in accessing this page. . . . . . Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, January 24, 2011 3:48 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? Have you seen this: http://wix.sourceforge.net/manual-wix3/authoring_first_msbuild_project.h tm Neil -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 24 January 2011 19:10 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WixProj? The documentation states: The easiest way to create a new .wixproj for your installer is to WiX in Visual Studio because it automatically generates standard msbuild project files I have a project file that I have been using for a number of years with WiX 2.0. I want to convert the project file to use WiX 3.0 libraries as well as the converted .wxs file. My project currecntly looks like: Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003; DefaultTargets=Build PropertyGroup Configuration Condition=$(Condition)==''Release/Configuration PackageRoot Condition=$(PackageRoot)==''..\PACKAGE\/PackageRoot IntermediateOutputPath Condition=$(IntermediateOutputPath)==''$(PackageRoot)WiX_Temp\$(Confi guration)\/IntermediateOutputPath OutputPath Condition=$(OutputPath)==''$(PackageRoot)$(Configuration)\/OutputPat h /PropertyGroup !-- -- UsingTask TaskName=BuySeasons.WebServices.SqlBuildTasks.StoredProcedureScript AssemblyFile=Source\Tools\SqlBuildTasks\bin\Debug\SqlBuildTasks.dll/ UsingTask TaskName=BuySeasons.WebServices.SqlBuildTasks.TableScript AssemblyFile=Source\Tools\SqlBuildTasks\bin\Debug\SqlBuildTasks.dll/ UsingTask TaskName=BuySeasons.WebServices.SqlBuildTasks.TriggerScript AssemblyFile=Source\Tools\SqlBuildTasks\bin\Debug\SqlBuildTasks.dll/ !--=== These must be declared BEFORE the statement that imports the wix.targets file ==-- PropertyGroup !-- The location pointing where WiX is installed -- ToolPathC:\Program Files\WiX\/ToolPath !-- Required Property by WiX -- OutputName Condition=$(OutputName)=='' $(Configuration)BsiServices/OutputName !-- Required property by WiX -- OutputType Condition=$(OutputType)=='' package/OutputType !-- Input path to source files -- BaseInputPath Condition=$(BaseInputPath)==''$(PackageRoot)$(Configuration)/BaseInp utPath DefineConstantsConfiguration=$(Configuration)/DefineConstants /PropertyGroup ItemGroup !-- Required WiX item. Files in this item are sent to the Candle tool. -- Compile Include=$(BaseInputPath)\BsiServices.wxs/ /ItemGroup PropertyGroup !-- Required to display strings in proper localized form
Re: [WiX-users] Build failed?
I have included a WiX project with my solution and I am using Visual Studio 2010. I have added a reference to WixUIExtension, WixUtilExtension, and WixNetFxExtension. If it helps I have attached the full source of the dialog as well as the 'main' .wxs. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Blair [mailto:os...@live.com] Sent: Tuesday, January 25, 2011 1:46 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Build failed? How are you building your UI? Are you using WixUIExtension? -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Monday, January 24, 2011 3:49 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Build failed? I am trying to build a WiX project that 'includes' a fragment. But I am getting an error: C:\Documents and Settings\kevinb\Local Settings\Temp\1\tik5wou0\BsiServices.msi(0,0): error LGHT0204: ICE31: The 'DefaultUIFont' Property must be set to a valid TextStyle in the Property table. I could not find an instance of DefaultUIFont or TextStyle in any of the .wxs files in the project. I am not sure where this is coming from? Kevin -- 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
Re: [WiX-users] WixProj?
Thank you. That is the same page that I referenced earlier in this thread. My question is about the quote in this article that states: The easiest way to create a new .wixproj for your installer is to WiX in Visual Studio because it automatically generates standard msbuild project files I am not sure how to take a 2.0 proj file and move it to 3.0 using the easiest way. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 25, 2011 9:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? The url is split in the email, make sure it ends .htm (see 2 in your reply). -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 14:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? I still get an error page. The full text is: An error has been encountered in accessing this page. 1. Server: wix.sourceforge.net 2. URL path: /manual-wix3/authoring_first_msbuild_project.h 3. Error notes: NONE 4. Error type: 404 5. Request method: GET 6. Request query string: NONE 7. Time: 2011-01-25 14:12:28 UTC (1295964748) Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net). If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above): Contact the project via their designated support resources. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page for their usernames) at user-n...@users.sourceforge.net If you are a maintainer of this web content, please refer to the Site Documentation regarding web services for further assistance. NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name .htaccess with this line: Options +Indexes Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 25, 2011 1:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? It is definitely there - the url may have word wrapped, the page end .htm. Same topic is in the help file Creating a .wixproj File. Neil -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 24 January 2011 23:29 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? I tried to access this page and I got: An error has been encountered in accessing this page. . . . . . Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, January 24, 2011 3:48 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? Have you seen this: http://wix.sourceforge.net/manual-wix3/authoring_first_msbuild_project.h tm Neil -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 24 January 2011 19:10 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WixProj? The documentation states: The easiest way to create a new .wixproj for your installer is to WiX in Visual Studio because it automatically generates standard msbuild project files I have a project file that I have been using for a number of years with WiX 2.0. I want to convert the project file to use WiX 3.0 libraries as well as the converted .wxs file. My project currecntly looks like: Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003; DefaultTargets=Build PropertyGroup Configuration Condition=$(Condition)==''Release/Configuration PackageRoot Condition=$(PackageRoot)==''..\PACKAGE\/PackageRoot IntermediateOutputPath Condition=$(IntermediateOutputPath)==''$(PackageRoot)WiX_Temp\$(Confi guration)\/IntermediateOutputPath OutputPath Condition=$(OutputPath)==''$(PackageRoot)$(Configuration)\/OutputPat h /PropertyGroup !-- -- UsingTask TaskName=BuySeasons.WebServices.SqlBuildTasks.StoredProcedureScript AssemblyFile=Source\Tools\SqlBuildTasks\bin\Debug\SqlBuildTasks.dll/ UsingTask TaskName=BuySeasons.WebServices.SqlBuildTasks.TableScript AssemblyFile=Source\Tools\SqlBuildTasks\bin\Debug\SqlBuildTasks.dll/ UsingTask TaskName=BuySeasons.WebServices.SqlBuildTasks.TriggerScript AssemblyFile=Source\Tools\SqlBuildTasks\bin\Debug\SqlBuildTasks.dll
Re: [WiX-users] Build failed?
So where is this declaration? What should it be? Where do I see the stock WiXUIs? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 8:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? You can't attach stuff to list replies. If you've Customized your UI you need to declare the DefaultUIFont Property same as the stock WiXUI's do. See the source for any of the WiXUI's (e.g src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs). 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 14:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? I have included a WiX project with my solution and I am using Visual Studio 2010. I have added a reference to WixUIExtension, WixUtilExtension, and WixNetFxExtension. If it helps I have attached the full source of the dialog as well as the 'main' .wxs. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Blair [mailto:os...@live.com] Sent: Tuesday, January 25, 2011 1:46 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Build failed? How are you building your UI? Are you using WixUIExtension? -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Monday, January 24, 2011 3:49 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Build failed? I am trying to build a WiX project that 'includes' a fragment. But I am getting an error: C:\Documents and Settings\kevinb\Local Settings\Temp\1\tik5wou0\BsiServices.msi(0,0): error LGHT0204: ICE31: The 'DefaultUIFont' Property must be set to a valid TextStyle in the Property table. I could not find an instance of DefaultUIFont or TextStyle in any of the .wxs files in the project. I am not sure where this is coming from? Kevin -- 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 -- 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
Re: [WiX-users] Build failed?
I have added a reference to WixUIExtension.dll and it is still not pulling the definition in. What should I manually declare it to be? Under download for Wix there is WiX35.msi but I couldn't find any .wxs source. Under http://wix.codeplex.com/ Source Code there is a link to download the latest version but it is a zip file that doesn't contain any .wxs. If you have the manual declaration would you mind sharing it? Is there documentation on how to create a custom UI? This worked for 2.0 but it must of changed for 3.0. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 10:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? 1 - In the WiXUI sets. 2 - In your installer that's what the error is saying. It should be either pulled from WiXUIExtension.dll or manually declared by you if you are using a customized version of a WiXUI set as previously stated. 3 - Surprisingly in the source code like I also stated previously. The sources are available from the same place you download the binaries. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 16:12 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? So where is this declaration? What should it be? Where do I see the stock WiXUIs? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 8:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? You can't attach stuff to list replies. If you've Customized your UI you need to declare the DefaultUIFont Property same as the stock WiXUI's do. See the source for any of the WiXUI's (e.g src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs). 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 14:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? I have included a WiX project with my solution and I am using Visual Studio 2010. I have added a reference to WixUIExtension, WixUtilExtension, and WixNetFxExtension. If it helps I have attached the full source of the dialog as well as the 'main' .wxs. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Blair [mailto:os...@live.com] Sent: Tuesday, January 25, 2011 1:46 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Build failed? How are you building your UI? Are you using WixUIExtension? -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Monday, January 24, 2011 3:49 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Build failed? I am trying to build a WiX project that 'includes' a fragment. But I am getting an error: C:\Documents and Settings\kevinb\Local Settings\Temp\1\tik5wou0\BsiServices.msi(0,0): error LGHT0204: ICE31: The 'DefaultUIFont' Property must be set to a valid TextStyle in the Property table. I could not find an instance of DefaultUIFont or TextStyle in any of the .wxs files in the project. I am not sure where this is coming from? Kevin -- 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
[WiX-users] Uninstall shortcut?
The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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
Re: [WiX-users] WixProj?
I ran WixCop on the single .wxs file that I had. No errors reported. But the custom dialog that I created never gets called. Is this a problem with .xs or .wixproj? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 10:39 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? Easiest way? Install WiX v3.5.2519.0, upgrade all your .wxs files using WiXCop.exe then create a new .wixproj add them to it. Alternatively, upgrade to WiX v3.5.2519.0, open your solution hope for the best. If that fails see above. Votive in WiX v2.0 was very experimental not ready for production use. WiX v3.0 was the first version it was recommended for use so you find yourself in a situation no one else has as you're using a version which as been superseded for 18 months plus. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 16:10 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? Thank you. That is the same page that I referenced earlier in this thread. My question is about the quote in this article that states: The easiest way to create a new .wixproj for your installer is to WiX in Visual Studio because it automatically generates standard msbuild project files I am not sure how to take a 2.0 proj file and move it to 3.0 using the easiest way. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 25, 2011 9:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? The url is split in the email, make sure it ends .htm (see 2 in your reply). -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 14:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? I still get an error page. The full text is: An error has been encountered in accessing this page. 1. Server: wix.sourceforge.net 2. URL path: /manual-wix3/authoring_first_msbuild_project.h 3. Error notes: NONE 4. Error type: 404 5. Request method: GET 6. Request query string: NONE 7. Time: 2011-01-25 14:12:28 UTC (1295964748) Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net). If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above): Contact the project via their designated support resources. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page for their usernames) at user-n...@users.sourceforge.net If you are a maintainer of this web content, please refer to the Site Documentation regarding web services for further assistance. NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name .htaccess with this line: Options +Indexes Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 25, 2011 1:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? It is definitely there - the url may have word wrapped, the page end .htm. Same topic is in the help file Creating a .wixproj File. Neil -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 24 January 2011 23:29 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? I tried to access this page and I got: An error has been encountered in accessing this page. . . . . . Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, January 24, 2011 3:48 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WixProj? Have you seen this: http://wix.sourceforge.net/manual-wix3/authoring_first_msbuild_project.h tm Neil
Re: [WiX-users] Uninstall shortcut?
The documentation had a registry entry: RegistryValue Root=HKCU Key=Software\Microsoft\MyApplicationName Name=installed Type=integer Value=1 KeyPath=yes/ Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? What Registry Entry are you referring to? In that entire sample there is but one RegistryValue which is simply a stub entry used as a KeyPath for a component. It appears you're missing the entire point of that How To guide. The purpose is to create a clickable shortcut which will uninstall your product. The sample code shows how to do that place the shortcut under the Start Menu entry for the sample product. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 17:14 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Uninstall shortcut? The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c,00,54,00, 65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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
Re: [WiX-users] Uninstall shortcut?
I am sorry I don't know what trolling is? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 11:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? You must be trolling. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 17:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? The documentation had a registry entry: RegistryValue Root=HKCU Key=Software\Microsoft\MyApplicationName Name=installed Type=integer Value=1 KeyPath=yes/ Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? What Registry Entry are you referring to? In that entire sample there is but one RegistryValue which is simply a stub entry used as a KeyPath for a component. It appears you're missing the entire point of that How To guide. The purpose is to create a clickable shortcut which will uninstall your product. The sample code shows how to do that place the shortcut under the Start Menu entry for the sample product. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 17:14 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Uninstall shortcut? The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c,00,54,00, 65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- 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
Re: [WiX-users] Build failed?
I put the code all in one .wxs and it compiles fine but when I run it (the .msi) the custom dialog is skipped. Something else has changed from 2.0 to 3.0. Again I have attached the .wxs that I am using if you would be so kind as to look at it. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 11:34 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? weekly releases contain the sources - http://wix.sourceforge.net/releases/ Documentation on the UI is at the following links (they may wrap across lines, you have been warned) http://wix.sourceforge.net/manual-wix3/WixUI_dialog_library.htm http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm Neil Sleightholm wrote a pretty good blog page on this subject before the 2nd of the above links existed http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 17:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? I have added a reference to WixUIExtension.dll and it is still not pulling the definition in. What should I manually declare it to be? Under download for Wix there is WiX35.msi but I couldn't find any .wxs source. Under http://wix.codeplex.com/ Source Code there is a link to download the latest version but it is a zip file that doesn't contain any .wxs. If you have the manual declaration would you mind sharing it? Is there documentation on how to create a custom UI? This worked for 2.0 but it must of changed for 3.0. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 10:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? 1 - In the WiXUI sets. 2 - In your installer that's what the error is saying. It should be either pulled from WiXUIExtension.dll or manually declared by you if you are using a customized version of a WiXUI set as previously stated. 3 - Surprisingly in the source code like I also stated previously. The sources are available from the same place you download the binaries. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 16:12 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? So where is this declaration? What should it be? Where do I see the stock WiXUIs? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 8:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? You can't attach stuff to list replies. If you've Customized your UI you need to declare the DefaultUIFont Property same as the stock WiXUI's do. See the source for any of the WiXUI's (e.g src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs). 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 14:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build failed? I have included a WiX project with my solution and I am using Visual Studio 2010. I have added a reference to WixUIExtension, WixUtilExtension, and WixNetFxExtension. If it helps I have attached the full source of the dialog as well as the 'main' .wxs. Kevin Burton Senior Software Engineer BUYSEASONS 262
Re: [WiX-users] Uninstall shortcut?
If I look in the registry I don't see my company's name or the application name. I did a find for the whole registry hive. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Blair [mailto:os...@live.com] Sent: Tuesday, January 25, 2011 12:07 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Uninstall shortcut? doing-something-against-my-better-judgment http://en.wikipedia.org/wiki/Troll_(Internet) RegistryValue Root=HKCU Key=Software\Microsoft\MyApplicationName Name=installed Type=integer Value=1 KeyPath=yes/ Replace Microsoft with your company's name, and MyApplicationName with your product's name. HKCU\Software\Microsoft\Installer\Products is undocumented data for Windows Installer's use only. /doing-something-against-my-better-judgment -Blair -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 9:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? I am sorry I don't know what trolling is? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 11:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? You must be trolling. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 17:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? The documentation had a registry entry: RegistryValue Root=HKCU Key=Software\Microsoft\MyApplicationName Name=installed Type=integer Value=1 KeyPath=yes/ Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, January 25, 2011 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? What Registry Entry are you referring to? In that entire sample there is but one RegistryValue which is simply a stub entry used as a KeyPath for a component. It appears you're missing the entire point of that How To guide. The purpose is to create a clickable shortcut which will uninstall your product. The sample code shows how to do that place the shortcut under the Start Menu entry for the sample product. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 25 January 2011 17:14 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Uninstall shortcut? The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c,00,54,00, 65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A867D85B17F23 4682FCB1D7916A797
Re: [WiX-users] Uninstall shortcut?
I haven't tried the example but based on other installed applications it seems that the registry settings that the example is using are not right. I didn't want to run an example that didn't meet the sniff test especially when modifying the registry. The sniff test for me was looking at other installed applications and seeing what registry settings they establish. So unless WiX has some special registry settings it seems that these registry settings are incorrect. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 12:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? Are you saying that the example doesn't work? In what way does it fail? From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 5:14 PM The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_sho rtcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c ,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 -- 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
Re: [WiX-users] Uninstall shortcut?
As far as I can tell the RegistryValue is not used. What is the purpose of the registry value? I have installed a WiX generated .msi file and it did not add any such registry entry. The shortcut that was generated does not refer to the Registry at all. Here is the code that I used. DirectoryRef Id=BsiServicesFolder Component Id=ApplicationShortcut Guid=536EBF29-1507-4246-B0EA-BEA60B76879C Shortcut Id=UninstallProduct Name=Uninstall BsiServices Description=Uninstalls The Brain Target=[System64Folder]msiexec.exe Arguments=/x [ProductCode]/ RemoveFolder Id=SERVICEINSTALLDIR On=uninstall/ RemoveFolder Id=WPFINSTALLDIR On=uninstall/ RemoveFolder Id=INSTALLATIONINSTALLDIR On=uninstall/ RegistryValue Root=HKCU Key=Software\[Manufacturer]\[ProductName] Name=installed Type=integer Value=1 KeyPath=yes/ /Component /DirectoryRef -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 12:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? Are you saying that the example doesn't work? In what way does it fail? From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 5:14 PM The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_sho rtcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c ,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 -- 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] Where is DesktopFolder?
I am trying to reference DesktopFolder and I get the error:
C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServices\Product.wxs(318,0):
error LGHT0094: Unresolved reference to symbol 'Directory:DesktopFolder' in
section 'Product:{8D768A77-71B5-432F-86F2-BCD197617A79}'.
Any idea on how to use the desktop?
Kevin
--
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
Re: [WiX-users] Uninstall shortcut?
I think I figured it out. I was confused since this link was about adding a shortcut I thought that the registry value had something to do with adding a remove shortcut. Which after some experimentation I found that the registry key has nothing to do with. What are the ICE test that you refer to? Looking at this page http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut.htm I see no reference to ICE tests. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 2:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? In what sense is it not right? It's a registry key private to your installer which the example creates to meet the requirements of the ICE tests, as explained in the documentation. If you consider the path or name not right use different ones, as others have already suggested. I wouldn't go anywhere near Windows Installer's private entries such as the ones you quoted though. From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 7:13 PM I haven't tried the example but based on other installed applications it seems that the registry settings that the example is using are not right. I didn't want to run an example that didn't meet the sniff test especially when modifying the registry. The sniff test for me was looking at other installed applications and seeing what registry settings they establish. So unless WiX has some special registry settings it seems that these registry settings are incorrect. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 12:16 PM Are you saying that the example doesn't work? In what way does it fail? From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 5:14 PM The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_sho rtcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c ,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 -- 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
Re: [WiX-users] Uninstall shortcut?
One more thing based on the code modified below: DirectoryRef Id=BsiServicesFolder Component Id=ApplicationShortcut Guid=536EBF29-1507-4246-B0EA-BEA60B76879C Shortcut Id=UninstallProduct Name=Uninstall BsiServices Description=Uninstalls The Brain Target=[System64Folder]msiexec.exe Arguments=/x [ProductCode]/ RemoveFolder Id=SERVICEINSTALLDIR On=uninstall/ RemoveFolder Id=WPFINSTALLDIR On=uninstall/ RemoveFolder Id=INSTALLATIONINSTALLDIR On=uninstall/ RegistryValue Root=HKCU Key=Software\[Manufacturer]\[ProductName] Name=installed Type=integer Value=1 KeyPath=yes/ /Component /DirectoryRef I get a warning C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServices\Product.wxs(319,0): warning LGHT1076: ICE57: Component 'ApplicationShortcut' has both per-user and per-machine data with an HKCU Registry KeyPath. Can I ignore this warning? Can I get rid of it? -Original Message- From: Kevin Burton Sent: Tuesday, January 25, 2011 3:12 PM To: General discussion for Windows Installer XML toolset. Subject: RE: Uninstall shortcut? I think I figured it out. I was confused since this link was about adding a shortcut I thought that the registry value had something to do with adding a remove shortcut. Which after some experimentation I found that the registry key has nothing to do with. What are the ICE test that you refer to? Looking at this page http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut.htm I see no reference to ICE tests. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 2:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? In what sense is it not right? It's a registry key private to your installer which the example creates to meet the requirements of the ICE tests, as explained in the documentation. If you consider the path or name not right use different ones, as others have already suggested. I wouldn't go anywhere near Windows Installer's private entries such as the ones you quoted though. From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 7:13 PM I haven't tried the example but based on other installed applications it seems that the registry settings that the example is using are not right. I didn't want to run an example that didn't meet the sniff test especially when modifying the registry. The sniff test for me was looking at other installed applications and seeing what registry settings they establish. So unless WiX has some special registry settings it seems that these registry settings are incorrect. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 12:16 PM Are you saying that the example doesn't work? In what way does it fail? From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 5:14 PM The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_sho rtcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c ,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00
Re: [WiX-users] Uninstall shortcut?
I was taking this from the online documentation. I was told that the only reason for the registry value was to satisfiy some compliance tests. If I move this registry value will it still satisfy the compliance tests? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, January 25, 2011 3:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServ i ces\Product.wxs(319,0): warning LGHT1076: ICE57: Component 'ApplicationShortcut' has both per-user and per-machine data with an HKCU Registry KeyPath. This warning is generated by ICE57. Google can find information about ICE57 easily enough. HKCU (HKEY_CURRENT_USER) registry paths are appropriate only for per-user data. The warning message itself says that the component has per-machine data which should live in HKLM (HKEY_LOCAL_MACHINE) registry paths. You have a couple of options: 1) Change the per-machine data into per-user data 2) Change the per-user data into per-machine data and use HKLM instead of HKCU. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: Tuesday, January 25, 2011 1:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? Explanation about ICE validation you find here in MSDN: http://msdn.microsoft.com/library/bb762153.aspx In short: Microsoft provides a set of Internal Consistency Evaluators, or ICEs, that can be used to detect potential problems with an MSI database. (comp http://en.wikipedia.org/wiki/Windows_Installer#ICE_validation ) 2011/1/25 Kevin Burton kev...@buyseasons.com: One more thing based on the code modified below: DirectoryRef Id=BsiServicesFolder Component Id=ApplicationShortcut Guid=536EBF29-1507-4246-B0EA-BEA60B76879C Shortcut Id=UninstallProduct Name=Uninstall BsiServices Description=Uninstalls The Brain Target=[System64Folder]msiexec.exe Arguments=/x [ProductCode]/ RemoveFolder Id=SERVICEINSTALLDIR On=uninstall/ RemoveFolder Id=WPFINSTALLDIR On=uninstall/ RemoveFolder Id=INSTALLATIONINSTALLDIR On=uninstall/ RegistryValue Root=HKCU Key=Software\[Manufacturer]\[ProductName] Name=installed Type=integer Value=1 KeyPath=yes/ /Component /DirectoryRef I get a warning C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServ i ces\Product.wxs(319,0): warning LGHT1076: ICE57: Component 'ApplicationShortcut' has both per-user and per-machine data with an HKCU Registry KeyPath. Can I ignore this warning? Can I get rid of it? -Original Message- From: Kevin Burton Sent: Tuesday, January 25, 2011 3:12 PM To: General discussion for Windows Installer XML toolset. Subject: RE: Uninstall shortcut? I think I figured it out. I was confused since this link was about adding a shortcut I thought that the registry value had something to do with adding a remove shortcut. Which after some experimentation I found that the registry key has nothing to do with. What are the ICE test that you refer to? Looking at this page http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut. ht m I see no reference to ICE tests. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 2:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? In what sense is it not right? It's a registry key private to your installer which the example creates to meet the requirements of the ICE tests, as explained in the documentation. If you consider the path or name not right use different ones, as others have already suggested. I wouldn't go anywhere near Windows Installer's private entries such as the ones you quoted though. From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 7:13 PM I haven't tried the example but based on other installed applications it seems that the registry settings that the example is using are not right. I didn't want to run an example that didn't meet the sniff test especially when modifying the registry. The sniff test for me was looking at other installed applications and seeing what
Re: [WiX-users] Uninstall shortcut?
Can I suggest that this page reference the reason for the registry value? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Tuesday, January 25, 2011 3:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? Kevin All you need to know about ICE and more http://msdn.microsoft.com/en-us/library/aa369554%28v=VS.85%29.aspx Chris On 01/25/2011 04:11 PM, Kevin Burton wrote: I think I figured it out. I was confused since this link was about adding a shortcut I thought that the registry value had something to do with adding a remove shortcut. Which after some experimentation I found that the registry key has nothing to do with. What are the ICE test that you refer to? Looking at this page http://wix.sourceforge.net/manual-wix3/create_an_uninstall_shortcut.ht m I see no reference to ICE tests. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 2:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall shortcut? In what sense is it not right? It's a registry key private to your installer which the example creates to meet the requirements of the ICE tests, as explained in the documentation. If you consider the path or name not right use different ones, as others have already suggested. I wouldn't go anywhere near Windows Installer's private entries such as the ones you quoted though. From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 7:13 PM I haven't tried the example but based on other installed applications it seems that the registry settings that the example is using are not right. I didn't want to run an example that didn't meet the sniff test especially when modifying the registry. The sniff test for me was looking at other installed applications and seeing what registry settings they establish. So unless WiX has some special registry settings it seems that these registry settings are incorrect. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 12:16 PM Are you saying that the example doesn't work? In what way does it fail? From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 5:14 PM The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_sho rtcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c ,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 -- 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
Re: [WiX-users] Where is DesktopFolder?
If I invoke msiexec it says that I am using Windows (r) Installer. V
5.0.7600.16385.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Tuesday, January 25, 2011 2:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
Kevin
What version of windows installer are you targeting. Looks like this parameter
is only available in Windows Installer 4 and onwards.
http://msdn.microsoft.com/en-us/library/aa368276%28v=vs.85%29.aspx
Chris
On 01/25/2011 03:34 PM, Kevin Burton wrote:
I am trying to reference DesktopFolder and I get the error:
C:\Projects\BuySeasonsIT\Source\Brain\Trunk\BuyseasonsServices\BsiServices\Product.wxs(318,0):
error LGHT0094: Unresolved reference to symbol 'Directory:DesktopFolder' in
section 'Product:{8D768A77-71B5-432F-86F2-BCD197617A79}'.
Any idea on how to use the desktop?
Kevin
--
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
