Re: [WiX-users] Uninstall stops Explorer but doesn't restart it
How do I force Windows Install to restart Explorer after it kills it? > -Original Message- > From: Bob Arnson [mailto:b...@joyofsetup.com] > Sent: Monday, October 17, 2011 8:39 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Uninstall stops Explorer but doesn't restart it > > On 10-Oct-11 16:29, Brad Lemings wrote: > > I have a package with a background process that is normally running. When > the user uninstalls the software, Wix and/or Windows Installer prompts to > shutdown both the process and Explorer (to unregister extensions) but it > does not restart Explorer. > A verbose log will have details from MSI about what it did/tried to do. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstall stops Explorer but doesn't restart it
Hi, I have a package with a background process that is normally running. When the user uninstalls the software, Wix and/or Windows Installer prompts to shutdown both the process and Explorer (to unregister extensions) but it does not restart Explorer. I'm sure this is a known issue. Can anyone point me to some solutions/work-arounds for this? Thanks. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixUIMondo
I think I found it after some searching. Just for those that also need it: 1. Go to wix.codeplex.com. 2. Select the Source tab. 3. Select the 3.5 branch from the drop-down list at the right. 4. Select the source code zip with the label "Associated with release: Wix Toolset 3.5". So I located the .wxl sources with the appropriate text strings. I'm assuming I don't need the special markup in comments (e.g. _locIDText, _locComment)? Thanks. > -Original Message----- > From: Brad Lemings [mailto:b...@rebit.com] > Sent: Monday, October 03, 2011 10:17 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] WixUIMondo > > > I can't seem to find source code downloads for specific versions. Is there > only the latest source code download or am I looking in the wrong place? > > Source code for 3.5 is the version I'm interested in. > > Thanks. > > > > -Original Message- > > From: Bob Arnson [mailto:b...@joyofsetup.com] > > Sent: Saturday, October 01, 2011 1:54 PM > > To: wix-users@lists.sourceforge.net > > Subject: Re: [WiX-users] WixUIMondo > > > > On 30-Sep-11 18:06, Brad Lemings wrote: > > > Is it possible to change the text of the Typical button? If so, how? > > > How about the text below the button? Yes, I'll have to localize > > > custom text. :) > > > > You can override all localization strings by specifying a .wxl file in your > project. > > Copy the strings from the .wxl in the WiX sources into your .wxl and > > replace the text with whatever you want. > > > > -- > > sig://boB > > http://joyofsetup.com/ > > > > > > -- > > All of the data generated in your IT infrastructure is > > seriously valuable. > > Why? It contains a definitive record of application performance, > > security threats, fraudulent activity, and more. Splunk takes this > > data and makes sense of it. IT sense. And common sense. > > http://p.sf.net/sfu/splunk-d2dcopy2 > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security threats, > fraudulent activity and more. Splunk takes this data and makes sense of it. > Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixUIMondo
I can't seem to find source code downloads for specific versions. Is there only the latest source code download or am I looking in the wrong place? Source code for 3.5 is the version I'm interested in. Thanks. > -Original Message- > From: Bob Arnson [mailto:b...@joyofsetup.com] > Sent: Saturday, October 01, 2011 1:54 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] WixUIMondo > > On 30-Sep-11 18:06, Brad Lemings wrote: > > Is it possible to change the text of the Typical button? If so, how? > > How about the text below the button? Yes, I'll have to localize > > custom text. :) > > You can override all localization strings by specifying a .wxl file in your > project. > Copy the strings from the .wxl in the WiX sources into your .wxl and replace > the text with whatever you want. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixUIMondo
Is it possible to change the text of the Typical button? If so, how? How about the text below the button? Yes, I'll have to localize custom text. :) Thanks. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Removing/Deleting data at uninstall
This question has probably been asked many times before. If there is a web page that answers it, please provide links. If I have a software package that creates a database, user settings, and other data files while it is installed and I want to allow the user to delete or keep this data when uninstalling, how would I go about doing that in Wix? Thanks. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Subscribe Events
Is it possible for an external program or embedded script to subscribe to events (e.g. SetProgress)? Thanks. -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Typical Wix conventions for displaying release notes?
How do you set WixShellExecTarget if you want to launch two applications in the same Wix file? -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Monday, July 11, 2011 11:42 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Typical Wix conventions for displaying release notes? On 11-Jul-11 13:02, Brad Lemings wrote: > Just wondering what the typical Wix conventions are for displaying release > notes near the end of an installation sequence. See "How To: Run the Installed Application After Setup" and replace "myapplication.exe" with "myreleasenotes.html." -- sig://boB http://joyofsetup.com/ -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Typical Wix conventions for displaying release notes?
Haven't tried yet but would this work? -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, July 15, 2011 10:09 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Typical Wix conventions for displaying release notes? Lots of properties built in listed here: http://msdn.microsoft.com/en-us/library/aa370905(v=VS.85).aspx This one might be interesting: http://msdn.microsoft.com/en-us/library/aa372384(v=VS.85).aspx On Fri, Jul 15, 2011 at 9:03 AM, Brad Lemings wrote: > And how can the current language/locale of the computer on which the > software is being installed be determined? > > Packaging/Installing multiple release notes, one for each supported > language is pretty straightforward. Display a file is too. But is > there a way to select and display the correct version depending on the > language of the target system? > > Thanks. > > -Original Message- > From: Bob Arnson [mailto:b...@joyofsetup.com] > Sent: Monday, July 11, 2011 11:42 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Typical Wix conventions for displaying > release notes? > > On 11-Jul-11 13:02, Brad Lemings wrote: > > Just wondering what the typical Wix conventions are for displaying > release notes near the end of an installation sequence. > > See "How To: Run the Installed Application After Setup" and replace > "myapplication.exe" with "myreleasenotes.html." > > -- > sig://boB > http://joyofsetup.com/ > > > > -- > All of the data generated in your IT infrastructure is > seriously valuable. > Why? It contains a definitive record of application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > AppSumo Presents a FREE Video for the SourceForge Community > by Eric Ries, the creator of the Lean Startup Methodology on "Lean > Startup Secrets Revealed." This video shows you how to validate your > ideas, optimize your ideas and identify your business strategy. > http://p.sf.net/sfu/appsumosfdev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Typical Wix conventions for displaying release notes?
And how can the current language/locale of the computer on which the software is being installed be determined? Packaging/Installing multiple release notes, one for each supported language is pretty straightforward. Display a file is too. But is there a way to select and display the correct version depending on the language of the target system? Thanks. -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Monday, July 11, 2011 11:42 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Typical Wix conventions for displaying release notes? On 11-Jul-11 13:02, Brad Lemings wrote: > Just wondering what the typical Wix conventions are for displaying release > notes near the end of an installation sequence. See "How To: Run the Installed Application After Setup" and replace "myapplication.exe" with "myreleasenotes.html." -- sig://boB http://joyofsetup.com/ -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multi-Lingual MSI
Our product does utilize a bootstrapper so this is a distinct possibility. Just wondering if there is a more illustrative tutorial or example somewhere that does what you describe? -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: Tuesday, July 12, 2011 12:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Multi-Lingual MSI Nope unfortunately not. For a good localization only embedding the transforms, creating a bootstrapper to select the transform or even handle the whole MSI installation are possible approaches. 2011/7/11 Brad Lemings : > Greetings, > > Just wondering if there is an easier way to accomplish this: > http://www.geektieguy.com/2010/03/13/create-a-multi-lingual-multi-language-msi-using-wix-and-custom-build-scripts/? > > Thanks. > > -- > All of the data generated in your IT infrastructure is > seriously valuable. > Why? It contains a definitive record of application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Typical Wix conventions for displaying release notes?
Oh nevermind. I didn't look at the whole example. "myapplication.exe" IS a Wix reference. -Original Message----- From: Brad Lemings Sent: Monday, July 11, 2011 1:51 PM To: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Typical Wix conventions for displaying release notes? How does Wix know where to find myapplication.exe? How would I replace myapplication.exe with a Component/File reference? I'm still somewhat new to Wix. :) Thanks. -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Monday, July 11, 2011 11:42 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Typical Wix conventions for displaying release notes? On 11-Jul-11 13:02, Brad Lemings wrote: > Just wondering what the typical Wix conventions are for displaying release > notes near the end of an installation sequence. See "How To: Run the Installed Application After Setup" and replace "myapplication.exe" with "myreleasenotes.html." -- sig://boB http://joyofsetup.com/ -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Typical Wix conventions for displaying release notes?
How does Wix know where to find myapplication.exe? How would I replace myapplication.exe with a Component/File reference? I'm still somewhat new to Wix. :) Thanks. -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Monday, July 11, 2011 11:42 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Typical Wix conventions for displaying release notes? On 11-Jul-11 13:02, Brad Lemings wrote: > Just wondering what the typical Wix conventions are for displaying release > notes near the end of an installation sequence. See "How To: Run the Installed Application After Setup" and replace "myapplication.exe" with "myreleasenotes.html." -- sig://boB http://joyofsetup.com/ -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Multi-Lingual MSI
Greetings, Just wondering if there is an easier way to accomplish this: http://www.geektieguy.com/2010/03/13/create-a-multi-lingual-multi-language-msi-using-wix-and-custom-build-scripts/? Thanks. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Typical Wix conventions for displaying release notes?
Hi, Just wondering what the typical Wix conventions are for displaying release notes near the end of an installation sequence. Thanks. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Install Directory Structures
Hi, I was wondering if there were techniques, methods for accommodating both single-level and multi-level install directory structures using the same set of Wix XML source files? If I'm not mistaken, the directory structure is currently reflected directly in the XML code. Example: Thanks, Eric. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Replacing regsvr32 commands with Wix elements
Greetings, This is a list of registry entries that I've uncovered for a couple of COM server components: -Original Message- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: Monday, June 20, 2011 4:07 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > > If I had to guess, this component may rely on other components. I > swear I saw something along the lines of this with an ATL component. > When the registry redirection occurs inside of Heat, it makes the > registry look empty. As such, if your component required ATL it would > fail inside its > regsvr32 procedure. > > I had pondered making a patch myself, where heat would allow for a > reg script to be passed as a parameter (basically reg script being > another heat fragment). With that, you could create an ATL.reg using > heat against the ATL DLL, and then pass it as a parameter to the Heat call > for your component. > > The only problem would be writing the logic to identify which > attributes were changed by your DLL compared to your reg script. > > I could be way off base, but I think I could generate a reproducible test > case. > > -Original Message- > From: Brad Lemings [mailto:b...@rebit.com] > Sent: Monday, June 20, 2011 4:47 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > My guess is it is not safe to ignore this warning. The generated Wix > source contains nothing but a DirectoryRef, a Component, and File > element. I know more is required to register a COM server than that. > So heat does not work. Question now is, why not? > > -Original Message- > From: Brad Lemings > Sent: Monday, June 20, 2011 3:42 PM > To: General discussion for Windows Installer XML toolset. > Subject: RE: [WiX-users] Replacing regsvr32 commands with Wix elements > > > What does "Unable to load file: error 93" mean? > > Here's the entire warning message: > > heat.exe : warning HEAT5150 : Could not harvest data from a file that > was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If this > file does not support SelfReg you can ignore this warning. > Otherwise, this error detail may be helpful to diagnose the failure: > Unable to load file: C:\Builds\MyNSE\MyNSE.dll, error: 193 > > When I run the command "regsvr32 MyNSE.dll", the command executes > successfully. Safe to ignore this warning? > > -Original Message- > From: Dave Brotherstone [mailto:dav...@pobox.com] > Sent: Monday, June 20, 2011 1:58 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > > > > -Original Message- > > From: Brad Lemings [mailto:b...@rebit.com] > > Sent: Monday, June 20, 2011 1:19 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix > > elements > > > > Hmm. How can I capture the effects of the regsvr32 command in a > > .reg file which is what Heat expects? > > > > You don't need to - heat file yourfile.dll -o install_actions.wxs > will capture everything that regsvr32 does (or actually what your > DllRegisterServer call in the DLL does). > > It really is that easy :) > -- > -- > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > -- > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > EditLive Enterprise is
Re: [WiX-users] Replacing regsvr32 commands with Wix elements
No, I think you're right on the money. The NSE DLL that I'm testing requires MFC, Qt, and a host of other dependencies. Being that I had to rebuild my Service so that it is statically linked just so Windows Installer could start it at the expected time, the MFC/ATL dependency is no surprise. :P > -Original Message- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: Monday, June 20, 2011 4:07 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > > If I had to guess, this component may rely on other components. I swear I > saw something along the lines of this with an ATL component. > When the registry redirection occurs inside of Heat, it makes the registry > look > empty. As such, if your component required ATL it would fail inside its > regsvr32 procedure. > > I had pondered making a patch myself, where heat would allow for a reg > script to be passed as a parameter (basically reg script being another heat > fragment). With that, you could create an ATL.reg using heat against the ATL > DLL, and then pass it as a parameter to the Heat call for your component. > > The only problem would be writing the logic to identify which attributes > were changed by your DLL compared to your reg script. > > I could be way off base, but I think I could generate a reproducible test > case. > > -Original Message- > From: Brad Lemings [mailto:b...@rebit.com] > Sent: Monday, June 20, 2011 4:47 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > My guess is it is not safe to ignore this warning. The generated Wix source > contains nothing but a DirectoryRef, a Component, and File element. I know > more is required to register a COM server than that. > So heat does not work. Question now is, why not? > > -Original Message- > From: Brad Lemings > Sent: Monday, June 20, 2011 3:42 PM > To: General discussion for Windows Installer XML toolset. > Subject: RE: [WiX-users] Replacing regsvr32 commands with Wix elements > > > What does "Unable to load file: error 93" mean? > > Here's the entire warning message: > > heat.exe : warning HEAT5150 : Could not harvest data from a file > that was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If > this file does not support SelfReg you can ignore this warning. > Otherwise, this error detail may be helpful to diagnose the failure: > Unable to load file: C:\Builds\MyNSE\MyNSE.dll, error: 193 > > When I run the command "regsvr32 MyNSE.dll", the command executes > successfully. Safe to ignore this warning? > > -Original Message- > From: Dave Brotherstone [mailto:dav...@pobox.com] > Sent: Monday, June 20, 2011 1:58 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > > > > -Original Message- > > From: Brad Lemings [mailto:b...@rebit.com] > > Sent: Monday, June 20, 2011 1:19 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > > > Hmm. How can I capture the effects of the regsvr32 command in a .reg > > file which is what Heat expects? > > > > You don't need to - heat file yourfile.dll -o install_actions.wxs will > capture everything that regsvr32 does (or actually what your > DllRegisterServer call in the DLL does). > > It really is that easy :) > > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > --
Re: [WiX-users] Replacing regsvr32 commands with Wix elements
My guess is it is not safe to ignore this warning. The generated Wix source contains nothing but a DirectoryRef, a Component, and File element. I know more is required to register a COM server than that. So heat does not work. Question now is, why not? -Original Message- From: Brad Lemings Sent: Monday, June 20, 2011 3:42 PM To: General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Replacing regsvr32 commands with Wix elements What does "Unable to load file: error 93" mean? Here's the entire warning message: heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Unable to load file: C:\Builds\MyNSE\MyNSE.dll, error: 193 When I run the command "regsvr32 MyNSE.dll", the command executes successfully. Safe to ignore this warning? -Original Message- From: Dave Brotherstone [mailto:dav...@pobox.com] Sent: Monday, June 20, 2011 1:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > -Original Message- > From: Brad Lemings [mailto:b...@rebit.com] > Sent: Monday, June 20, 2011 1:19 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > Hmm. How can I capture the effects of the regsvr32 command in a .reg > file which is what Heat expects? > You don't need to - heat file yourfile.dll -o install_actions.wxs will capture everything that regsvr32 does (or actually what your DllRegisterServer call in the DLL does). It really is that easy :) -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Replacing regsvr32 commands with Wix elements
What does "Unable to load file: error 93" mean? Here's the entire warning message: heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Unable to load file: C:\Builds\MyNSE\MyNSE.dll, error: 193 When I run the command "regsvr32 MyNSE.dll", the command executes successfully. Safe to ignore this warning? -Original Message- From: Dave Brotherstone [mailto:dav...@pobox.com] Sent: Monday, June 20, 2011 1:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > -Original Message- > From: Brad Lemings [mailto:b...@rebit.com] > Sent: Monday, June 20, 2011 1:19 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements > > Hmm. How can I capture the effects of the regsvr32 command in a .reg > file which is what Heat expects? > You don't need to - heat file yourfile.dll -o install_actions.wxs will capture everything that regsvr32 does (or actually what your DllRegisterServer call in the DLL does). It really is that easy :) -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Replacing regsvr32 commands with Wix elements
Found a regdiff tool. Hopefully this should do the trick. :) -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Sent: Monday, June 20, 2011 1:19 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements Hmm. How can I capture the effects of the regsvr32 command in a .reg file which is what Heat expects? -Original Message- From: Thom Leigh [mailto:t...@mondago.com] Sent: Monday, June 20, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements Use heat <http://wix.sourceforge.net/manual-wix3/heat.htm> to harvest your registration information and create a wix fragment that you can include or copy/paste from... It's actually very easy :) -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Sent: 20 June 2011 17:27 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Replacing regsvr32 commands with Wix elements G'morning (or evening wherever you are): Our software has a couple of Explorer extensions - a namespace and shell extension to be exact - which we've always installed and uninstalled by running regsvr32 commands. Are there any helpful Wix tutorials circulating on the net that describe the Wix equivalent for doing this? Thanks. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Replacing regsvr32 commands with Wix elements
Hmm. How can I capture the effects of the regsvr32 command in a .reg file which is what Heat expects? -Original Message- From: Thom Leigh [mailto:t...@mondago.com] Sent: Monday, June 20, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements Use heat <http://wix.sourceforge.net/manual-wix3/heat.htm> to harvest your registration information and create a wix fragment that you can include or copy/paste from... It's actually very easy :) -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Sent: 20 June 2011 17:27 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Replacing regsvr32 commands with Wix elements G'morning (or evening wherever you are): Our software has a couple of Explorer extensions - a namespace and shell extension to be exact - which we've always installed and uninstalled by running regsvr32 commands. Are there any helpful Wix tutorials circulating on the net that describe the Wix equivalent for doing this? Thanks. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Replacing regsvr32 commands with Wix elements
G'morning (or evening wherever you are): Our software has a couple of Explorer extensions - a namespace and shell extension to be exact - which we've always installed and uninstalled by running regsvr32 commands. Are there any helpful Wix tutorials circulating on the net that describe the Wix equivalent for doing this? Thanks. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Combined 32-bit and 64-bit MSI?
AFAICT, both links use separate MSI files for 32-bit and 64-bit installs. Did I miss something? -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Monday, June 13, 2011 12:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Combined 32-bit and 64-bit MSI? Two separate MSI files are recommended. http://blogs.msdn.com/b/heaths/archive/2008/01/15/different-packages-are-required-for-different-processor-architectures.aspx Same source though: http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx Phil Wilson -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Sent: Monday, June 13, 2011 10:38 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Combined 32-bit and 64-bit MSI? Is it possible to combine a 32-bit and 64-bit install in the same MSI file? If so, are there some examples, tutorials to look at? Thanks, Eric. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ 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 (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Combined 32-bit and 64-bit MSI?
Is it possible to combine a 32-bit and 64-bit install in the same MSI file? If so, are there some examples, tutorials to look at? Thanks, Eric. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Elevated Custom Actions
Ah. My original question wasn't entirely accurate. :) I meant to ask, is it possible to execute a custom action WITH ELEVATED PRIVILEGES after InstallFinalize? -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Monday, May 23, 2011 9:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Elevated Custom Actions http://www.tramontana.co.hu/wix/lesson3.php#3.2 Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Brad Lemings [mailto:b...@rebit.com] Sent: 23 May 2011 16:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Elevated Custom Actions Can you send a link for the custom action in the Wix tutorial? Thanks. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Monday, May 23, 2011 5:33 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Elevated Custom Actions False to the best of my knowledge. The Visual C++ merge modules put an Uninstall Custom Action (SxsUninstallCA) after InstallFinalize & the WiX tutorial uses a Type 2 Custom Action after InstallFinalize to show how to launch an installed executable. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Brad Lemings [mailto:b...@rebit.com] Sent: 22 May 2011 00:31 To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] Elevated Custom Actions AFAICT, it is not possible to execute a custom action after InstallFinalize. Is this true? -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Elevated Custom Actions
Can you send a link for the custom action in the Wix tutorial? Thanks. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Monday, May 23, 2011 5:33 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Elevated Custom Actions False to the best of my knowledge. The Visual C++ merge modules put an Uninstall Custom Action (SxsUninstallCA) after InstallFinalize & the WiX tutorial uses a Type 2 Custom Action after InstallFinalize to show how to launch an installed executable. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Brad Lemings [mailto:b...@rebit.com] Sent: 22 May 2011 00:31 To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] Elevated Custom Actions AFAICT, it is not possible to execute a custom action after InstallFinalize. Is this true? -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Elevated Custom Actions
AFAICT, it is not possible to execute a custom action after InstallFinalize. Is this true? -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Debugging Custom Actions
ServiceInstall (e.g. SCM registration) works fine AFAICT and, as I suspected, does the same as the 'My-Svc.exe /install' command. If I disable (comment out) the custom "start service" action, I can start the service up normally with elevated privileges after the install completes. So now its just a matter of getting the service started at the proper stage of InstallSequence. Once installed and started, I believe StopService and DeleteServices will all fall into their conventional Wix sequences for all other possible scenarios (upgrades, rollbacks, etc). On May 20, 2011, at 8:34 PM, Gregg Swanson wrote: > If you use the pattern that Castro provided you may have an issue with your > service. For example if you service is creating an event log entry, you may > fail if the SERVICEACCOUNT is not authorized to create an entry. > > Check the event log for messages, I have on occasion specified an invalid > password as one of my properties, etc... > > Thanks > Gregg > > -Original Message- > From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] > Sent: Friday, May 20, 2011 6:29 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Debugging Custom Actions > > In my limited experience something like this has always simply done the > RightThing (TM) : > > Guid="5E7A07C7-9299-4992-A601-EBB79D441A83" >Win64='$(var.Win64)'> >Source='$(var.TARGET_DIR)\$(var.MY_SERVICE_OUTPUT_NAME)' >KeyPath='yes' Checksum='yes'/> >Name="$(var.MY_SERVICE_SVC_NAME)" >DisplayName="$(var.MY_SERVICE_DISPLAY_NAME)" >Type="ownProcess" >Start="auto" >ErrorControl="normal" >Description="$(var.MY_SERVICE_DESCRIPTION)" >Account="[SERVICEACCOUNT]" >Password="[SERVICEPASSWORD]" /> >Name="$(var.MY_SERVICE_SVC_NAME)" >Start="install" >Stop="both" >Remove="uninstall" >Wait="yes" /> > > > I would give this a try first, rather than trying to start the service > manually with a custom action. I'm sure somebody with a lot more experience > with _BIND_TO_CURRENT_VCLIBS_VERSION can say whether the authoring above is > expected to work or not. > > 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: Brad Lemings [mailto:b...@rebit.com] >> Sent: Friday, May 20, 2011 1:16 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Debugging Custom Actions >> >> >> After a lot more investigation, I've came to the same conclusion: the >> service can't be used at all until after InstallFinalize since it is >> linked to a specific VC runtime version using the >> _BIND_TO_CURRENT_VCLIBS_VERSION macro when it is built. >> >> Also, I now believe 'My-Svc.exe /install' and the Wix ServiceInstall >> element do exactly the same thing by different means. If that's the >> case, I now only need to start the service after InstallFinalize. The >> CustomAction though does not seem to execute the command with elevated >> priviliges. How does one ensure that CustomActions are executed with >> elevated privileges? Or is there a way to postpone the standard >> StartServices action until after InstallFinalize instead of using a custom >> action? >> >> Proper Windows Installer features? Links, references please! >> >> Thanks for all the help. >> >> P.S. I dunno if it's Wix or the underlying Windows Installler but >> developing an installer with this technology is a real PITA! >> >> -Original Message- >> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] >> Sent: Friday, May 20, 2011 12:21 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Debugging Custom Actions >> >> This one of the reasons why you should avoid exe custom actions. They >> are notoriously hard to debug. >> >> I see that you are scheduling your RunMySvcInstall custom action after >> InstallServices. That suggests you still have the >> element. I assume that My-Svc.exe /install actually registers
Re: [WiX-users] Debugging Custom Actions
I've tried that. It doesn't work because the VC runtimes contained in the merge modules don't get commited to the GAC until after StartServices and possibly InstallFinalize IIUC. On May 20, 2011, at 5:28 PM, Castro, Edwin G. (Hillsboro) wrote: > In my limited experience something like this has always simply done the > RightThing (TM) : > > Guid="5E7A07C7-9299-4992-A601-EBB79D441A83" >Win64='$(var.Win64)'> >Source='$(var.TARGET_DIR)\$(var.MY_SERVICE_OUTPUT_NAME)' >KeyPath='yes' Checksum='yes'/> >Name="$(var.MY_SERVICE_SVC_NAME)" >DisplayName="$(var.MY_SERVICE_DISPLAY_NAME)" >Type="ownProcess" >Start="auto" >ErrorControl="normal" >Description="$(var.MY_SERVICE_DESCRIPTION)" >Account="[SERVICEACCOUNT]" >Password="[SERVICEPASSWORD]" /> >Name="$(var.MY_SERVICE_SVC_NAME)" >Start="install" >Stop="both" >Remove="uninstall" >Wait="yes" /> > > > I would give this a try first, rather than trying to start the service > manually with a custom action. I'm sure somebody with a lot more experience > with _BIND_TO_CURRENT_VCLIBS_VERSION can say whether the authoring above is > expected to work or not. > > Edwin G. Castro > Software Developer - Staff > Digital Channels > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > Please consider the environment before printing this e-mail > > >> -Original Message- >> From: Brad Lemings [mailto:b...@rebit.com] >> Sent: Friday, May 20, 2011 1:16 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Debugging Custom Actions >> >> >> After a lot more investigation, I've came to the same conclusion: the service >> can't be used at all until after InstallFinalize since it is linked to a >> specific VC >> runtime version using the _BIND_TO_CURRENT_VCLIBS_VERSION macro >> when it is built. >> >> Also, I now believe 'My-Svc.exe /install' and the Wix ServiceInstall element >> do exactly the same thing by different means. If that's the case, I now only >> need to start the service after InstallFinalize. The CustomAction though >> does >> not seem to execute the command with elevated priviliges. How does one >> ensure that CustomActions are executed with elevated privileges? Or is >> there a way to postpone the standard StartServices action until after >> InstallFinalize instead of using a custom action? >> >> Proper Windows Installer features? Links, references please! >> >> Thanks for all the help. >> >> P.S. I dunno if it's Wix or the underlying Windows Installler but developing >> an >> installer with this technology is a real PITA! >> >> -Original Message- >> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] >> Sent: Friday, May 20, 2011 12:21 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Debugging Custom Actions >> >> This one of the reasons why you should avoid exe custom actions. They are >> notoriously hard to debug. >> >> I see that you are scheduling your RunMySvcInstall custom action after >> InstallServices. That suggests you still have the element. >> I >> assume that My-Svc.exe /install actually registers the service just like the >> element would do. If this is true then it is duplication >> and >> might cause problems. I really think you need to know what My-Svc.exe >> /install does to know how to author the msi package. >> >> If you have removed the element then you may need to >> change After="InstallServices" to something else. >> >> Is it possible that some of the dependencies needed by My-Svc.exe to >> execute are not available until after InstallFinalize? Changing the >> RunMySvcInstall custom action to run after InstallFinalize will require an >> immediate custom action *and* it will execute after the transaction is closed >> (that means no rollback after failures, yuk!). >> >> My personal strategy here would be to avoid the RunMySvcInstall and >> RunMySvcUninstall custom actions and use proper Windows Installer >> features... >> >> Edwin G. Castr
Re: [WiX-users] Debugging Custom Actions
After a lot more investigation, I've came to the same conclusion: the service can't be used at all until after InstallFinalize since it is linked to a specific VC runtime version using the _BIND_TO_CURRENT_VCLIBS_VERSION macro when it is built. Also, I now believe 'My-Svc.exe /install' and the Wix ServiceInstall element do exactly the same thing by different means. If that's the case, I now only need to start the service after InstallFinalize. The CustomAction though does not seem to execute the command with elevated priviliges. How does one ensure that CustomActions are executed with elevated privileges? Or is there a way to postpone the standard StartServices action until after InstallFinalize instead of using a custom action? Proper Windows Installer features? Links, references please! Thanks for all the help. P.S. I dunno if it's Wix or the underlying Windows Installler but developing an installer with this technology is a real PITA! -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, May 20, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Debugging Custom Actions This one of the reasons why you should avoid exe custom actions. They are notoriously hard to debug. I see that you are scheduling your RunMySvcInstall custom action after InstallServices. That suggests you still have the element. I assume that My-Svc.exe /install actually registers the service just like the element would do. If this is true then it is duplication and might cause problems. I really think you need to know what My-Svc.exe /install does to know how to author the msi package. If you have removed the element then you may need to change After="InstallServices" to something else. Is it possible that some of the dependencies needed by My-Svc.exe to execute are not available until after InstallFinalize? Changing the RunMySvcInstall custom action to run after InstallFinalize will require an immediate custom action *and* it will execute after the transaction is closed (that means no rollback after failures, yuk!). My personal strategy here would be to avoid the RunMySvcInstall and RunMySvcUninstall custom actions and use proper Windows Installer features... 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: Brad Lemings [mailto:b...@rebit.com] > Sent: Friday, May 20, 2011 10:32 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Debugging Custom Actions > > Hi all, > > So I've added custom actions and conditions to run my service with > /install and /uninstall options before the service is started and > before it is deleted respectively. Here's the XML: > >FileKey="MySvcExe" > ExeCommand="/install" > Execute="deferred" /> >FileKey="MySvcExe" > ExeCommand="/uninstall" > Execute="deferred" /> > > After="InstallServices"> > NOT Installed > > Before="DeleteServices"> > Installed AND REMOVE~="ALL" > > > > The log shows this: > > ... > MSI (s) (EC:9C) [11:24:35:347]: Executing op: > ActionStart(Name=RunMySvcInstall,,) > MSI (s) (EC:9C) [11:24:35:347]: Executing op: > CustomActionSchedule(Action=RunMySvcInstall,ActionType=1042,Source=C: > \Program Files\My Svc\My-Svc.exe,Target=/install,) MSI (s) (EC:9C) > [11:24:35:831]: Note: 1: 1721 2: RunMySvcInstall 3: C:\Program > Files\My Svc\My-Svc.exe 4: /install MSI (s) (EC:9C) [11:24:35:831]: Note: 1: > 2205 2: 3: > Error MSI (s) (EC:9C) [11:24:35:831]: Note: 1: 2228 2: 3: Error 4: > SELECT `Message` FROM `Error` WHERE `Error` = 1721 MSI (c) (04:EC) > [11:24:35:847]: > Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS > Shell Dlg > > Error 1721. There is a problem with this Windows Installer package. A > program required for this install to complete could not be run. > Contact your support personnel or package vendor. Action: RunMySvcInstall, > location: > C:\Program Files\My Svc\My-Svc.exe, command: /install MSI (s) (EC:9C) > [11:24:45:409]: Note: 1: 2205 2: 3: Error MSI (s) (EC:9C) [11:24:45:409]: > Note: > 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = > 1709 MSI > (s) (EC:9C) [11:24:45:409]: Product: My Svc (64-bit) -- Error 1721. > There is a problem with this Windows Installer package. A
[WiX-users] Debugging Custom Actions
Hi all, So I've added custom actions and conditions to run my service with /install and /uninstall options before the service is started and before it is deleted respectively. Here's the XML: NOT Installed Installed AND REMOVE~="ALL" The log shows this: ... MSI (s) (EC:9C) [11:24:35:347]: Executing op: ActionStart(Name=RunMySvcInstall,,) MSI (s) (EC:9C) [11:24:35:347]: Executing op: CustomActionSchedule(Action=RunMySvcInstall,ActionType=1042,Source=C:\Program Files\My Svc\My-Svc.exe,Target=/install,) MSI (s) (EC:9C) [11:24:35:831]: Note: 1: 1721 2: RunMySvcInstall 3: C:\Program Files\My Svc\My-Svc.exe 4: /install MSI (s) (EC:9C) [11:24:35:831]: Note: 1: 2205 2: 3: Error MSI (s) (EC:9C) [11:24:35:831]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1721 MSI (c) (04:EC) [11:24:35:847]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: RunMySvcInstall, location: C:\Program Files\My Svc\My-Svc.exe, command: /install MSI (s) (EC:9C) [11:24:45:409]: Note: 1: 2205 2: 3: Error MSI (s) (EC:9C) [11:24:45:409]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (EC:9C) [11:24:45:409]: Product: My Svc (64-bit) -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: RunMySvcInstall, location: C:\Program Files\My Svc\My-Svc.exe, command: /install Action ended 11:24:45: InstallFinalize. Return value 3. ... Not much help there. How does one go about determining why the action/command failed? Thanks, Eric. -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Sent: Thursday, May 19, 2011 10:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Debugging/Troubleshooting Service Installs I dunno. I'm inclined to stick with the abstraction principle and trust that the /uninstall option will undo everything done by the /install option. So I only have two custom actions but several applicable scenarios: * Install - RunInstallCmd * Rollback Install - RunUninstallCmd * Repair - RunInstallCmd * Rollback Repair - no action (RunUninstallCmd would partially uninstall service) * Uninstall - RunUninstallCmd * Rollback Uninstall - RunInstallCmd * Upgrade - no action (unless this scenario is actually composed of install/uninstall scenarios) * Rollback Upgrade - no action (ditto) But theory and practice do no always coincide. I'll have to put my theories to the test. Eric. On May 19, 2011, at 5:56 PM, Castro, Edwin G. (Hillsboro) wrote: > My recommendation would be to perform any other activities that the service > performs itself during /install in a Windows Installer friendly fashion. The > reason is that Windows Installer (and WiX standard custom actions) behave > more robustly in the face of failures and associated rollback scenarios. > > If you do decide to use a custom action to execute "service.exe /install" and > "service.exe /uninstall" then remember to handle the following scenarios: > * Install > * Rollback Install > * Repair (Reinstall/Reconfigure) > * Rollback Repair (Reinstall/Reconfigure) > * Uninstall > * Rollback Uninstall > * Upgrade > * Rollback Upgrade > > That's a lot of custom actions and it's going to be very difficult to know > what to do in each scenario if you don't know what "service.exe /install" > does. > > 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: Brad Lemings [mailto:b...@rebit.com] >> Sent: Thursday, May 19, 2011 4:21 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Debugging/Troubleshooting Service Installs >> >> Hi Edwin, >> >> I suspected this would be the case -- writing a custom action. The >> service however must be executed with the /install option before it >> can be started so unless there's an alternative to writing a custom >> action, this is the only possible solution. >> >> Thanks for the help. >> >> Eric. >> >> -Original Message- >> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] >> Sent: Thursday, May 19, 2011 4:24 PM >> To: General discussion for Windows In
Re: [WiX-users] Debugging/Troubleshooting Service Installs
I dunno. I'm inclined to stick with the abstraction principle and trust that the /uninstall option will undo everything done by the /install option. So I only have two custom actions but several applicable scenarios: * Install - RunInstallCmd * Rollback Install - RunUninstallCmd * Repair - RunInstallCmd * Rollback Repair - no action (RunUninstallCmd would partially uninstall service) * Uninstall - RunUninstallCmd * Rollback Uninstall - RunInstallCmd * Upgrade - no action (unless this scenario is actually composed of install/uninstall scenarios) * Rollback Upgrade - no action (ditto) But theory and practice do no always coincide. I'll have to put my theories to the test. Eric. On May 19, 2011, at 5:56 PM, Castro, Edwin G. (Hillsboro) wrote: > My recommendation would be to perform any other activities that the service > performs itself during /install in a Windows Installer friendly fashion. The > reason is that Windows Installer (and WiX standard custom actions) behave > more robustly in the face of failures and associated rollback scenarios. > > If you do decide to use a custom action to execute "service.exe /install" and > "service.exe /uninstall" then remember to handle the following scenarios: > * Install > * Rollback Install > * Repair (Reinstall/Reconfigure) > * Rollback Repair (Reinstall/Reconfigure) > * Uninstall > * Rollback Uninstall > * Upgrade > * Rollback Upgrade > > That's a lot of custom actions and it's going to be very difficult to know > what to do in each scenario if you don't know what "service.exe /install" > does. > > Edwin G. Castro > Software Developer - Staff > Digital Channels > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > Please consider the environment before printing this e-mail > >> -Original Message- >> From: Brad Lemings [mailto:b...@rebit.com] >> Sent: Thursday, May 19, 2011 4:21 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Debugging/Troubleshooting Service Installs >> >> Hi Edwin, >> >> I suspected this would be the case -- writing a custom action. The service >> however must be executed with the /install option before it can be started >> so unless there's an alternative to writing a custom action, this is the only >> possible solution. >> >> Thanks for the help. >> >> Eric. >> >> -Original Message- >> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] >> Sent: Thursday, May 19, 2011 4:24 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Debugging/Troubleshooting Service Installs >> >> ... >> If you really want to execute your service with /install and /uninstall to >> install >> and uninstall then you'll need to schedule a custom action to execute your >> service appropriately. I would *highly* discourage this course of action. >> >> 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: Brad Lemings [mailto:b...@rebit.com] >>> Sent: Thursday, May 19, 2011 1:43 PM >>> To: General discussion for Windows Installer XML toolset. >>> Subject: Re: [WiX-users] Debugging/Troubleshooting Service Installs >>> >>> Followup. I have a better idea what the problem is. Either msiexec >>> is not "installing" the service by executing it with the proper >>> /install argument or it is not executing the install command with >> Administrator privileges. >>> >>>> From the log, it appears that the /install option is specified so I'm >>>> guessing >>> the latter case is the real problem although its somewhat >>> inconceivable that the ServiceControl element does not imply >> Administrator privileges. >>> >>> I'm guessing the Account and Password attributes are the real culprit. >>> Now to prove it... >>> >>> -Original Message- >>> From: Brad Lemings [mailto:b...@rebit.com] >>> Sent: Thursday, May 19, 2011 1:33 PM >>> To: General discussion for Windows Installer XML toolset. (wix- >>> us...@lists.sourceforge.net) >>> Subject: [WiX-users] Debugging/Troubleshooting Service Installs >>> >>> Greetings, >>> >>> The following excerpt of a Wix fil
Re: [WiX-users] Debugging/Troubleshooting Service Installs
Hi Edwin, I suspected this would be the case -- writing a custom action. The service however must be executed with the /install option before it can be started so unless there's an alternative to writing a custom action, this is the only possible solution. Thanks for the help. Eric. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, May 19, 2011 4:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Debugging/Troubleshooting Service Installs ... If you really want to execute your service with /install and /uninstall to install and uninstall then you'll need to schedule a custom action to execute your service appropriately. I would *highly* discourage this course of action. 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: Brad Lemings [mailto:b...@rebit.com] > Sent: Thursday, May 19, 2011 1:43 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Debugging/Troubleshooting Service Installs > > Followup. I have a better idea what the problem is. Either msiexec > is not "installing" the service by executing it with the proper > /install argument or it is not executing the install command with > Administrator privileges. > > >From the log, it appears that the /install option is specified so I'm > >guessing > the latter case is the real problem although its somewhat > inconceivable that the ServiceControl element does not imply Administrator > privileges. > > I'm guessing the Account and Password attributes are the real culprit. > Now to prove it... > > -Original Message- > From: Brad Lemings [mailto:b...@rebit.com] > Sent: Thursday, May 19, 2011 1:33 PM > To: General discussion for Windows Installer XML toolset. (wix- > us...@lists.sourceforge.net) > Subject: [WiX-users] Debugging/Troubleshooting Service Installs > > Greetings, > > The following excerpt of a Wix file is supposed to install, stop, > start, and uninstall a service (exact names have been tweaked): > > Guid="5E7A07C7-9299-4992-A601-EBB79D441A83" > Win64='$(var.Win64)'> > >Source='$(var.TARGET_DIR)\$(var.MY_SERVICE_OUTPUT_NAME)' > KeyPath='yes' Checksum='yes'/> > > Name="$(var.MY_SERVICE_SVC_NAME)" > DisplayName="$(var.MY_SERVICE_DISPLAY_NAME)" > Type="ownProcess" > Start="auto" > Arguments="/install" > ErrorControl="normal" > Description="$(var.MY_SERVICE_DESCRIPTION)" > Account="[SERVICEACCOUNT]" > Password="[SERVICEPASSWORD]" /> > Name="$(var.MY_SERVICE_SVC_NAME)" > Start="install" > Wait="yes" /> > Name="$(var.MY_SERVICE_SVC_NAME)" > Stop="both" > Wait="yes" /> > Name="$(var.MY_SERVICE_SVC_NAME)" > Remove="uninstall" > > /uninstall > > > > I'm trying to install the resulting .MSI with the following command: > > msiexec /norestart /lvx*+ mysvc.log /i mysvc.msi > > The install fails and msiexec reports via GUI that the service failed to > start. > Part of the log shows this: > > MSI (s) (2C:D8) [13:17:05:419]: Executing op: RegCreateKey() MSI (s) > (2C:D8) > [13:17:05:419]: Executing op: > ActionStart(Name=InstallServices,Description=Installing new > services,Template=Service: [2]) MSI (s) (2C:D8) [13:17:05:419]: Executing op: > ProgressTotal(Total=1,Type=1,ByteEquivalent=130) > MSI (s) (2C:D8) [13:17:05:419]: Executing op: ServiceInstall(Name=My- > Svc,DisplayName=My Svc,ImagePath="C:\Program Files\My\My-Svc.exe" > /install,ServiceType=16,StartType=2,ErrorControl=1,,Dependencies=[~],, > ,Pas sword=**,Description=My Backup Service,,) MSI (s) (2C:D8) > [13:17:06:060]: Executing op: > ActionStart(Name=RollbackServiceConfig,,) > MSI (s) (2C:D8) [13:17:06:060]: Executing op: > CustomActionSchedule(Action=RollbackServiceConfig,Actio
Re: [WiX-users] Debugging/Troubleshooting Service Installs
Followup. I have a better idea what the problem is. Either msiexec is not "installing" the service by executing it with the proper /install argument or it is not executing the install command with Administrator privileges. >From the log, it appears that the /install option is specified so I'm guessing >the latter case is the real problem although its somewhat inconceivable that >the ServiceControl element does not imply Administrator privileges. I'm guessing the Account and Password attributes are the real culprit. Now to prove it... -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Sent: Thursday, May 19, 2011 1:33 PM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Subject: [WiX-users] Debugging/Troubleshooting Service Installs Greetings, The following excerpt of a Wix file is supposed to install, stop, start, and uninstall a service (exact names have been tweaked): /uninstall I'm trying to install the resulting .MSI with the following command: msiexec /norestart /lvx*+ mysvc.log /i mysvc.msi The install fails and msiexec reports via GUI that the service failed to start. Part of the log shows this: MSI (s) (2C:D8) [13:17:05:419]: Executing op: RegCreateKey() MSI (s) (2C:D8) [13:17:05:419]: Executing op: ActionStart(Name=InstallServices,Description=Installing new services,Template=Service: [2]) MSI (s) (2C:D8) [13:17:05:419]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (2C:D8) [13:17:05:419]: Executing op: ServiceInstall(Name=My-Svc,DisplayName=My Svc,ImagePath="C:\Program Files\My\My-Svc.exe" /install,ServiceType=16,StartType=2,ErrorControl=1,,Dependencies=[~],,,Password=**,Description=My Backup Service,,) MSI (s) (2C:D8) [13:17:06:060]: Executing op: ActionStart(Name=RollbackServiceConfig,,) MSI (s) (2C:D8) [13:17:06:060]: Executing op: CustomActionSchedule(Action=RollbackServiceConfig,ActionType=3329,Source=BinaryData,Target=RollbackServiceConfig,CustomActionData=SchedServiceConfig) MSI (s) (2C:D8) [13:17:06:060]: Executing op: ActionStart(Name=ExecServiceConfig,,) MSI (s) (2C:D8) [13:17:06:060]: Executing op: CustomActionSchedule(Action=ExecServiceConfig,ActionType=3073,Source=BinaryData,Target=ExecServiceConfig,CustomActionData=SchedServiceConfigEURMy-SvcEUR0EURrestartEURrestartEURnoneEUR1EUR60EUREUR) MSI (s) (2C:D8) [13:17:06:060]: Creating MSIHANDLE (8) of type 790536 for thread 1496 MSI (s) (2C:34) [13:17:06:060]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIC5E2.tmp, Entrypoint: ExecServiceConfig MSI (s) (2C:20) [13:17:06:060]: Generating random cookie. MSI (s) (2C:20) [13:17:06:075]: Created Custom Action Server with PID 784 (0x310). MSI (s) (2C:78) [13:17:06:091]: Running as a service. MSI (s) (2C:78) [13:17:06:091]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (2C!B8) [13:17:06:263]: Creating MSIHANDLE (9) of type 790531 for thread 3000 MSI (s) (2C!B8) [13:17:06:263]: Closing MSIHANDLE (9) of type 790531 for thread 3000 MSI (s) (2C:34) [13:17:06:263]: Closing MSIHANDLE (8) of type 790536 for thread 1496 MSI (s) (2C:D8) [13:17:06:263]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1]) MSI (s) (2C:D8) [13:17:06:263]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (2C:D8) [13:17:06:263]: Executing op: ServiceControl(,Name=My-Svc,Action=1,Wait=1,) MSI (s) (2C:D8) [13:17:36:310]: Note: 1: 2205 2: 3: Error MSI (s) (2C:D8) [13:17:36:310]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1920 MSI (c) (FC:38) [13:17:36:310]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1920. Service 'My Svc' (My-Svc) failed to start. Verify that you have sufficient privileges to start system services. MSI (s) (2C:D8) [13:17:49:482]: Note: 1: 2205 2: 3: Error MSI (s) (2C:D8) [13:17:49:482]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (2C:D8) [13:17:49:482]: Product: My (64-bit) -- Error 1920. Service 'My Svc' (My-Svc) failed to start. Verify that you have sufficient privileges to start system services. MSI (s) (2C:D8) [13:18:19:482]: Note: 1: 2205 2: 3: Error MSI (s) (2C:D8) [13:18:19:482]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1920 MSI (c) (FC:38) [13:18:19:482]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1920. Service 'My Svc' (My-Svc) failed to start. Verify that you have sufficient privileges to start system services. MSI (s) (2C:F0) [13:18:21:216]: I/O on thread 1796 could not be cancelled. Error: 1168 Even with all information being logged, there still isn't enough to determine the problem
[WiX-users] Debugging/Troubleshooting Service Installs
Greetings, The following excerpt of a Wix file is supposed to install, stop, start, and uninstall a service (exact names have been tweaked): /uninstall I'm trying to install the resulting .MSI with the following command: msiexec /norestart /lvx*+ mysvc.log /i mysvc.msi The install fails and msiexec reports via GUI that the service failed to start. Part of the log shows this: MSI (s) (2C:D8) [13:17:05:419]: Executing op: RegCreateKey() MSI (s) (2C:D8) [13:17:05:419]: Executing op: ActionStart(Name=InstallServices,Description=Installing new services,Template=Service: [2]) MSI (s) (2C:D8) [13:17:05:419]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (2C:D8) [13:17:05:419]: Executing op: ServiceInstall(Name=My-Svc,DisplayName=My Svc,ImagePath="C:\Program Files\My\My-Svc.exe" /install,ServiceType=16,StartType=2,ErrorControl=1,,Dependencies=[~],,,Password=**,Description=My Backup Service,,) MSI (s) (2C:D8) [13:17:06:060]: Executing op: ActionStart(Name=RollbackServiceConfig,,) MSI (s) (2C:D8) [13:17:06:060]: Executing op: CustomActionSchedule(Action=RollbackServiceConfig,ActionType=3329,Source=BinaryData,Target=RollbackServiceConfig,CustomActionData=SchedServiceConfig) MSI (s) (2C:D8) [13:17:06:060]: Executing op: ActionStart(Name=ExecServiceConfig,,) MSI (s) (2C:D8) [13:17:06:060]: Executing op: CustomActionSchedule(Action=ExecServiceConfig,ActionType=3073,Source=BinaryData,Target=ExecServiceConfig,CustomActionData=SchedServiceConfigEURMy-SvcEUR0EURrestartEURrestartEURnoneEUR1EUR60EUREUR) MSI (s) (2C:D8) [13:17:06:060]: Creating MSIHANDLE (8) of type 790536 for thread 1496 MSI (s) (2C:34) [13:17:06:060]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIC5E2.tmp, Entrypoint: ExecServiceConfig MSI (s) (2C:20) [13:17:06:060]: Generating random cookie. MSI (s) (2C:20) [13:17:06:075]: Created Custom Action Server with PID 784 (0x310). MSI (s) (2C:78) [13:17:06:091]: Running as a service. MSI (s) (2C:78) [13:17:06:091]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (2C!B8) [13:17:06:263]: Creating MSIHANDLE (9) of type 790531 for thread 3000 MSI (s) (2C!B8) [13:17:06:263]: Closing MSIHANDLE (9) of type 790531 for thread 3000 MSI (s) (2C:34) [13:17:06:263]: Closing MSIHANDLE (8) of type 790536 for thread 1496 MSI (s) (2C:D8) [13:17:06:263]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1]) MSI (s) (2C:D8) [13:17:06:263]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (2C:D8) [13:17:06:263]: Executing op: ServiceControl(,Name=My-Svc,Action=1,Wait=1,) MSI (s) (2C:D8) [13:17:36:310]: Note: 1: 2205 2: 3: Error MSI (s) (2C:D8) [13:17:36:310]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1920 MSI (c) (FC:38) [13:17:36:310]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1920. Service 'My Svc' (My-Svc) failed to start. Verify that you have sufficient privileges to start system services. MSI (s) (2C:D8) [13:17:49:482]: Note: 1: 2205 2: 3: Error MSI (s) (2C:D8) [13:17:49:482]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (2C:D8) [13:17:49:482]: Product: My (64-bit) -- Error 1920. Service 'My Svc' (My-Svc) failed to start. Verify that you have sufficient privileges to start system services. MSI (s) (2C:D8) [13:18:19:482]: Note: 1: 2205 2: 3: Error MSI (s) (2C:D8) [13:18:19:482]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1920 MSI (c) (FC:38) [13:18:19:482]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1920. Service 'My Svc' (My-Svc) failed to start. Verify that you have sufficient privileges to start system services. MSI (s) (2C:F0) [13:18:21:216]: I/O on thread 1796 could not be cancelled. Error: 1168 Even with all information being logged, there still isn't enough to determine the problem. When I don't abort the install and the files are copied into their final resting places, I can execute the following commands without any errors: My-Svc.exe /install sc start My-Svc So it must be something wrong with the Wix file. Any clues why the service fails to start? Any tips, references, resources, links useful for debugging service installs using Wix? Any and all help appreciated. Eric. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourcef
[WiX-users] Grouping Merge Modules?
Currently, I have a .wxs file with the following: ... ... ... I was wondering if and how these merge modules could be grouped somehow and referenced with a single Wix element. Thanks. P.S. Sorry for the HTML. Is plain text the preferred format? P.S.S. If this is answered somewhere already (e.g. a FAQ), please send a link! -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to use a particular version of runtime merge modules?
Only way to obtain Orca currently is to install the latest Windows SDK? -Original Message- From: Francisco Gabriel Malbrán [mailto:fgmalb...@gmail.com] Sent: Wednesday, May 18, 2011 9:54 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to use a particular version of runtime merge modules? 1. Open the msm with Orca 2. Go to the file table 3. Check out the "Version" column 2011/5/18 Brad Lemings > Moving to the latest runtime version means a couple days work > rebuilding/redistributing our 3rd-party tools. That's about the only > reason. > > Given a particular .msm file, how does one "inspect" the file, to > determine the version in particular? > > -Original Message- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Wednesday, May 18, 2011 3:38 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] How to use a particular version of runtime > merge modules? > > Make sure the machine you build your package on has that version of > Visual Studio installed & it will have the corresponding merge modules > in the Common Files area then just link them as usual. > Visual Studio installs the same version of merge modules as itself. It > doesn't keep a repository of previous versions or anything. > However you would probably be better off submitting the specific > version of the runtime merge modules to your source control & then > linking them into your package from there. If your binaries are built > on one machine & your package on another you may find they get out of > sync due to Windows Updates & your app then fails to launch after > installation with a Side-by-Side error (someone posted this exact same > issue not too long ago). If updates to your machines are controlled by > your company using WSUS or something similar & you can be 100% sure no > one will approve any Visual Studio 2008 updates which will change that > version then you could live with the ones in Common Files but personally I > wouldn't risk it. > > Any reason why you need to stick to a specific version? Most up to > date version as of last month is 9.0.30729.5570 as far as I can see > which resolves some pretty major security exploits. > > Palbinder Sandher > Software Deployment Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the ** > 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: Brad Lemings [mailto:b...@rebit.com] > Sent: 18 May 2011 03:22 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] How to use a particular version of runtime > mergemodules? > > > All of our software - both 3rd-party and in-house - is built against a > particular version of the VS/VC runtimes - specifically "9.0.30729.4148". > > How does one utilize merge modules in Wix sources using a particular > manifest/version of the VS/VC runtimes? > > Thanks, > Eric. > > > -- > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applicatio
Re: [WiX-users] How to use a particular version of runtime merge modules?
I'll give that a try. Thanks. -Original Message- From: Rob Hamflett [mailto:r...@snsys.com] Sent: Wednesday, May 18, 2011 9:34 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to use a particular version of runtime merge modules? I'd definitely include the policy modules. I took them out after reading the referenced comment in the WiX doc, and then a Visual Studio update broke our installation. Visual Studio was building against one version of the runtime and the merge modules were distributing another. Re-adding the policy merge module fixed things. Rob On 18/05/2011 13:49, Francisco Gabriel Malbrán wrote: > You may also consider installing the policy redistributable merge module. > Although WiX's documentation says you probably shouldn't need it, it > does not say that you will *definitely* not need it. > I haven't found much information on the policy merge module, but > enough to know that it basically serves the purpose of redirection > when a different > (lower) version of the redistributable is asked for and you happen not > to have exactly that one. > > People in the list will probably know more on the subject, but I just > wanted to pointed out. > > Regards > > 2011/5/18 Pally Sandher > >> Make sure the machine you build your package on has that version of >> Visual Studio installed& it will have the corresponding merge >> modules in the Common Files area then just link them as usual. >> Visual Studio installs the same version of merge modules as itself. >> It doesn't keep a repository of previous versions or anything. >> However you would probably be better off submitting the specific >> version of the runtime merge modules to your source control& then >> linking them into your package from there. If your binaries are built >> on one machine& your package on another you may find they get out of >> sync due to Windows Updates & your app then fails to launch after >> installation with a Side-by-Side error (someone posted this exact >> same issue not too long ago). If updates to your machines are >> controlled by your company using WSUS or something similar& you can >> be 100% sure no one will approve any Visual Studio 2008 updates which >> will change that version then you could live with the ones in Common Files >> but personally I wouldn't risk it. >> >> Any reason why you need to stick to a specific version? Most up to >> date version as of last month is 9.0.30729.5570 as far as I can see >> which resolves some pretty major security exploits. >> >> Palbinder Sandher >> Software Deployment Engineer >> T: +44 (0) 141 945 8500 >> F: +44 (0) 141 945 8501 >> >> http://www.iesve.com >> **Design, Simulate + Innovate with the** >> 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: Brad Lemings [mailto:b...@rebit.com] >> Sent: 18 May 2011 03:22 >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] How to use a particular version of runtime >> mergemodules? >> >> >> All of our software - both 3rd-party and in-house - is built against >> a particular version of the VS/VC runtimes - specifically "9.0.30729.4148". >> >> How does one utilize merge modules in Wix sources using a particular >> manifest/version of the VS/VC runtimes? >> >> Thanks, >> Eric. >> >> >> - >> - What Every C/C++ and Fortran developer Should Know! >> Read this article and learn how Intel has extended the reach of its >> next-generation tools to help Windows* and Linux* C/C++ and Fortran >> developers boost performance applications - including clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> >> - >> - What Every C/C++ and Fortran developer Should Know! >> Read this article and learn how Intel has extended the reach of its >> next-generation tools to help Windows* and Linux* C/C++ and Fortran >> developers boost performance applications - including clusters. >> http://p.sf.net/sfu/intel-dev2devmay >
Re: [WiX-users] How to use a particular version of runtime merge modules?
Moving to the latest runtime version means a couple days work rebuilding/redistributing our 3rd-party tools. That's about the only reason. Given a particular .msm file, how does one "inspect" the file, to determine the version in particular? -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, May 18, 2011 3:38 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to use a particular version of runtime merge modules? Make sure the machine you build your package on has that version of Visual Studio installed & it will have the corresponding merge modules in the Common Files area then just link them as usual. Visual Studio installs the same version of merge modules as itself. It doesn't keep a repository of previous versions or anything. However you would probably be better off submitting the specific version of the runtime merge modules to your source control & then linking them into your package from there. If your binaries are built on one machine & your package on another you may find they get out of sync due to Windows Updates & your app then fails to launch after installation with a Side-by-Side error (someone posted this exact same issue not too long ago). If updates to your machines are controlled by your company using WSUS or something similar & you can be 100% sure no one will approve any Visual Studio 2008 updates which will change that version then you could live with the ones in Common Files but personally I wouldn't risk it. Any reason why you need to stick to a specific version? Most up to date version as of last month is 9.0.30729.5570 as far as I can see which resolves some pretty major security exploits. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Brad Lemings [mailto:b...@rebit.com] Sent: 18 May 2011 03:22 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to use a particular version of runtime mergemodules? All of our software - both 3rd-party and in-house - is built against a particular version of the VS/VC runtimes - specifically "9.0.30729.4148". How does one utilize merge modules in Wix sources using a particular manifest/version of the VS/VC runtimes? Thanks, Eric. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to use a particular version of runtime merge modules?
All of our software – both 3rd-party and in-house – is built against a particular version of the VS/VC runtimes – specifically "9.0.30729.4148". How does one utilize merge modules in Wix sources using a particular manifest/version of the VS/VC runtimes? Thanks, Eric. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
