Re: [WiX-users] transform creation
Why is it important to protect the registry keys with such extreme measures? There are plenty of registry keys in the system that if you modify them the whole system refuses to boot. I guess I agree that it just seems a might bit overkill to me. Templating a set of install settings into a transform to have many machines be identical is certainly seems to be a reasonable use of MST files. I'm not sure I'd do it in the general case though. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: Tuesday, July 01, 2008 21:32 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] transform creation Similarly, what would the recommended approach be for the custom properties values during a maintenance procedure (upgrade, repair, removal, etc...)? A number of folks seem to simply squirrel the settings off in the registry, then have the installation reg-search the values during maintenance ops. But I've often wondered how they would repair their installation should the registry values A) be modified or B) get totally obliterated. For that, we had decided upon the external UI / bootstrap approach that grabs all the values then generates a transform file that gets applied during installation; relying on Windows Installer to secure the transform and apply it correctly during maintenance ops to get the settings right. For fun, we also squirrel the settings away in the registry. You should see the grin on my face when internal customers decide they are registry modifying guru's and decide they know better than the install folks, hack the registry to change a setting, then realize the registry setting does nothing. Further, on a repair it gets set back to the original value. The sheer puzzled look on their face is more than satisfying to me grin/. Our normal installation process uses this approach [we haven't been bitten (to my knowledge at least) during patching scenarios to date (knock on wood)]. We had looked at the Office Customization Wizard, then decided to get real funky with an administrative installation's AdminProperties property to accomplish the dirty deed [but this approach was more for 'templat-ing' an installation to be deployed 'similarly' across many machines vs. a new installation, single machine scenario] Is there a general consensus [short of giving WiX to a user :?) ] on what a recommended course of action might be? Moving to an external UI handler to capture silly/trivial/little installation property values to accomplish the transform approach seems like a lot of dev over-kill. [Incidentally, dev's are forced down this path if they need to support multiple instances :( ]. From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Rob Mensching [EMAIL PROTECTED] Sent: Tuesday, July 01, 2008 11:04 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] transform creation 0. Modifying the MSI is not advised since that will mess with the signature. I think MST will have the same problem, but it might not if using the TRANSFORMS property (haven't tried). A tool to generate transforms makes sense (Office used to ship something just like this called Office Customization Wizard or something). Patching could get crazy. 1. Properties are the cleanest solution, except for the command-line. You could create your own bootstrapper that modified the way it took input to make this easier. 2. Orca? I've never considered giving that to an user. 3. WiX? I've considered giving that to an user. grin/ There are a lot of options here... kinda' depends on the specifics of your scenario. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Mumford Sent: Tuesday, July 01, 2008 20:57 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] transform creation I just wanted to make sure I'm not doing thing the hard way here. I'm creating an inatallation and I want my customers to be able to modify some its many properties. From what I can see they have the following options: 1. Specify a property on the command line. 2. Use Orca. 3. Use a WiX tool (like torch). These solutions have their problems: 1. Setting lots of properties means a really long command line and it's error prone. 2. Not normal-user friendly and huge download. 3. Even less user friendly than #2 since it's a developer tool. So instead I'm writing my own tool to use MSI.DLL to create a new modified MSI and/or MST. I just wanted to check that I'm not doing things the hard way here. Is this the best way to solve this problem? Thanks, Chris - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along
[WiX-users] Playing a video in the installer
Hi all, Customer wants to know if they can play a 'flash' video in the installer. I suspect it is possible but I understand I'll need to steer them to a native format for 100% compatibility (Flash has 97% of desktops I think). I've not seen anything that does this (for any format). Does anyone have any experience with videos in installers? Regards Ryan - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Protecting config files during an upgrade
Rob Mensching wrote: Am I going to have to resort to a custom action to read the settings and propagate them? If so, ugh. It seems like there should be a WiX custom action for simply reading the contents of an XML file (value or attribute) and putting the value into a property. Open feature request that no one has had time to write. Care to write it? This would fall into the bucket of sure, when I have time, but my C++ skills may not be up to the task. Looks like you've got some library functions already written that would make it fairly easy though. If I get to it, I'll contact you about what I need to do to submit the code for inclusion into the project. In the meantime, since it looks like I'll need to rely on a custom action, I can code a DTF custom action to do what I want. As a reminder, I'm wanting to: * Read the user's app.config file, if it has already been installed * Get the settings out of the config file set during the initial installation * Restore those settings to the newly-installed config file Furthermore, I only want to do this in the update, reinstall, or repair case. My code to set the config values during the initial installation works great; I just need to preserve those settings should the user ever repair, reinstall, or apply an update (which I'm implementing as a reinstall with an updated .msi). What I'm looking for is some guidance about how to use my custom action. My instincts tell me to perform a FileSearch for the config file and set a custom property if the file exists; schedule the harvest settings custom action before InstallFiles; and within the custom action code, harvest the settings if the custom property is actually set. Are my instincts correct or is there a better way? For my own education about Windows Installer and WiX, I have a few other questions that the SDK docs aren't clear to me on: Should I be trying to conditionally schedule the custom action to only run during reinstall? If so, what properties should I be checking (checking REINSTALLMODE for the value vomus seems fragile to me)? How do you conditionally schedule a custom action anyway (neither the CustomAction nor the Custom elements support a Condition element)? - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Protecting config files during an upgrade
This is one of the pain points in switching from InstallShield ( which has had an AppSearch/XMLLocator extension pattern for years ) to WiX. Implementing this pattern in DTF would be pretty easy. Fully writing it as a WiX C++ CA/Extension would be a lot more work but it really needs to get done.I'd love to do it, but my C++ skills, well, suck. --- On Wed, 7/2/08, Evans, Jim [EMAIL PROTECTED] wrote: From: Evans, Jim [EMAIL PROTECTED] Subject: Re: [WiX-users] Protecting config files during an upgrade To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Wednesday, July 2, 2008, 7:28 AM Rob Mensching wrote: Am I going to have to resort to a custom action to read the settings and propagate them? If so, ugh. It seems like there should be a WiX custom action for simply reading the contents of an XML file (value or attribute) and putting the value into a property. Open feature request that no one has had time to write. Care to write it? This would fall into the bucket of sure, when I have time, but my C++ skills may not be up to the task. Looks like you've got some library functions already written that would make it fairly easy though. If I get to it, I'll contact you about what I need to do to submit the code for inclusion into the project. In the meantime, since it looks like I'll need to rely on a custom action, I can code a DTF custom action to do what I want. As a reminder, I'm wanting to: * Read the user's app.config file, if it has already been installed * Get the settings out of the config file set during the initial installation * Restore those settings to the newly-installed config file Furthermore, I only want to do this in the update, reinstall, or repair case. My code to set the config values during the initial installation works great; I just need to preserve those settings should the user ever repair, reinstall, or apply an update (which I'm implementing as a reinstall with an updated .msi). What I'm looking for is some guidance about how to use my custom action. My instincts tell me to perform a FileSearch for the config file and set a custom property if the file exists; schedule the harvest settings custom action before InstallFiles; and within the custom action code, harvest the settings if the custom property is actually set. Are my instincts correct or is there a better way? For my own education about Windows Installer and WiX, I have a few other questions that the SDK docs aren't clear to me on: Should I be trying to conditionally schedule the custom action to only run during reinstall? If so, what properties should I be checking (checking REINSTALLMODE for the value vomus seems fragile to me)? How do you conditionally schedule a custom action anyway (neither the CustomAction nor the Custom elements support a Condition element)? - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Playing a video in the installer
There isn't any built-in MSI control that could do that. An external UI handler certainly could but your setup design is going to get way more complicated then you probably have the time or desire for. 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 --- On Wed, 7/2/08, Ryan O'Neill [EMAIL PROTECTED] wrote: From: Ryan O'Neill [EMAIL PROTECTED] Subject: [WiX-users] Playing a video in the installer To: 'General discussion for Windows Installer XML toolset.' wix-users@lists.sourceforge.net Date: Wednesday, July 2, 2008, 5:59 AM Hi all, Customer wants to know if they can play a 'flash' video in the installer. I suspect it is possible but I understand I'll need to steer them to a native format for 100% compatibility (Flash has 97% of desktops I think). I've not seen anything that does this (for any format). Does anyone have any experience with videos in installers? Regards Ryan - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Playing a video in the installer
If it doesn't have to be directly in the installer you could use a bootstrapper to play the video before the installation pretty easily using Zinc or maybe AIR to play the FLV. On 7/2/08 9:27 AM, Christopher Painter [EMAIL PROTECTED] wrote: There isn't any built-in MSI control that could do that. An external UI handler certainly could but your setup design is going to get way more complicated then you probably have the time or desire for. 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 --- On Wed, 7/2/08, Ryan O'Neill [EMAIL PROTECTED] wrote: From: Ryan O'Neill [EMAIL PROTECTED] Subject: [WiX-users] Playing a video in the installer To: 'General discussion for Windows Installer XML toolset.' wix-users@lists.sourceforge.net Date: Wednesday, July 2, 2008, 5:59 AM Hi all, Customer wants to know if they can play a 'flash' video in the installer. I suspect it is possible but I understand I'll need to steer them to a native format for 100% compatibility (Flash has 97% of desktops I think). I've not seen anything that does this (for any format). Does anyone have any experience with videos in installers? Regards Ryan - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Keith Starling Rosetta Stone® Software Developer T (540) 236-5176 M (540) 383-5478 F (540) 432-0953 (800) 788-0822 RosettaStone.com This e-mail and any attachments thereto are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please contact the sender by reply email and destroy all copies of the original message. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
Is this a bug report? If so, please open a bug on Source Forge. There have been some strange issues in the Votive integration lately that no one working on Votive has been able to reproduce. So if you can provide lots and lots of information that would be much appreciated because everyone is pretty much stumped without being able to see the problem happen. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 08:13 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Playing a video in the installer
I know that I've seen standalone executables that have an embedded Flash runtime that playback content and then exit. Unfortunately I can't point you at any particular product, but hopefully knowing they exist gets you in the right direction if that will suit your needs. It would certainly be better than having a dependency on the Flash or AIR runtimes. -- --Nathan Stohlmann Minneapolis, MN USA [EMAIL PROTECTED] On Wed, Jul 2, 2008 at 8:32 AM, Keith Starling [EMAIL PROTECTED] wrote: If it doesn't have to be directly in the installer you could use a bootstrapper to play the video before the installation pretty easily using Zinc or maybe AIR to play the FLV. On 7/2/08 9:27 AM, Christopher Painter [EMAIL PROTECTED] wrote: There isn't any built-in MSI control that could do that. An external UI handler certainly could but your setup design is going to get way more complicated then you probably have the time or desire for. 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 --- On Wed, 7/2/08, Ryan O'Neill [EMAIL PROTECTED] wrote: From: Ryan O'Neill [EMAIL PROTECTED] Subject: [WiX-users] Playing a video in the installer To: 'General discussion for Windows Installer XML toolset.' wix-users@lists.sourceforge.net Date: Wednesday, July 2, 2008, 5:59 AM Hi all, Customer wants to know if they can play a 'flash' video in the installer. I suspect it is possible but I understand I'll need to steer them to a native format for 100% compatibility (Flash has 97% of desktops I think). I've not seen anything that does this (for any format). Does anyone have any experience with videos in installers? Regards Ryan - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Keith Starling Rosetta Stone(R) Software Developer T (540) 236-5176 M (540) 383-5478 F (540) 432-0953 (800) 788-0822 RosettaStone.com This e-mail and any attachments thereto are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please contact the sender by reply email and destroy all copies of the original message. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Playing a video in the installer
I like the MSI approach though so it looks like I'll have to do it in the bootstrapper after the main app has installed. Thanks for your ideas everyone Ryan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Stohlmann Sent: 02 July 2008 16:28 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Playing a video in the installer I know that I've seen standalone executables that have an embedded Flash runtime that playback content and then exit. Unfortunately I can't point you at any particular product, but hopefully knowing they exist gets you in the right direction if that will suit your needs. It would certainly be better than having a dependency on the Flash or AIR runtimes. -- --Nathan Stohlmann Minneapolis, MN USA [EMAIL PROTECTED] On Wed, Jul 2, 2008 at 8:32 AM, Keith Starling [EMAIL PROTECTED] wrote: If it doesn't have to be directly in the installer you could use a bootstrapper to play the video before the installation pretty easily using Zinc or maybe AIR to play the FLV. On 7/2/08 9:27 AM, Christopher Painter [EMAIL PROTECTED] wrote: There isn't any built-in MSI control that could do that. An external UI handler certainly could but your setup design is going to get way more complicated then you probably have the time or desire for. 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 --- On Wed, 7/2/08, Ryan O'Neill [EMAIL PROTECTED] wrote: From: Ryan O'Neill [EMAIL PROTECTED] Subject: [WiX-users] Playing a video in the installer To: 'General discussion for Windows Installer XML toolset.' wix-users@lists.sourceforge.net Date: Wednesday, July 2, 2008, 5:59 AM Hi all, Customer wants to know if they can play a 'flash' video in the installer. I suspect it is possible but I understand I'll need to steer them to a native format for 100% compatibility (Flash has 97% of desktops I think). I've not seen anything that does this (for any format). Does anyone have any experience with videos in installers? Regards Ryan - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Keith Starling Rosetta Stone(R) Software Developer T (540) 236-5176 M (540) 383-5478 F (540) 432-0953 (800) 788-0822 RosettaStone.com This e-mail and any attachments thereto are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please contact the sender by reply email and destroy all copies of the original message. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users No virus found in this incoming message. Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.4/1530 - Release Date: 02/07/2008 08:05
Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
Am I to understand that you are now testing on VS2005 (previous messages indicated everyone on the dev team has moved to VS 2008 and VS 2005 gets no testing) and you still are unable to reproduce these issues? I ask because they've been acknowledged on this list before. Specifically on May 13th in a thread titled Did WiX V3 projects break compatibility with earlier builds? Scott On Wed, Jul 2, 2008 at 11:17 AM, Rob Mensching [EMAIL PROTECTED] wrote: Is this a bug report? If so, please open a bug on Source Forge. There have been some strange issues in the Votive integration lately that no one working on Votive has been able to reproduce. So if you can provide lots and lots of information that would be much appreciated because everyone is pretty much stumped without being able to see the problem happen. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 08:13 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
There's a bug on this already that's been around for a while: http://sourceforge.net/tracker/index.php?func=detailaid=1821966group_id=105970atid=642714 Actually we're not stumped on this one. If I recall, investigation revealed it to be a bug in VS2005 (which is why it's not a problem in VS2008). There is a moderately complex workaround possible, but nobody has implemented it yet. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 11:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 Am I to understand that you are now testing on VS2005 (previous messages indicated everyone on the dev team has moved to VS 2008 and VS 2005 gets no testing) and you still are unable to reproduce these issues? I ask because they've been acknowledged on this list before. Specifically on May 13th in a thread titled Did WiX V3 projects break compatibility with earlier builds? Scott On Wed, Jul 2, 2008 at 11:17 AM, Rob Mensching [EMAIL PROTECTED] wrote: Is this a bug report? If so, please open a bug on Source Forge. There have been some strange issues in the Votive integration lately that no one working on Votive has been able to reproduce. So if you can provide lots and lots of information that would be much appreciated because everyone is pretty much stumped without being able to see the problem happen. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 08:13 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WIX 3 UI Localisation
Hi I've been reading you can override the UI strings with a localisation file. I was wondering where I could find a list of the variable names? Thanks -- View this message in context: http://www.nabble.com/WIX-3-UI-Localisation-tp18244032p18244032.html Sent from the wix-users mailing list archive at Nabble.com. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3 UI Localisation
See: http://wix.cvs.sourceforge.net/*checkout*/wix/wix/src/ext/UIExtension/wixlib/ErrorProgressText.wxs Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of andywhitt Sent: Wednesday, July 02, 2008 11:39 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WIX 3 UI Localisation Hi I've been reading you can override the UI strings with a localisation file. I was wondering where I could find a list of the variable names? Thanks -- View this message in context: http://www.nabble.com/WIX-3-UI-Localisation-tp18244032p18244032.html Sent from the wix-users mailing list archive at Nabble.com. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WXI codePage question
Try again to see if I could get some help for the question below. thx From: Arthur Jin Sent: Tuesday, July 01, 2008 4:36 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: FW: WXI codePage question Forwarding this question from our dev. - we are trying to build msi from wix for hindi on win2003, but found that the code page does not exist. How do we get around this issue? There are quite a few languages that are supported in xp starter edition, but not on win2003 which is our main production server. Thanks Arthur From: Jiamin Zhu Sent: Monday, June 30, 2008 4:34 PM To: Jiamin Zhu; Arthur Jin; Ashwin Padwalkar; Ken Jordan; Kevin Chien; Tania Ward Subject: RE: WXI codePage question Btw Arthur, even if I match up the LANGUAGE_CODE, it's still complaining that it's not a valid lang id... Since WXI is not supporting these languages, and I can't seem to find a reasonable work around, I will not build MSI for these cultures and will fall be to EN instead. Tania, please note that these will affect the RichUpload Control install for these cultures, but since we have minimal UI I think we are fine. I also spoke with ppl on Toolbar but since they don't support these cultures (yet) they don't run into this issue... Thanks, Jiamin From: Jiamin Zhu Sent: Monday, June 30, 2008 2:47 PM To: Arthur Jin; Ashwin Padwalkar; Ken Jordan; Kevin Chien; Tania Ward Subject: RE: WXI codePage question Btw, both 1200 or 1137 don't work. I got the following errors: 4c:\enlistment\working.sdx2\server\folders\product\richuploadsetup\buildmsi\light.exe : error LGHT0001 : Invalid IDT file: 'c:\enlistment\working.sdx 2\target\debug\i386\Folders\richuploadwixobj\hi\i-boqwrx\codepage.idt' I also ran across this fact on WXI website: http://sourceforge.net/mailarchive/message.php?msg_id=009f01c82009%24bb883700%240201a8c0%40buzzard Does this mean that we can't have MSI in GU, HI, KN, ML, MR, TA, and TE? Would you recommend teams to fall back to en in these scenarios? I wonder how other teams handle these new cultures in their MSIs... Thanks, Jiamin From: Arthur Jin Sent: Monday, June 30, 2008 1:38 PM To: Jiamin Zhu; Ashwin Padwalkar; Ken Jordan; Kevin Chien Cc: Tania Ward Subject: RE: WXI codePage question You are right - Hindi was only supported in Vista and xp starter edition. Even so, there is no code page specifically assigned to it. I know that WXI requires code page specification for MSI build. So, in this case, try specify 1200 (UCS-2LE Unicodehttp://en.wikipedia.org/wiki/Unicode little-endianhttp://en.wikipedia.org/wiki/Little-endian) or 1137 (IBM code page). Btw, the language code should be set to 1081 instead of 1033. From: Jiamin Zhu Sent: Monday, June 30, 2008 12:48 PM To: Ashwin Padwalkar; Arthur Jin; Ken Jordan; Kevin Chien Subject: WXI codePage question Hi all, I am wondering if you know the answer to this question, and if not, do you know any contact in this area? We have wxi file that build MSI for RichUpload control for each culture, looks like at the top of the wxi, we specify LANGUAGE_CODE and LANGUAGE_CODEPAGE. Example, for en: Include ?define LANGUAGE_CODE=1033 ? ?define LANGUAGE_CODEPAGE=1252 ? /Include Now for the culture like HI, it doesn't have a corresponding code page, and if I leave LANGUAGE_CODEPAGE=0 I will get build errors when building the WXI files: 3c:\enlistment\working.sdx2\server\folders\product\richuploadsetup\buildmsi\common\richupload.wxs(31) : error CNDL0049 : The Package element has an i nvalid SummaryCodepage value of '0', which is not valid. A value of '1252' represents Latin-1, which may be what you want. 3c:\enlistment\working.sdx2\server\folders\product\richuploadsetup\buildmsi\light.exe : error LGHT0103 : The system cannot find the file 'c:\enlistme nt\working.sdx2\target\debug\i386\Folders\richuploadwixobj\hi\RichUpload.wixobj' with type 'Source'. Do you know the correct way to solve this? Thanks, Jiamin - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WXI codePage question
Does the Windows Installer support Hindi? Somewhere in the back of my head I remember them missing support for one codepage... but you'd need to follow up with the windows Installer team. WiX toolset just creates what MSI supports. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arthur Jin Sent: Wednesday, July 02, 2008 12:00 To: Arthur Jin; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WXI codePage question Try again to see if I could get some help for the question below. thx From: Arthur Jin Sent: Tuesday, July 01, 2008 4:36 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: FW: WXI codePage question Forwarding this question from our dev. - we are trying to build msi from wix for hindi on win2003, but found that the code page does not exist. How do we get around this issue? There are quite a few languages that are supported in xp starter edition, but not on win2003 which is our main production server. Thanks Arthur From: Jiamin Zhu Sent: Monday, June 30, 2008 4:34 PM To: Jiamin Zhu; Arthur Jin; Ashwin Padwalkar; Ken Jordan; Kevin Chien; Tania Ward Subject: RE: WXI codePage question Btw Arthur, even if I match up the LANGUAGE_CODE, it's still complaining that it's not a valid lang id... Since WXI is not supporting these languages, and I can't seem to find a reasonable work around, I will not build MSI for these cultures and will fall be to EN instead. Tania, please note that these will affect the RichUpload Control install for these cultures, but since we have minimal UI I think we are fine. I also spoke with ppl on Toolbar but since they don't support these cultures (yet) they don't run into this issue... Thanks, Jiamin From: Jiamin Zhu Sent: Monday, June 30, 2008 2:47 PM To: Arthur Jin; Ashwin Padwalkar; Ken Jordan; Kevin Chien; Tania Ward Subject: RE: WXI codePage question Btw, both 1200 or 1137 don't work. I got the following errors: 4c:\enlistment\working.sdx2\server\folders\product\richuploadsetup\buildmsi\light.exe : error LGHT0001 : Invalid IDT file: 'c:\enlistment\working.sdx 2\target\debug\i386\Folders\richuploadwixobj\hi\i-boqwrx\codepage.idt' I also ran across this fact on WXI website: http://sourceforge.net/mailarchive/message.php?msg_id=009f01c82009%24bb883700%240201a8c0%40buzzard Does this mean that we can't have MSI in GU, HI, KN, ML, MR, TA, and TE? Would you recommend teams to fall back to en in these scenarios? I wonder how other teams handle these new cultures in their MSIs... Thanks, Jiamin From: Arthur Jin Sent: Monday, June 30, 2008 1:38 PM To: Jiamin Zhu; Ashwin Padwalkar; Ken Jordan; Kevin Chien Cc: Tania Ward Subject: RE: WXI codePage question You are right - Hindi was only supported in Vista and xp starter edition. Even so, there is no code page specifically assigned to it. I know that WXI requires code page specification for MSI build. So, in this case, try specify 1200 (UCS-2LE Unicodehttp://en.wikipedia.org/wiki/Unicode little-endianhttp://en.wikipedia.org/wiki/Little-endian) or 1137 (IBM code page). Btw, the language code should be set to 1081 instead of 1033. From: Jiamin Zhu Sent: Monday, June 30, 2008 12:48 PM To: Ashwin Padwalkar; Arthur Jin; Ken Jordan; Kevin Chien Subject: WXI codePage question Hi all, I am wondering if you know the answer to this question, and if not, do you know any contact in this area? We have wxi file that build MSI for RichUpload control for each culture, looks like at the top of the wxi, we specify LANGUAGE_CODE and LANGUAGE_CODEPAGE. Example, for en: Include ?define LANGUAGE_CODE=1033 ? ?define LANGUAGE_CODEPAGE=1252 ? /Include Now for the culture like HI, it doesn't have a corresponding code page, and if I leave LANGUAGE_CODEPAGE=0 I will get build errors when building the WXI files: 3c:\enlistment\working.sdx2\server\folders\product\richuploadsetup\buildmsi\common\richupload.wxs(31) : error CNDL0049 : The Package element has an i nvalid SummaryCodepage value of '0', which is not valid. A value of '1252' represents Latin-1, which may be what you want. 3c:\enlistment\working.sdx2\server\folders\product\richuploadsetup\buildmsi\light.exe : error LGHT0103 : The system cannot find the file 'c:\enlistme nt\working.sdx2\target\debug\i386\Folders\richuploadwixobj\hi\RichUpload.wixobj' with type 'Source'. Do you know the correct way to solve this? Thanks, Jiamin - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list
Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
Sorry, my fault, didn't realize this particular issue was a dupe. Is the workaround something that can be explained in the bug? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, July 02, 2008 11:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 There's a bug on this already that's been around for a while: http://sourceforge.net/tracker/index.php?func=detailaid=1821966group_id=105970atid=642714 Actually we're not stumped on this one. If I recall, investigation revealed it to be a bug in VS2005 (which is why it's not a problem in VS2008). There is a moderately complex workaround possible, but nobody has implemented it yet. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 11:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 Am I to understand that you are now testing on VS2005 (previous messages indicated everyone on the dev team has moved to VS 2008 and VS 2005 gets no testing) and you still are unable to reproduce these issues? I ask because they've been acknowledged on this list before. Specifically on May 13th in a thread titled Did WiX V3 projects break compatibility with earlier builds? Scott On Wed, Jul 2, 2008 at 11:17 AM, Rob Mensching [EMAIL PROTECTED] wrote: Is this a bug report? If so, please open a bug on Source Forge. There have been some strange issues in the Votive integration lately that no one working on Votive has been able to reproduce. So if you can provide lots and lots of information that would be much appreciated because everyone is pretty much stumped without being able to see the problem happen. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 08:13 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
When there were a number of people that reported issues that were specific to VS 2005, the people working on Votive started trying to repro the issues there. A few bugs were fixed (or at least understood) and there is one (or maybe two) left that are particularly debilitating. My current (mostly uneducated since I don't work on votive) theory is that there is some problem upgrading the project files due to some changes in a relatively recent build of WiX v3. If projects are recreated that seems to work... but the issue is still being investigated. If you have a solution that reproduces the problem that you can share, I'm sure Jason would very much appreciate it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 11:12 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 Am I to understand that you are now testing on VS2005 (previous messages indicated everyone on the dev team has moved to VS 2008 and VS 2005 gets no testing) and you still are unable to reproduce these issues? I ask because they've been acknowledged on this list before. Specifically on May 13th in a thread titled Did WiX V3 projects break compatibility with earlier builds? Scott On Wed, Jul 2, 2008 at 11:17 AM, Rob Mensching [EMAIL PROTECTED] wrote: Is this a bug report? If so, please open a bug on Source Forge. There have been some strange issues in the Votive integration lately that no one working on Votive has been able to reproduce. So if you can provide lots and lots of information that would be much appreciated because everyone is pretty much stumped without being able to see the problem happen. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 08:13 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Protecting config files during an upgrade
This would fall into the bucket of sure, when I have time, Ditto. smile/ - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Protecting config files during an upgrade
If you're doing a Windows Installer major upgrade and RemoveExistingProducts is late in the new install the upgrade is actually more of an update and it follows the file update rules. This means that an altered (after the initial install) data file won't be replaced according to the file versioning rules. Late means at the end of the execute sequence (InstallExecute, RemoveExistingProducts, InstallFinalize) or after InstallFinalize. Visual Studio 2008 setups now work this way (2005 did not) and I think this was a response to complaints about upgrading databases, config files and so on. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim Sent: Wednesday, July 02, 2008 5:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Protecting config files during an upgrade Rob Mensching wrote: Am I going to have to resort to a custom action to read the settings and propagate them? If so, ugh. It seems like there should be a WiX custom action for simply reading the contents of an XML file (value or attribute) and putting the value into a property. Open feature request that no one has had time to write. Care to write it? This would fall into the bucket of sure, when I have time, but my C++ skills may not be up to the task. Looks like you've got some library functions already written that would make it fairly easy though. If I get to it, I'll contact you about what I need to do to submit the code for inclusion into the project. In the meantime, since it looks like I'll need to rely on a custom action, I can code a DTF custom action to do what I want. As a reminder, I'm wanting to: * Read the user's app.config file, if it has already been installed * Get the settings out of the config file set during the initial installation * Restore those settings to the newly-installed config file Furthermore, I only want to do this in the update, reinstall, or repair case. My code to set the config values during the initial installation works great; I just need to preserve those settings should the user ever repair, reinstall, or apply an update (which I'm implementing as a reinstall with an updated .msi). What I'm looking for is some guidance about how to use my custom action. My instincts tell me to perform a FileSearch for the config file and set a custom property if the file exists; schedule the harvest settings custom action before InstallFiles; and within the custom action code, harvest the settings if the custom property is actually set. Are my instincts correct or is there a better way? For my own education about Windows Installer and WiX, I have a few other questions that the SDK docs aren't clear to me on: Should I be trying to conditionally schedule the custom action to only run during reinstall? If so, what properties should I be checking (checking REINSTALLMODE for the value vomus seems fragile to me)? How do you conditionally schedule a custom action anyway (neither the CustomAction nor the Custom elements support a Condition element)? - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Warning CNDL1044 - How to get rid of this?
It must be really obscure (and I assume the bug was in the resulting Office MSI,. Not in Windows/MSI?) Phil Wilson p.s. If I had had the time, I'd volunteer to make up all sorts of WiX stuff ;=) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 4:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? You know, I'd agree with you *except* that the warning was added after Office ran into a bug that took them a long time to track down because the short name in the MSI matched a short name of a file that already existed on the machine. Maybe admin images? I don't remember the specifics but I remember being surprised when it happened (and was happy to have Derek, who was in Office at the time and still quite upset about never getting those lost days back in his life, add the warning). We don't just make this stuff up you know. smile/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Friday, June 27, 2008 14:19 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? IMO the danger is being overestimated. Windows isn't that dumb. It doesn't care if all your MSI short names are Something~1 (or any other name for that matter) because it ignores them. It's easy to demonstrate that every time Windows sees a short name that conflicts with one already in the destination directory it will create a new one when the file is added to the directory. A The warning implies that you cannot safely install these MSI file table entries: SOMELO~1.EXE|somelongfile4name.exe SOMELO~1.EXE|somelongfile3name.exe SOMELO~1.EXE|somelongfile2name.exe SOMELO~1.EXE|somelongfile1name.exe SOMELO~1.EXE|somelongfile5name.exe Into a folder which already has Somelongfile6name.exe Somelongfile7name.exe Somelongfile8name.exe Somelongfile9name.exe Somelongfile10name.exe Which all have some unpredictable long names, including SOMELO~1.EXE and SOMELO~2.EXE. In reality the install works fine. Calling the GetShortPath API confirms that none of the short names in the MSI file table are relevant. The only caveat I can think of is the (mythical?) OS that doesn't do long names, and I'm pretty sure there are none of those around any more, so I've never tested this on a SFN-only system. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 12:11 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? No, why would we remove the warning? You're doing a dangerous thing, the compiler is trying to help you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam (GTS) Sent: Friday, June 27, 2008 11:19 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? Thanks Rob but I have 5000 files (5000 rows in XML file) in my package and I don't think this is the easiest fix. Can we assume this warning will go away in new version of WIX? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 2:11 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? The easiest fix is to remove the ShortName attribute. The WiX toolset will generate a stable identifier that doesn't have the ambiguity problem. PS: Is there some way to improve the error message? It's basically telling you that you need change the short name since it could collide with other files already on the system. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam (GTS) Sent: Friday, June 27, 2008 11:09 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? I am using Wix toolkit 3.0.4220.0. Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? What version of the WiX toolset are you using? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam (GTS) Sent: Friday, June 27, 2008 10:47 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Warning CNDL1044 - How to get rid of this? Hello, I am constantly receiving this warning upon building the WIX project file: Warning CNDL1044: The File/@ShortName attribute's value 'PERFOR~1.XML' is an ambiguous short
Re: [WiX-users] Warning CNDL1044 - How to get rid of this?
You'd have to have a file in your MSI with the same short name as a file already on the system. Unlikely but possible. So, WiX tries to help you out up front. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Wednesday, July 02, 2008 12:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? It must be really obscure (and I assume the bug was in the resulting Office MSI,. Not in Windows/MSI?) Phil Wilson p.s. If I had had the time, I'd volunteer to make up all sorts of WiX stuff ;=) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 4:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? You know, I'd agree with you *except* that the warning was added after Office ran into a bug that took them a long time to track down because the short name in the MSI matched a short name of a file that already existed on the machine. Maybe admin images? I don't remember the specifics but I remember being surprised when it happened (and was happy to have Derek, who was in Office at the time and still quite upset about never getting those lost days back in his life, add the warning). We don't just make this stuff up you know. smile/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Friday, June 27, 2008 14:19 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? IMO the danger is being overestimated. Windows isn't that dumb. It doesn't care if all your MSI short names are Something~1 (or any other name for that matter) because it ignores them. It's easy to demonstrate that every time Windows sees a short name that conflicts with one already in the destination directory it will create a new one when the file is added to the directory. A The warning implies that you cannot safely install these MSI file table entries: SOMELO~1.EXE|somelongfile4name.exe SOMELO~1.EXE|somelongfile3name.exe SOMELO~1.EXE|somelongfile2name.exe SOMELO~1.EXE|somelongfile1name.exe SOMELO~1.EXE|somelongfile5name.exe Into a folder which already has Somelongfile6name.exe Somelongfile7name.exe Somelongfile8name.exe Somelongfile9name.exe Somelongfile10name.exe Which all have some unpredictable long names, including SOMELO~1.EXE and SOMELO~2.EXE. In reality the install works fine. Calling the GetShortPath API confirms that none of the short names in the MSI file table are relevant. The only caveat I can think of is the (mythical?) OS that doesn't do long names, and I'm pretty sure there are none of those around any more, so I've never tested this on a SFN-only system. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 12:11 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? No, why would we remove the warning? You're doing a dangerous thing, the compiler is trying to help you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam (GTS) Sent: Friday, June 27, 2008 11:19 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? Thanks Rob but I have 5000 files (5000 rows in XML file) in my package and I don't think this is the easiest fix. Can we assume this warning will go away in new version of WIX? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 2:11 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? The easiest fix is to remove the ShortName attribute. The WiX toolset will generate a stable identifier that doesn't have the ambiguity problem. PS: Is there some way to improve the error message? It's basically telling you that you need change the short name since it could collide with other files already on the system. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam (GTS) Sent: Friday, June 27, 2008 11:09 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? I am using Wix toolkit 3.0.4220.0. Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 27, 2008 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Warning CNDL1044 - How to get rid of this? What version of the WiX toolset are you
Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
By workaround I meant some special code to be added to Votive/WixTasks to satisfy the VS2005 output window. I'm trying to track down who it was here who did the investigation to find out why the fix was never implemented. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Wednesday, July 02, 2008 12:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 Sorry, my fault, didn't realize this particular issue was a dupe. Is the workaround something that can be explained in the bug? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, July 02, 2008 11:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 There's a bug on this already that's been around for a while: http://sourceforge.net/tracker/index.php?func=detailaid=1821966group_id=105970atid=642714 Actually we're not stumped on this one. If I recall, investigation revealed it to be a bug in VS2005 (which is why it's not a problem in VS2008). There is a moderately complex workaround possible, but nobody has implemented it yet. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 11:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 Am I to understand that you are now testing on VS2005 (previous messages indicated everyone on the dev team has moved to VS 2008 and VS 2005 gets no testing) and you still are unable to reproduce these issues? I ask because they've been acknowledged on this list before. Specifically on May 13th in a thread titled Did WiX V3 projects break compatibility with earlier builds? Scott On Wed, Jul 2, 2008 at 11:17 AM, Rob Mensching [EMAIL PROTECTED] wrote: Is this a bug report? If so, please open a bug on Source Forge. There have been some strange issues in the Votive integration lately that no one working on Votive has been able to reproduce. So if you can provide lots and lots of information that would be much appreciated because everyone is pretty much stumped without being able to see the problem happen. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 08:13 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net
Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
Yes.. I remember much of this was mentioned back in May. Of course it used to work in the older 3.0.2925.0 build - the report cited below even mentions this. It isn't clear why it stopped working. Scott On Wed, Jul 2, 2008 at 3:55 PM, Jason Ginchereau [EMAIL PROTECTED] wrote: By workaround I meant some special code to be added to Votive/WixTasks to satisfy the VS2005 output window. I'm trying to track down who it was here who did the investigation to find out why the fix was never implemented. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Wednesday, July 02, 2008 12:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 Sorry, my fault, didn't realize this particular issue was a dupe. Is the workaround something that can be explained in the bug? -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, July 02, 2008 11:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 There's a bug on this already that's been around for a while: http://sourceforge.net/tracker/index.php?func=detailaid=1821966group_id=105970atid=642714 Actually we're not stumped on this one. If I recall, investigation revealed it to be a bug in VS2005 (which is why it's not a problem in VS2008). There is a moderately complex workaround possible, but nobody has implemented it yet. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 11:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 Am I to understand that you are now testing on VS2005 (previous messages indicated everyone on the dev team has moved to VS 2008 and VS 2005 gets no testing) and you still are unable to reproduce these issues? I ask because they've been acknowledged on this list before. Specifically on May 13th in a thread titled Did WiX V3 projects break compatibility with earlier builds? Scott On Wed, Jul 2, 2008 at 11:17 AM, Rob Mensching [EMAIL PROTECTED] wrote: Is this a bug report? If so, please open a bug on Source Forge. There have been some strange issues in the Votive integration lately that no one working on Votive has been able to reproduce. So if you can provide lots and lots of information that would be much appreciated because everyone is pretty much stumped without being able to see the problem happen. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, July 02, 2008 08:13 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005 In the output window: error messages are seen only numerically e.g. Error CNDL0205 with no descriptive text, and newlines are still missing. Scott - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet,
[WiX-users] MSXML4 SP1 merge module error
I need to include MS SOAP in my installer via three merge modules provided
by Microsoft:
isapi3_files.msm
soap3_core.msm
winhttp51.msm
They in turn depending on MS XML4 SP1.. of which I have two merge modules,
also from Microsoft:
msxml4sxs32.msm
msxml4sys32.msm
As it happened I was missing the XML merge modules and my installer would
run fine, but we had some issues parsing SOAP responses. When I added the
XML merge modules my installer can no longer install. very near the end of
installing it fails with the following error message:
An error occurred during the installation of assembly
'Microsoft.MSXML2,publicKeyToken=6bd6b9abf345378f,type=win32,version=4.20.9818.0,processorArchitecture=x86'.
Please refer to Help and Support for more information. HRESULT: 0x80070003.
The log file shows:
...
MSI (s) (78:50) [16:32:47:524]: Executing op:
End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=413225981)
MSI (s) (78:50) [16:32:47:571]: Assembly Error:The system cannot find the
path specified.
MSI (s) (78:50) [16:32:47:571]: Note: 1: 1935 2:
{303994BA-6487-47AE-AF1D-7AF6088EEBDB} 3: 0x80070003 4: IAssemblyCacheItem
5: Commit 6:
Microsoft.MSXML2,publicKeyToken=6bd6b9abf345378f,type=win32,version=4.20.9818.0,processorArchitecture=x86
Error 1935. An error occurred during the installation of assembly
'Microsoft.MSXML2,publicKeyToken=6bd6b9abf345378f,type=win32,version=4.20.9818.0,processorArchitecture=x86'.
Please refer to Help and Support for more information. HRESULT: 0x80070003.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{303994BA-6487-47AE-AF1D-7AF6088EEBDB}
MSI (s) (78:50) [16:33:09:946]: Product: MyProduct -- Error 1935. An error
occurred during the installation of assembly
'Microsoft.MSXML2,publicKeyToken=6bd6b9abf345378f,type=win32,version=4.20.9818.0,processorArchitecture=x86'.
Please refer to Help and Support for more information. HRESULT: 0x80070003.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{303994BA-6487-47AE-AF1D-7AF6088EEBDB}
Action ended 16:33:09: InstallFinalize. Return value 3.
...
followed by a rollback
I don't get it. Does anyone have some ideas?
Scott
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstalling or Installing while an exe of the product is running errors
Hi, I was experimenting with an MSI packaged on Vista (WiX v 3.0.4207.0) and installed on Vista with some situations trying to figure out the behaviour: 1. Install Prism.msi version 10.61 C:\Windows\system32msiexec /i \\isdist01z\prism\Vista\Build_10.61.0\MSI\Prism.msi /q /l* C:\Prog ramData\House of Commons\Prism\PRISM.VB6.install.61.log 2. Launch Prism.exe version 10.61 3. Uninstall Prism.msi version 10.61 while foo.exe is running C:\Windows\system32msiexec /x \\isdist01z\prism\Vista\Build_10.61.0\MSI\Prism.msi /q /l* C:\Prog ramData\House of Commons\Prism\PRISM.VB6.uninstall.61.running.log Prism.exe simply hangs and says (Not Responding). I checked the eventvwr and got the following error messages in chronological order: 1. Starting session 1 - 2008/07/02 9:35:13 PM. 2. Application 'C:\Program Files\House Of Commons\PRISM Shell\PRISM.exe' (pid 4984) cannot be restarted - Application SID does not match Conductor SID.. 3. Machine restart is required. 4. Starting session 1 - 2008/07/02 9:35:14 PM. Here's the weird part. I did this at 5:35:14 pm and NOT 9:35:14pm. So the question is. Why am I off by 4 hours ahead? I live in Ottawa, Canada (EST) by the way which is UTC - 5. Also, what does Application SID does not match Conductor SID mean? Is there is a more gracefull way of doing silent installs of a product when the user is running the said product? Thanks! Here's the uninstall log file: === Logging started: 2008/07/02 17:35:13 === Action start 17:35:13: INSTALL. Action start 17:35:13: SystemFolder.B05A204B_CEB8_4A82_B515_ADFB4AE6965C. Action ended 17:35:13: SystemFolder.B05A204B_CEB8_4A82_B515_ADFB4AE6965C. Return value 1. Action start 17:35:13: ProgramFilesFolder.B05A204B_CEB8_4A82_B515_ADFB4AE6965C. Action ended 17:35:13: ProgramFilesFolder.B05A204B_CEB8_4A82_B515_ADFB4AE6965C. Return value 1. Action start 17:35:13: ProgramFilesFolder.C7AC8538_65ED_4C2B_AE16_6291871D0918. Action ended 17:35:13: ProgramFilesFolder.C7AC8538_65ED_4C2B_AE16_6291871D0918. Return value 1. Action start 17:35:13: ProgramMenuFolder.C7AC8538_65ED_4C2B_AE16_6291871D0918. Action ended 17:35:13: ProgramMenuFolder.C7AC8538_65ED_4C2B_AE16_6291871D0918. Return value 1. Action start 17:35:13: DesktopFolder.C7AC8538_65ED_4C2B_AE16_6291871D0918. Action ended 17:35:13: DesktopFolder.C7AC8538_65ED_4C2B_AE16_6291871D0918. Return value 1. Action start 17:35:13: FindRelatedProducts. Action ended 17:35:13: FindRelatedProducts. Return value 0. Action start 17:35:13: ValidateProductID. Action ended 17:35:13: ValidateProductID. Return value 1. Action start 17:35:13: CostInitialize. Action ended 17:35:13: CostInitialize. Return value 1. Action start 17:35:13: FileCost. Action ended 17:35:13: FileCost. Return value 1. Action start 17:35:13: CostFinalize. Action ended 17:35:13: CostFinalize. Return value 1. Action start 17:35:13: InstallValidate. Action ended 17:35:54: InstallValidate. Return value 1. Action start 17:35:54: InstallInitialize. Action ended 17:35:54: InstallInitialize. Return value 1. Action start 17:35:54: ProcessComponents. Action ended 17:35:55: ProcessComponents. Return value 1. Action start 17:35:55: UnpublishFeatures. Action ended 17:35:55: UnpublishFeatures. Return value 1. Action start 17:35:55: RemoveRegistryValues. Action ended 17:35:59: RemoveRegistryValues. Return value 1. Action start 17:35:59: RemoveShortcuts. Action ended 17:35:59: RemoveShortcuts. Return value 1. Action start 17:35:59: RemoveFiles. Action ended 17:35:59: RemoveFiles. Return value 0. Action start 17:35:59: InstallFiles. Action ended 17:35:59: InstallFiles. Return value 1. Action start 17:35:59: CreateShortcuts. Action ended 17:35:59: CreateShortcuts. Return value 1. Action start 17:35:59: WriteRegistryValues. Action ended 17:35:59: WriteRegistryValues. Return value 1. Action start 17:35:59: RegisterUser. Action ended 17:35:59: RegisterUser. Return value 0. Action start 17:35:59: RegisterProduct. Action ended 17:35:59: RegisterProduct. Return value 1. Action start 17:35:59: PublishFeatures. Action ended 17:35:59: PublishFeatures. Return value 1. Action start 17:35:59: PublishProduct. Action ended 17:35:59: PublishProduct. Return value 1. Action start 17:35:59: InstallFinalize. Info 1903. Scheduling reboot operation: Deleting file C:\Config.Msi\540af.rbf. Must reboot to complete operation. Info 1903. Scheduling reboot operation: Deleting file C:\Config.Msi\540b5.rbf. Must reboot to complete operation. Info 1903. Scheduling reboot operation: Deleting file C:\Config.Msi\540bc.rbf. Must reboot to complete operation. Info 1903. Scheduling reboot operation: Deleting file C:\Config.Msi\54102.rbf. Must reboot to complete operation. Info 1903. Scheduling reboot operation: Deleting file C:\Config.Msi\54118.rbf. Must reboot to complete operation. Info 1903. Scheduling reboot operation: Deleting file C:\Config.Msi\54129.rbf. Must reboot to complete operation. Action ended 17:36:19: InstallFinalize. Return value 1. Action ended 17:36:19:
[WiX-users] 64-bit wix tools (heat/etc...)
Great work moving towards 64-bit compatibility so far. What's the latest timeframe expected on 64-bit tools, especially compiling heat.exe for both x64 and x86 for .NET? (it would be great to get them separately, rather than anycpu, such that we could run both, as appropriate for the dll being harvested, on an x64 build machine) I'd love to be able to harvest regkey settings out of 64-bit dlls, and obviously, x64 heat would be needed for this, since x86 heat can't load the files. Thanks, Aaron Averbuch Software Development Manager Pure Networks, Inc. (206) 812-1919 http://www.purenetworks.com http://www.purenetworks.com/ - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
