[WiX-users] UNSUBSCRIBE
UNSUBSCRIBE -- 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] Bootstrapper upgrade code detection
Hey, Alexander. Try to use DetectRelatedMsiPackage. It detects installed products based on Upgrade Code, but not on Product Code. Best regards, Vadym -- Date: Mon, 4 Jul 2011 10:52:50 +0200 From: Alexander Kriv?cs Schr?deralexander.schro...@mermaid.no Subject: [WiX-users] Bootstrapper upgrade code detection To: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Message-ID: 17860180d1bd8c41abece6ac6f36239c6e6ba7d...@htv-mail01.headline.tv Content-Type: text/plain; charset=iso-8859-1 Hey. According to the Windows Installer specifications, we change the Product Code of our product with every release (We just use Product Id=* ... /) and we keep the Upgrade Code the same. That way, when the individual MSIs are run, if any previous versions exist, they are first uninstalled. At the moment, we're making a bootstrapper for our products, and in this process, we're also making a custom managed GUI. It detects if a product is already installed (its PackageState is reported as PackageState.Present) or not installed (PackageState.Absent). However, if a product is installed, but the bootstrapper contains a newer version of the product, it is reported as PackageState.Absent, not PackageState.Superseded, like one would expect. Is there anything in particular we need to do in order to get this upgrade detection mechanism to work? Best regards ALEXANDER K. SCHR?DER SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- 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] Using the same component in different features
Hi Rob, Appreciate your reply on this and will look through the MSI SDK to understand this. Regards, Anil. On Mon, Jul 4, 2011 at 6:29 PM, Rob Mensching r...@robmensching.com wrote: What you are describing is the expected behavior of the Windows Installer. The MSI SDK explains the Windows Installer behavior in a lot of detail... but is pretty dense material. On Fri, Jul 1, 2011 at 8:32 AM, Anil Patel apatel...@googlemail.com wrote: Hello, As this is my first time in authoring WiX source files, I have a need to use the same component group (hence components) in different features. The 'shared' components will only ever be installed in one location. What I would like to understand is if there are any dangers in this doing this? I have also noticed that if I uninstall a feature, the 'shared' components within that feature are not deleted. I can see why this is the case as there is another feature referencing it but how does the Windows Installer do this? The features themselves have no unique identifiers (ie no GUIDs) other than the string feature id which have to be unique. Many thanks, Anil. -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC -- 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] Run a custom exe with administrator privileges with burn
Hi, I want to start an application after burn has finished setup. This appliation needs administrator privileges. Is it possible start the application without prompting for elevation (using the same elevation mechanism as the setup)? Michael -- 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] Problem with Win7
Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? 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
Re: [WiX-users] Run a custom exe with administrator privileges with burn
If you run a process that requires admin privileges then it will prompt, unless you run it from a process that is already elevated. If Burn is elevated then you'll be fine, otherwise you'll get the prompt. Rob On 05/07/2011 11:30, Michael Stoll wrote: Hi, I want to start an application after burn has finished setup. This appliation needs administrator privileges. Is it possible start the application without prompting for elevation (using the same elevation mechanism as the setup)? Michael -- 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 -- 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] Problem with Win7
Check a verbose log. 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 Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: yheip p [mailto:zyhp...@gmail.com] Sent: 05 July 2011 11:51 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem with Win7 Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? 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
Re: [WiX-users] Bootstrapper upgrade code detection
I'm using Burn v3.6.1803.0. Here's the detect section of the log file: [1708:1F44][2011-07-05T12:35:51.683+01:00]: Detect 11 packages [1708:1F44][2011-07-05T12:35:52.097+01:00]: Condition 'Netfx4FullVersion AND (NOT VersionNT64 OR Netfx4x64FullVersion)' evaluates to true. [1708:1F44][2011-07-05T12:35:52.097+01:00]: Detected package: Netfx4Full, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.117+01:00]: Detect 1 msi features for package: ReactiveFramework [1708:1F44][2011-07-05T12:35:52.158+01:00]: Detected feature: ProductFeature, state: Local [1708:1F44][2011-07-05T12:35:52.161+01:00]: Detected package: ReactiveFramework, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.162+01:00]: Detect 1 msi features for package: SyncFramework.Synchronization [1708:1F44][2011-07-05T12:35:52.174+01:00]: Detected feature: Feature_Synchronization_Core, state: Local [1708:1F44][2011-07-05T12:35:52.174+01:00]: Detected package: SyncFramework.Synchronization, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.175+01:00]: Detect 1 msi features for package: SyncFramework.ProviderServices [1708:1F44][2011-07-05T12:35:52.176+01:00]: Detected feature: Feature_FileSync_Provider, state: Absent [1708:1F44][2011-07-05T12:35:52.176+01:00]: Detected package: SyncFramework.ProviderServices, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.177+01:00]: Detect 1 msi features for package: SyncFramework.DatabaseProviders [1708:1F44][2011-07-05T12:35:52.187+01:00]: Detected feature: OCS_v2.0_Core, state: Local [1708:1F44][2011-07-05T12:35:52.187+01:00]: Detected package: SyncFramework.DatabaseProviders, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.187+01:00]: Condition 'SqlCeVersion=v3.5.8080.0 AND SqlCeServicePackLevel=2' evaluates to true. [1708:1F44][2011-07-05T12:35:52.187+01:00]: Detected package: SqlCompactEdition, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.190+01:00]: Detect 1 msi features for package: Headline.Operations [1708:1F44][2011-07-05T12:35:52.190+01:00]: Detected feature: Operations.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.190+01:00]: Detected package: Headline.Operations, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.192+01:00]: Detect 1 msi features for package: Headline.ChannelBuilder [1708:1F44][2011-07-05T12:35:52.192+01:00]: Detected feature: ChannelBuilder.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.214+01:00]: Detected package: Headline.ChannelBuilder, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.224+01:00]: Detect 3 msi features for package: Headline.Client [1708:1F44][2011-07-05T12:35:52.224+01:00]: Detected feature: PublicEnvironmentVariable.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.230+01:00]: Detected feature: ClientPDB.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.230+01:00]: Detected feature: Client.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.230+01:00]: Detected package: Headline.Client, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.235+01:00]: Detect 1 msi features for package: Headline.Agent [1708:1F44][2011-07-05T12:35:52.235+01:00]: Detected feature: Agent.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.243+01:00]: Detected package: Headline.Agent, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.248+01:00]: Detect 5 msi features for package: Headline.Player [1708:1F44][2011-07-05T12:35:52.248+01:00]: Detected feature: DirectXRedist, state: Absent [1708:1F44][2011-07-05T12:35:52.270+01:00]: Detected feature: AppConfig.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.270+01:00]: Detected feature: Player.Plugins.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.270+01:00]: Detected feature: Player.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.271+01:00]: Detected feature: PlayerPDB.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.274+01:00]: Detected package: Headline.Player, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.279+01:00]: Detect complete, result: 0x0 The relevant package here is Headline.Agent. It is installed with version 3.5.10617 and this bootstrapper has version 3.5.10704. Best regards ALEXANDER K. SCHRØDER -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 4. juli 2011 19:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrapper upgrade code detection What version of Burn are you using? Can you share out the detect section of the Burn log file? On Mon, Jul 4, 2011 at 4:58 AM, Rob Hamflett r...@snsys.com wrote: Ah. I haven't looked at Burn. Sorry. Hopefully someone else has the answer to that one. Rob On 04/07/2011 12:13, Alexander Krivács Schrøder wrote: Hi Rob. I probably should have mentioned that the bootstrapper we're using is WiX's burn, and the managed GUI we're making is for it. The BootstrapperApplication class has an event
Re: [WiX-users] Problem with Win7
Is it Win7 64 bit? If so, are you sure the correct registry is being checked/written to (32-bit vs. 64-bit)? -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, July 05, 2011 6:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem with Win7 Check a verbose log. 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 Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: yheip p [mailto:zyhp...@gmail.com] Sent: 05 July 2011 11:51 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem with Win7 Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? 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] Problem with Win7
Is the problem on a 32 bit or 64 bit system? Make sure the registry search matches the bit level that was set for component containing the initial registry write. -Original Message- From: yheip p [mailto:zyhp...@gmail.com] Sent: Tuesday, July 05, 2011 5:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem with Win7 Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? 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
Re: [WiX-users] Buirn Queries
What kind of code are you trying to run? You can definitely run an ExePackage (EXE file) at any point before, after, between installing any of your 3 MSI files, without writing a complete BA. It's true you cannot run the UI inside the MSI though. However, and this is an ugly hack, but I have had some success doing this: I wrote an EXE RunCommand.exe that just runs commands, since it seems ExePackage is limited to files that are part of the bootstrapper. Then have that run something like msiexec /i MyMSI.msi with the parameters for installing and showing your MSI UI. -Original Message- From: John Robbins [mailto:j...@wintellect.com] Sent: Saturday, July 02, 2011 2:36 PM To: General discussion for Windows Installer XML toolset.; sean.far...@seanfarrow.co.uk Subject: Re: [WiX-users] Buirn Queries Hi, Do run code you'll need to write a complete BA like the WiX36.exe. See src\Setup\UX for the code. As of today there's no way to run UI that's inside the MSI. John Wintellect http://www.wintellect.com +1-877-968-5528 -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Saturday, July 02, 2011 9:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Buirn Queries Hi All: I'm currently using burn and have a few questions: Is there a way to run code before/after installing a particular msi. For Example, I am installing 3 msi's, I install msi 1, and then would like to run some code before installing msi 2-is this doable. Secondly, is there a way to show the msi ui instead of a burn user interface? Any help appreciated. Cheers Sean. -- 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] Run a custom exe with administrator privileges with burn
I don't know much about how Burn works, sorry. The only thing that springs to mind is if Burn itself was elevated. Rob On 05/07/2011 14:54, Michael Stoll wrote: I tried starting the application in the close command of the mba. But then the user is prompted twice for administration privileges (Once by burn and once by the app). So I assume that the UI is running without elevation. Is it possible to tell burn to run the application from within the elevated process? Michael Am 05.07.2011 12:51, schrieb Rob Hamflett: If you run a process that requires admin privileges then it will prompt, unless you run it from a process that is already elevated. If Burn is elevated then you'll be fine, otherwise you'll get the prompt. Rob On 05/07/2011 11:30, Michael Stoll wrote: Hi, I want to start an application after burn has finished setup. This appliation needs administrator privileges. Is it possible start the application without prompting for elevation (using the same elevation mechanism as the setup)? Michael -- 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 -- 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 -- 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] Bootstrapper upgrade code detection
Okay, Vadym is pointing you in the right direction. DetectPackage tells you the state of *this* package where package is defined by ProductCode. You will get superseded from DetectPackage only when you try to install the same ProductCode with a lower version number (basically a minor downgrade). DetectRelatedPackage tells you the states of packages that share an UpgradeCode. You'll get superseded there if there is a package with same upgrade code and higher version (basically a major downgrade). These messages are separate to enable you to detect both minor upgrades (DetectPackage) and major upgrades (DetectRelatedPackage). Plus a bunch of other pure detection scenarios with DetectRelatedPackage(). 2011/7/5 Alexander Krivács Schrøder alexander.schro...@mermaid.no I'm using Burn v3.6.1803.0. Here's the detect section of the log file: [1708:1F44][2011-07-05T12:35:51.683+01:00]: Detect 11 packages [1708:1F44][2011-07-05T12:35:52.097+01:00]: Condition 'Netfx4FullVersion AND (NOT VersionNT64 OR Netfx4x64FullVersion)' evaluates to true. [1708:1F44][2011-07-05T12:35:52.097+01:00]: Detected package: Netfx4Full, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.117+01:00]: Detect 1 msi features for package: ReactiveFramework [1708:1F44][2011-07-05T12:35:52.158+01:00]: Detected feature: ProductFeature, state: Local [1708:1F44][2011-07-05T12:35:52.161+01:00]: Detected package: ReactiveFramework, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.162+01:00]: Detect 1 msi features for package: SyncFramework.Synchronization [1708:1F44][2011-07-05T12:35:52.174+01:00]: Detected feature: Feature_Synchronization_Core, state: Local [1708:1F44][2011-07-05T12:35:52.174+01:00]: Detected package: SyncFramework.Synchronization, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.175+01:00]: Detect 1 msi features for package: SyncFramework.ProviderServices [1708:1F44][2011-07-05T12:35:52.176+01:00]: Detected feature: Feature_FileSync_Provider, state: Absent [1708:1F44][2011-07-05T12:35:52.176+01:00]: Detected package: SyncFramework.ProviderServices, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.177+01:00]: Detect 1 msi features for package: SyncFramework.DatabaseProviders [1708:1F44][2011-07-05T12:35:52.187+01:00]: Detected feature: OCS_v2.0_Core, state: Local [1708:1F44][2011-07-05T12:35:52.187+01:00]: Detected package: SyncFramework.DatabaseProviders, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.187+01:00]: Condition 'SqlCeVersion=v3.5.8080.0 AND SqlCeServicePackLevel=2' evaluates to true. [1708:1F44][2011-07-05T12:35:52.187+01:00]: Detected package: SqlCompactEdition, state: Present, cached: No [1708:1F44][2011-07-05T12:35:52.190+01:00]: Detect 1 msi features for package: Headline.Operations [1708:1F44][2011-07-05T12:35:52.190+01:00]: Detected feature: Operations.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.190+01:00]: Detected package: Headline.Operations, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.192+01:00]: Detect 1 msi features for package: Headline.ChannelBuilder [1708:1F44][2011-07-05T12:35:52.192+01:00]: Detected feature: ChannelBuilder.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.214+01:00]: Detected package: Headline.ChannelBuilder, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.224+01:00]: Detect 3 msi features for package: Headline.Client [1708:1F44][2011-07-05T12:35:52.224+01:00]: Detected feature: PublicEnvironmentVariable.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.230+01:00]: Detected feature: ClientPDB.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.230+01:00]: Detected feature: Client.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.230+01:00]: Detected package: Headline.Client, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.235+01:00]: Detect 1 msi features for package: Headline.Agent [1708:1F44][2011-07-05T12:35:52.235+01:00]: Detected feature: Agent.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.243+01:00]: Detected package: Headline.Agent, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.248+01:00]: Detect 5 msi features for package: Headline.Player [1708:1F44][2011-07-05T12:35:52.248+01:00]: Detected feature: DirectXRedist, state: Absent [1708:1F44][2011-07-05T12:35:52.270+01:00]: Detected feature: AppConfig.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.270+01:00]: Detected feature: Player.Plugins.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.270+01:00]: Detected feature: Player.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.271+01:00]: Detected feature: PlayerPDB.Feature, state: Absent [1708:1F44][2011-07-05T12:35:52.274+01:00]: Detected package: Headline.Player, state: Absent, cached: No [1708:1F44][2011-07-05T12:35:52.279+01:00]: Detect complete, result: 0x0 The relevant package here is Headline.Agent. It is installed with version 3.5.10617 and
Re: [WiX-users] Run a custom exe with administrator privileges with burn
Burn doesn't have anything built in to do this yet, although we've talked about it a lot. Currently, you'd have to schedule your ExePackage as the last thing in the Chain and mark it @PerMachine=yes. Then you'd have to have your BA or a very cleverly designed InstallCondtiion control when the ExePackage was installed (aka: launched). All of that is undoubtedly a hassle. Adding the feature to Burn just requires figuring out all the right ttimes to launch a configuration thing... and when. On Tue, Jul 5, 2011 at 7:03 AM, Rob Hamflett r...@snsys.com wrote: I don't know much about how Burn works, sorry. The only thing that springs to mind is if Burn itself was elevated. Rob On 05/07/2011 14:54, Michael Stoll wrote: I tried starting the application in the close command of the mba. But then the user is prompted twice for administration privileges (Once by burn and once by the app). So I assume that the UI is running without elevation. Is it possible to tell burn to run the application from within the elevated process? Michael Am 05.07.2011 12:51, schrieb Rob Hamflett: If you run a process that requires admin privileges then it will prompt, unless you run it from a process that is already elevated. If Burn is elevated then you'll be fine, otherwise you'll get the prompt. Rob On 05/07/2011 11:30, Michael Stoll wrote: Hi, I want to start an application after burn has finished setup. This appliation needs administrator privileges. Is it possible start the application without prompting for elevation (using the same elevation mechanism as the setup)? Michael -- 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 -- 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 -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC -- 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: Directory Id=CompanyInstallDir Name=MyCompany ... Directory Id=ProductInstallDir Name= MyProduct ... !-- features, components, etc... -- /Directory /Directory 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] Install Directory Structures
Off the top of my head, so no guarantees given ... You could do it if you were prepared to pass (or write a program to pass) public directory properties on the command line. Something like this: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLDIR Name=ApplicationX Directory Id=LEVEL1 Name=SomeSubDir Directory Id=LEVEL2 Name=MmmmSubs And then pass the same directory path in the INSTALLDIR, LEVEL1 and LEVEL2 properties. You'd have to be careful you don't have the same components or resources occurring at multiple levels or you'd get files overwriting each other and uninstall problems. -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Sent: 05 July 2011 17:32 To: General discussion for Windows Installer XML toolset. Subject: [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: Directory Id=CompanyInstallDir Name=MyCompany ... Directory Id=ProductInstallDir Name= MyProduct ... !-- features, components, etc... -- /Directory /Directory 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 SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- 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] HEAT5150 and ATL registrar
Hi all - I'm working on an install with a somewhat large number of older COM objects and .NET classes exposed to COM. For the most part, heat.exe works very well to move away from self-registration; very impressive. We have had some issues, like how to deal with the inability of heat to harvest EXE servers. For those I used RegSpy2 (the one on installsite.org) to create .reg files, which can then be used to create .wxs files. The other issue is how to deal with the infamous HEAT5150 warning. Admittedly we have only a few legacy DLL's which are affected. Regspy2 harvests registry entries for these just fine, and I was curious to know why.. After looking through the regspy2 code, and then the Wix UtilExtension code, I realized that they were doing basically the same things -- registry redirection using RegOverridePredefKey. The difference was that regspy2 was initializing the redirected registry with entries for the ATL Registrar COM object (see CreateAtlRegistrar in the regspy2 source code), which enabled these ancient DLL's to self-register. I might modify my copy of UtilExtension, and perhaps add some hack like an -atl switch to enable a similar feature in heat.exe (if I make any progress on getting the source to build :), but primarily wanted to share this observation. Cheers ! -Rob -- 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] Can an x86 msi create a registry key under HKEY_CLASSES_ROOT\Wow6432Node on x64 systems?
Hi David, Thanks for the information. I'm writing the registry data to HKLM\Software\Classes since the is a per machine installer. Thanks a lot, Miaohsi -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Thursday, June 30, 2011 10:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Can an x86 msi create a registry key under HKEY_CLASSES_ROOT\Wow6432Node on x64 systems? 32 bit (x86) installers can indeed write to wow6432nodes and do so by by default. Specify the key you wish to write to and omit Wow6432Node as they will be redirected there automatically. http://wix.sourceforge.net/manual-wix3/write_a_registry_entry.htm Its also worth noting that Microsoft say it is bad form to actually write to HKCR directly (its behaviour depends on the environment) so for per machine installs you should install to HKLM\Software\Classes and HKCU\Software\Classes for per user installs. http://msdn.microsoft.com/en-us/library/ms724475(VS.85).aspx -Original Message- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: 30 June 2011 16:35 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Can an x86 msi create a registry key under HKEY_CLASSES_ROOT\Wow6432Node on x64 systems? Dear All, I have an x86 installer which needs to create a registry key under HKEY_CLASSES_ROOT\Wow6432Node on 64-bit machines. I created a component to do the task. The component installs fine but does not create the key on x64 systems. Is there a way to accomplish this with WiX? Your help will be greatly appreciated. Thanks a lot, Miaohsi *** 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=77nav_id=80prev_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). - - 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 SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- 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 *** 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
[WiX-users] How can ignore .NET 3.5 setup prerequisite reboot prompt
Hello All, I created a bootstrapper that installs .NET 3.5 on the target machine if it is not present. The problem is that after its installation, the bootstrapper prompts the user to reboot the machine. Is there a way to avoid this prompt? Thanks a lot for your help. Regards, Miaohsi *** 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=77nav_id=80prev_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). -- 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] HEAT5150 and ATL registrar
I believe this has been seen before IIRC. Rob might still have an old code review for the fix. Otherwise I can look for it when I am back from vacation. Sent from my Windows Phone From: robert_y...@non.agilent.com Sent: Tuesday, July 05, 2011 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] HEAT5150 and ATL registrar Hi all - I'm working on an install with a somewhat large number of older COM objects and .NET classes exposed to COM. For the most part, heat.exe works very well to move away from self-registration; very impressive. We have had some issues, like how to deal with the inability of heat to harvest EXE servers. For those I used RegSpy2 (the one on installsite.org) to create .reg files, which can then be used to create .wxs files. The other issue is how to deal with the infamous HEAT5150 warning. Admittedly we have only a few legacy DLL's which are affected. Regspy2 harvests registry entries for these just fine, and I was curious to know why.. After looking through the regspy2 code, and then the Wix UtilExtension code, I realized that they were doing basically the same things -- registry redirection using RegOverridePredefKey. The difference was that regspy2 was initializing the redirected registry with entries for the ATL Registrar COM object (see CreateAtlRegistrar in the regspy2 source code), which enabled these ancient DLL's to self-register. I might modify my copy of UtilExtension, and perhaps add some hack like an -atl switch to enable a similar feature in heat.exe (if I make any progress on getting the source to build :), but primarily wanted to share this observation. Cheers ! -Rob -- 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] Run a custom exe with administrator privileges with burn
So I added a feature request (3354758). I stick with the second prompt for now, because I want to start the application when the boostrapper closes. Michael Am 05.07.2011 17:20, schrieb Rob Mensching: Burn doesn't have anything built in to do this yet, although we've talked about it a lot. Currently, you'd have to schedule your ExePackage as the last thing in the Chain and mark it @PerMachine=yes. Then you'd have to have your BA or a very cleverly designed InstallCondtiion control when the ExePackage was installed (aka: launched). All of that is undoubtedly a hassle. Adding the feature to Burn just requires figuring out all the right ttimes to launch a configuration thing... and when. On Tue, Jul 5, 2011 at 7:03 AM, Rob Hamflettr...@snsys.com wrote: I don't know much about how Burn works, sorry. The only thing that springs to mind is if Burn itself was elevated. Rob On 05/07/2011 14:54, Michael Stoll wrote: I tried starting the application in the close command of the mba. But then the user is prompted twice for administration privileges (Once by burn and once by the app). So I assume that the UI is running without elevation. Is it possible to tell burn to run the application from within the elevated process? Michael Am 05.07.2011 12:51, schrieb Rob Hamflett: If you run a process that requires admin privileges then it will prompt, unless you run it from a process that is already elevated. If Burn is elevated then you'll be fine, otherwise you'll get the prompt. Rob On 05/07/2011 11:30, Michael Stoll wrote: Hi, I want to start an application after burn has finished setup. This appliation needs administrator privileges. Is it possible start the application without prompting for elevation (using the same elevation mechanism as the setup)? Michael -- 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 -- 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 -- 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] HEAT5150 and ATL registrar
I had a similar problem, and started hacking at a custom heat extension to do a similar job. However, I then realized what I was doing would violate many component rules due to the multiplicity of installation instances I need to support. I am currently prototyping a different approach using Side By Side / Reg Free COM, which eliminates the need for HeatFile tasks, and eliminates the component rule issues. I don't think SxS is able to handle the out of process of components, but if you are having issues with legacy DLL's I'd suggest looking at SxS/Manifests for them. -Original Message- From: Brian Rogers [mailto:rogers.br...@gmail.com] Sent: Tuesday, July 05, 2011 1:40 PM To: robert_y...@non.agilent.com; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] HEAT5150 and ATL registrar I believe this has been seen before IIRC. Rob might still have an old code review for the fix. Otherwise I can look for it when I am back from vacation. Sent from my Windows Phone From: robert_y...@non.agilent.com Sent: Tuesday, July 05, 2011 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] HEAT5150 and ATL registrar Hi all - I'm working on an install with a somewhat large number of older COM objects and .NET classes exposed to COM. For the most part, heat.exe works very well to move away from self-registration; very impressive. We have had some issues, like how to deal with the inability of heat to harvest EXE servers. For those I used RegSpy2 (the one on installsite.org) to create .reg files, which can then be used to create .wxs files. The other issue is how to deal with the infamous HEAT5150 warning. Admittedly we have only a few legacy DLL's which are affected. Regspy2 harvests registry entries for these just fine, and I was curious to know why.. After looking through the regspy2 code, and then the Wix UtilExtension code, I realized that they were doing basically the same things -- registry redirection using RegOverridePredefKey. The difference was that regspy2 was initializing the redirected registry with entries for the ATL Registrar COM object (see CreateAtlRegistrar in the regspy2 source code), which enabled these ancient DLL's to self-register. I might modify my copy of UtilExtension, and perhaps add some hack like an -atl switch to enable a similar feature in heat.exe (if I make any progress on getting the source to build :), but primarily wanted to share this observation. Cheers ! -Rob -- 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] Problem with Win7
It is a 32bit win7, I tried to call the uninstallation from command prompt msiexec /x myinstaller.msi and the registry search works. It also works when choosing uninstall in the right-click menu as well as uninstalling from Control panel. But it only fails when I choose Remove from the Installer UI. 2011/7/5 Skildum, Mathew mathew.skil...@aspect.com Is the problem on a 32 bit or 64 bit system? Make sure the registry search matches the bit level that was set for component containing the initial registry write. -Original Message- From: yheip p [mailto:zyhp...@gmail.com] Sent: Tuesday, July 05, 2011 5:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem with Win7 Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? 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] Problem with Win7
I have checked to log msiexec /i myinstaller.msi /l* log for both XP and Win7 32bit and right after ExcuteAction MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property INSTALLLOCATION MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property FILEEXISTS MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property TARGETDIR MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property USERNAME MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property ROOTDRIVE The above lines appear in the Win7 log ( which do not appear in XP) where INSTALLLOCATION is the property that used to do fileSearch and return to FILEEXISTS property. anyone know what's going on here...??? 2011/7/6 yheip p zyhp...@gmail.com It is a 32bit win7, I tried to call the uninstallation from command prompt msiexec /x myinstaller.msi and the registry search works. It also works when choosing uninstall in the right-click menu as well as uninstalling from Control panel. But it only fails when I choose Remove from the Installer UI. 2011/7/5 Skildum, Mathew mathew.skil...@aspect.com Is the problem on a 32 bit or 64 bit system? Make sure the registry search matches the bit level that was set for component containing the initial registry write. -Original Message- From: yheip p [mailto:zyhp...@gmail.com] Sent: Tuesday, July 05, 2011 5:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem with Win7 Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? 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] Problem with Win7
Adding Secure=yes to that two property solve to problem. thanks:) 2011/7/6 yheip p zyhp...@gmail.com I have checked to log msiexec /i myinstaller.msi /l* log for both XP and Win7 32bit and right after ExcuteAction MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property INSTALLLOCATION MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property FILEEXISTS MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property TARGETDIR MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property USERNAME MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property ROOTDRIVE The above lines appear in the Win7 log ( which do not appear in XP) where INSTALLLOCATION is the property that used to do fileSearch and return to FILEEXISTS property. anyone know what's going on here...??? 2011/7/6 yheip p zyhp...@gmail.com It is a 32bit win7, I tried to call the uninstallation from command prompt msiexec /x myinstaller.msi and the registry search works. It also works when choosing uninstall in the right-click menu as well as uninstalling from Control panel. But it only fails when I choose Remove from the Installer UI. 2011/7/5 Skildum, Mathew mathew.skil...@aspect.com Is the problem on a 32 bit or 64 bit system? Make sure the registry search matches the bit level that was set for component containing the initial registry write. -Original Message- From: yheip p [mailto:zyhp...@gmail.com] Sent: Tuesday, July 05, 2011 5:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem with Win7 Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? 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
