Re: [WiX-users] read a regkey with special permission
Pavan, Thank you for the suggestion. But my problem is a little bit complicated. The value I need for the custom action can be only fetched through a deferred custom action. I will get the value from deferred custom action. Now, I need find a way either to pass the value back to WIX; or pass it along to another custom action. Thanks Nan -Original Message- From: Pavan Konduru [mailto:pavan.kond...@accelrys.com] Sent: Thursday, March 06, 2014 10:25 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] read a regkey with special permission Hi Nan, Before running your custom action , run another custom action that will pass that property to your custom action(set that as immediate). Something like this: Where the "value" is the one that you want from the session, here I used INSTALLLOCATION, so put there your own property. Make sure to run the "SetProperty1" action before your c# custom action. In the Installexecute sequence: --Pavan -Original Message- From: Nan Zang [mailto:naz...@microsoft.com] Sent: Wednesday, March 05, 2014 9:58 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] read a regkey with special permission Hi, I didn't find a possible way to get the regkey value. So, I decided to use an elevated custom action to read the regkey. However, I met with another issue. >From my understanding since my customaction needs to be elevated, so it must >be executed as deferred. However, deferred custom action cannot use session >directly. How can I pass back this value to wix (or another custom action)? I >must pass it back to wix for some sql operation. My custom action is written in C# using Microsoft.Deployment.WindowsInstaller.dll Any help is appreciated. Thanks Nan -Original Message- From: Nan Zang [mailto:naz...@microsoft.com] Sent: Wednesday, March 5, 2014 1:33 PM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Subject: [WiX-users] read a regkey with special permission Hi, I am trying to read a regkey value in the msi. But, this regkey has special ACL set on it, which only allows Local System/Administrator to read it. I am using RegistrySearch Element to read the regkey. The operation will work if the msi is launched through elevated cmd window. But, if launched normally, the operation will fail with error. "Info 1402. Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Test\. System error 5. Verify that you have sufficient access to that key, or contact your support personnel." Could you recommend any solution to get this regkey value? At this point, we prefer to avoid custom action if possible. Thanks Nan -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization an
Re: [WiX-users] read a regkey with special permission
Hi, I didn't find a possible way to get the regkey value. So, I decided to use an elevated custom action to read the regkey. However, I met with another issue. >From my understanding since my customaction needs to be elevated, so it must >be executed as deferred. However, deferred custom action cannot use session >directly. How can I pass back this value to wix (or another custom action)? I >must pass it back to wix for some sql operation. My custom action is written in C# using Microsoft.Deployment.WindowsInstaller.dll Any help is appreciated. Thanks Nan -Original Message----- From: Nan Zang [mailto:naz...@microsoft.com] Sent: Wednesday, March 5, 2014 1:33 PM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Subject: [WiX-users] read a regkey with special permission Hi, I am trying to read a regkey value in the msi. But, this regkey has special ACL set on it, which only allows Local System/Administrator to read it. I am using RegistrySearch Element to read the regkey. The operation will work if the msi is launched through elevated cmd window. But, if launched normally, the operation will fail with error. "Info 1402. Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Test\. System error 5. Verify that you have sufficient access to that key, or contact your support personnel." Could you recommend any solution to get this regkey value? At this point, we prefer to avoid custom action if possible. Thanks Nan -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] read a regkey with special permission
Hi, I am trying to read a regkey value in the msi. But, this regkey has special ACL set on it, which only allows Local System/Administrator to read it. I am using RegistrySearch Element to read the regkey. The operation will work if the msi is launched through elevated cmd window. But, if launched normally, the operation will fail with error. "Info 1402. Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Test\. System error 5. Verify that you have sufficient access to that key, or contact your support personnel." Could you recommend any solution to get this regkey value? At this point, we prefer to avoid custom action if possible. Thanks Nan -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA
I would like to try the option of change the prereq-BA to a different native BA which do the precheck. I don't have much knowledge about how BA. Do I need to modify wix source code to achieve this? Could you give me some more details on how to do it? 1. Which interface my prereq BA needs to implement. 2. How to configure the bundle.wxs to use my customized prereq BA. Is there any example I can take a look at? Thanks for the great help, Nan -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Tuesday, August 20, 2013 12:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA The error message is from Windows (ERROR_OLD_WIN_VERSION). The only other possibility would be to change the prereq-BA to a different native BA that would determine the applicability of your installation attempt and present the appropriate error message before the prerequisites are installed. Or alter the current stdba (which is the current mbapreq using a different codepath) to add that feature. I would suggest if you go that route that you also update WixBalExtension and add a bal:PrereqCondition mirroring the current bal:Condition. > From: naz...@microsoft.com > To: wix-users@lists.sourceforge.net > Date: Tue, 20 Aug 2013 06:33:18 + > Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if > using MBA > > I tried it, however it doesn't work fully for my case. Besides the OS > version, I also need to check the architecture of the OS. I want to block 64 > bit package to be installed on a 32 bit OS. If I set the condition, the > installation will be blocked, however, I didn't see I can customize the > error, I always get "The specified program requires a newer version of > Windows." > > For the bundle\@condition, is that possible I can customize the error > message? Or, any other way to do it? > > Thanks, > Nan > > -Original Message- > From: Blair Murri [mailto:os...@live.com] > Sent: Monday, August 19, 2013 10:46 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if > using MBA > > Bundle\@Condition attribute. > > The limited conditions it can evaluate include OS. > > > From: naz...@microsoft.com > > To: wix-users@lists.sourceforge.net > > Date: Tue, 20 Aug 2013 05:12:55 + > > Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if > > using MBA > > > > Hi, > > > > I met with the same problem with the MBA precheck. Definitely, I can have > > the code in my MBA to check the pre conditions, however, I think the > > following scenario is totally broken. Eg. We want to block installation of > > our product on the OS vista or before. > > > > A user uses a vista machine without .net 4. User downloads the package and > > clicks install. To load MBA, the setup will guide user to install .Net 4 > > and after installing .net 4, the setup will tell the user, sorry, wrong OS. > > I think this is a horrible user experience, and I really want to do better > > here. Is there any possible way to handle the above situation? Any precheck > > I can do except having it in my MBA. > > > > Many Thanks, > > Nan > > > > > > > > -Original Message- > > From: Phill Hogland [mailto:phogl...@rimage.com] > > Sent: Friday, August 2, 2013 6:13 AM > > To: wix-users@lists.sourceforge.net > > Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if > > using MBA > > > > The WixBA at src\Setup\WixBA is the C# managed BA that is used by the > > installer that installs the toolset. The Bundle does not have a > > bal:Condition in it and as far as I can tell there is nothing directly > > related to Bal:Condition in WixBA. However I think what folks have > > suggested is that one could look at how the processing of bal:Condition is > > implemented in the C++ WixStdBA at src\ext\BalExtensions\wixstdba and using > > that functionality as a pattern implement something like that in the > > managed BA that you are writing. I think one would want to look at > > EvaluateConditions in WixStandardBootstrapperApplication.cpp for a starter. > > > > > > > > -- > > View this message in context: > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Bu > > rn > > -Bundle-condition-does-not-work-if-using-MBA-tp7581757p758.html > > Sent from the wix-users mailing list archive at Nabble.com. > > > > > > -- > > Get your SQL database under version control now! > > Version control is standard for application code, but databases havent > > caught up. So what steps can you take to put your SQL databases under > > version control? Why should you start doing it? Read more to find out. > > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg > > .c lktrk ___
Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA
I tried it, however it doesn't work fully for my case. Besides the OS version, I also need to check the architecture of the OS. I want to block 64 bit package to be installed on a 32 bit OS. If I set the condition, the installation will be blocked, however, I didn't see I can customize the error, I always get "The specified program requires a newer version of Windows." For the bundle\@condition, is that possible I can customize the error message? Or, any other way to do it? Thanks, Nan -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Monday, August 19, 2013 10:46 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA Bundle\@Condition attribute. The limited conditions it can evaluate include OS. > From: naz...@microsoft.com > To: wix-users@lists.sourceforge.net > Date: Tue, 20 Aug 2013 05:12:55 + > Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if > using MBA > > Hi, > > I met with the same problem with the MBA precheck. Definitely, I can have the > code in my MBA to check the pre conditions, however, I think the following > scenario is totally broken. Eg. We want to block installation of our product > on the OS vista or before. > > A user uses a vista machine without .net 4. User downloads the package and > clicks install. To load MBA, the setup will guide user to install .Net 4 and > after installing .net 4, the setup will tell the user, sorry, wrong OS. I > think this is a horrible user experience, and I really want to do better > here. Is there any possible way to handle the above situation? Any precheck I > can do except having it in my MBA. > > Many Thanks, > Nan > > > > -Original Message- > From: Phill Hogland [mailto:phogl...@rimage.com] > Sent: Friday, August 2, 2013 6:13 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if > using MBA > > The WixBA at src\Setup\WixBA is the C# managed BA that is used by the > installer that installs the toolset. The Bundle does not have a > bal:Condition in it and as far as I can tell there is nothing directly > related to Bal:Condition in WixBA. However I think what folks have suggested > is that one could look at how the processing of bal:Condition is implemented > in the C++ WixStdBA at src\ext\BalExtensions\wixstdba and using that > functionality as a pattern implement something like that in the managed BA > that you are writing. I think one would want to look at EvaluateConditions > in WixStandardBootstrapperApplication.cpp for a starter. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn > -Bundle-condition-does-not-work-if-using-MBA-tp7581757p758.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > Get your SQL database under version control now! > Version control is standard for application code, but databases havent caught > up. So what steps can you take to put your SQL databases under version > control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.c > lktrk ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > Introducing Performance Central, a new site from SourceForge > and AppDynamics. Performance Central is your source for news, > insights, analysis and resources for efficient Application Performance > Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.c > lktrk ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! ht
Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA
Hi, I met with the same problem with the MBA precheck. Definitely, I can have the code in my MBA to check the pre conditions, however, I think the following scenario is totally broken. Eg. We want to block installation of our product on the OS vista or before. A user uses a vista machine without .net 4. User downloads the package and clicks install. To load MBA, the setup will guide user to install .Net 4 and after installing .net 4, the setup will tell the user, sorry, wrong OS. I think this is a horrible user experience, and I really want to do better here. Is there any possible way to handle the above situation? Any precheck I can do except having it in my MBA. Many Thanks, Nan -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Friday, August 2, 2013 6:13 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA The WixBA at src\Setup\WixBA is the C# managed BA that is used by the installer that installs the toolset. The Bundle does not have a bal:Condition in it and as far as I can tell there is nothing directly related to Bal:Condition in WixBA. However I think what folks have suggested is that one could look at how the processing of bal:Condition is implemented in the C++ WixStdBA at src\ext\BalExtensions\wixstdba and using that functionality as a pattern implement something like that in the managed BA that you are writing. I think one would want to look at EvaluateConditions in WixStandardBootstrapperApplication.cpp for a starter. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Bundle-condition-does-not-work-if-using-MBA-tp7581757p758.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] BA has problem adding a feature
Thank you Rob, that works.
In case anyone has the same issue.
Here is my code to get it work
private void ExecuteOnPlanMsiFeature(object sender,
PlanMsiFeatureEventArgs args)
{
if (this.action == LaunchAction.Install)
{
If (user selected the feature, and we want to install it)
// ba request state will be set to local
{
args.State = FeatureState.Local;
}
else
{
args.State = FeatureState.Absent;
}
}
}
Thanks,
Nan
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, April 01, 2013 2:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] BA has problem adding a feature
Don't try to control feature states using the properties. Instead, turn on
EnableFeatureSelection and handle the PlanFeature callback from the engine.
The ADDLOCAL property and friends won't give you the control necessary to
succeed.
On Mon, Apr 1, 2013 at 2:10 PM, Nan Zang wrote:
> Hi,
>
> I am building a bootstrapper based on the managed BA (I am using a
> customized WPF UI), but met with the following issue.
>
> My BA.exe refers to an MsiPackage, which contains two features
> (WebService and AdminTool).
>
> If everything is not installed, if user selects AdminTool, the BA will
> call msi using ADDLOCAL=AdminTool and AdminTool is installed as expected.
> But, there is a problem, if AdminTool has been installed, and user
> selects to Add "WebService" Feature, the BA will call msi using
> ADDLCAL=WebSerivce (I also tried ADDLOCAL=ALL ) WebServiceFeature
> didn't get installed at all, and also there is no error reported.
>
> Can anyone provide any hint on troubleshooting this one?
>
> Here is the log:
>
> [18BC:1C48][2013-04-01T13:41:39]i001: Burn v3.7.1224.0, Windows v6.1
> (Build 7601: Service Pack 1), path:
> E:\rmsonline\bins\debug\amd64\Setup\AadrmConnectorSetup\AadrmConnector
> Setup.exe,
> cmdline: ''
> [18BC:1C48][2013-04-01T13:41:39]i000: Setting string variable
> 'WixBundleLog' to value 'C:\Users\nazang\AppData\Local\Temp\Azure AD
> Rights Management Connector_20130401134139.log'
> [18BC:1C48][2013-04-01T13:41:39]i000: Setting string variable
> 'WixBundleOriginalSource' to value
> 'E:\rmsonline\bins\debug\amd64\Setup\AadrmConnectorSetup\AadrmConnectorSetup.exe'
> [18BC:1C48][2013-04-01T13:41:49]i000: Loading managed bootstrapper
> application.
> [18BC:1C48][2013-04-01T13:42:21]i000: Creating BA thread to run
> asynchronously.
> [18BC:1DD8][2013-04-01T13:42:38]i000: Full
> [18BC:1DD8][2013-04-01T13:42:38]i000: Launching the AADRM Connector
> Setup UI.
> [18BC:1C48][2013-04-01T13:42:55]i100: Detect begin, 2 packages
> [18BC:1C48][2013-04-01T13:42:56]i000: Setting string variable
> 'Netfx4x64FullVersion' to value '4.5.50709'
> [18BC:1C48][2013-04-01T13:42:56]i000: Setting string variable
> 'Netfx4FullVersion' to value '4.5.50709'
> [18BC:1C48][2013-04-01T13:42:56]i052: Condition 'Netfx4FullVersion AND
> (NOT VersionNT64 OR Netfx4x64FullVersion)' evaluates to true.
> [18BC:1C48][2013-04-01T13:43:04]i101: Detected package: NetFx40Web, state:
> Present, cached: None
> [18BC:1C48][2013-04-01T13:43:04]i101: Detected package:
> AADRMConnectorPackage, state: Present, cached: None
> [18BC:1C48][2013-04-01T13:43:04]i104: Detected package:
> AADRMConnectorPackage, feature: AADRMConnectorWebService, state:
> Absent
> [18BC:1C48][2013-04-01T13:43:04]i104: Detected package:
> AADRMConnectorPackage, feature: AADRMConnectorAdminTool, state: Local
> [18BC:1C48][2013-04-01T13:43:04]i199: Detect complete, result: 0x0
> [18BC:1C48][2013-04-01T13:44:24]i200: Plan begin, 2 packages, action:
> Install
> [18BC:1C48][2013-04-01T13:44:25]w321: Skipping dependency registration
> on package with no dependency providers: NetFx40Web
> [18BC:1C48][2013-04-01T13:44:25]i204: Plan 2 msi features for package:
> AADRMConnectorPackage
> [18BC:1C48][2013-04-01T13:44:25]i203: Planned feature:
> AADRMConnectorWebService, state: Absent, default requested: Unknown,
> ba
> requested: Unknown, execute action: None, rollback action: None
> [18BC:1C48][2013-04-01T13:44:25]i203: Planned feature:
> AADRMConnectorAdminTool, state: Local, default requested: Unknown, ba
> requested: Unknown, execute action: None, rollback action: None
> [18BC:1C48][2013-04-01T13:44:25]i201: Planned package: NetFx40Web, state:
> Present, default requested: Present, ba requested: Present, execute:
> None,
> rollback: None
[WiX-users] BA has problem adding a feature
Hi,
I am building a bootstrapper based on the managed BA (I am using a customized
WPF UI), but met with the following issue.
My BA.exe refers to an MsiPackage, which contains two features (WebService and
AdminTool).
If everything is not installed, if user selects AdminTool, the BA will call msi
using ADDLOCAL=AdminTool and AdminTool is installed as expected. But, there is
a problem, if AdminTool has been installed, and user selects to Add
"WebService" Feature, the BA will call msi using ADDLCAL=WebSerivce (I also
tried ADDLOCAL=ALL ) WebServiceFeature didn't get installed at all, and also
there is no error reported.
Can anyone provide any hint on troubleshooting this one?
Here is the log:
[18BC:1C48][2013-04-01T13:41:39]i001: Burn v3.7.1224.0, Windows v6.1 (Build
7601: Service Pack 1), path:
E:\rmsonline\bins\debug\amd64\Setup\AadrmConnectorSetup\AadrmConnectorSetup.exe,
cmdline: ''
[18BC:1C48][2013-04-01T13:41:39]i000: Setting string variable 'WixBundleLog' to
value 'C:\Users\nazang\AppData\Local\Temp\Azure AD Rights Management
Connector_20130401134139.log'
[18BC:1C48][2013-04-01T13:41:39]i000: Setting string variable
'WixBundleOriginalSource' to value
'E:\rmsonline\bins\debug\amd64\Setup\AadrmConnectorSetup\AadrmConnectorSetup.exe'
[18BC:1C48][2013-04-01T13:41:49]i000: Loading managed bootstrapper application.
[18BC:1C48][2013-04-01T13:42:21]i000: Creating BA thread to run asynchronously.
[18BC:1DD8][2013-04-01T13:42:38]i000: Full
[18BC:1DD8][2013-04-01T13:42:38]i000: Launching the AADRM Connector Setup UI.
[18BC:1C48][2013-04-01T13:42:55]i100: Detect begin, 2 packages
[18BC:1C48][2013-04-01T13:42:56]i000: Setting string variable
'Netfx4x64FullVersion' to value '4.5.50709'
[18BC:1C48][2013-04-01T13:42:56]i000: Setting string variable
'Netfx4FullVersion' to value '4.5.50709'
[18BC:1C48][2013-04-01T13:42:56]i052: Condition 'Netfx4FullVersion AND (NOT
VersionNT64 OR Netfx4x64FullVersion)' evaluates to true.
[18BC:1C48][2013-04-01T13:43:04]i101: Detected package: NetFx40Web, state:
Present, cached: None
[18BC:1C48][2013-04-01T13:43:04]i101: Detected package: AADRMConnectorPackage,
state: Present, cached: None
[18BC:1C48][2013-04-01T13:43:04]i104: Detected package: AADRMConnectorPackage,
feature: AADRMConnectorWebService, state: Absent
[18BC:1C48][2013-04-01T13:43:04]i104: Detected package: AADRMConnectorPackage,
feature: AADRMConnectorAdminTool, state: Local
[18BC:1C48][2013-04-01T13:43:04]i199: Detect complete, result: 0x0
[18BC:1C48][2013-04-01T13:44:24]i200: Plan begin, 2 packages, action: Install
[18BC:1C48][2013-04-01T13:44:25]w321: Skipping dependency registration on
package with no dependency providers: NetFx40Web
[18BC:1C48][2013-04-01T13:44:25]i204: Plan 2 msi features for package:
AADRMConnectorPackage
[18BC:1C48][2013-04-01T13:44:25]i203: Planned feature:
AADRMConnectorWebService, state: Absent, default requested: Unknown, ba
requested: Unknown, execute action: None, rollback action: None
[18BC:1C48][2013-04-01T13:44:25]i203: Planned feature: AADRMConnectorAdminTool,
state: Local, default requested: Unknown, ba requested: Unknown, execute
action: None, rollback action: None
[18BC:1C48][2013-04-01T13:44:25]i201: Planned package: NetFx40Web, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[18BC:1C48][2013-04-01T13:44:25]i201: Planned package: AADRMConnectorPackage,
state: Present, default requested: Present, ba requested: Present, execute:
None, rollback: None, cache: No, uncache: No, dependency: Register
[18BC:1C48][2013-04-01T13:44:25]i000: Setting string variable 'ADDLOCAL' to
value 'AADRMConnectorWebService'
[18BC:1C48][2013-04-01T13:44:25]i299: Plan complete, result: 0x0
[18BC:1C48][2013-04-01T13:44:25]i300: Apply begin
[0DB8:1D50][2013-04-01T13:44:34]i360: Creating a system restore point.
[0DB8:1D50][2013-04-01T13:44:34]i362: System restore disabled, system restore
point not created.
[0DB8:1D50][2013-04-01T13:44:34]i323: Registering package dependency provider:
{1EE6FAA1-542C-4450-BFC9-223FC2E50C69}, version: 1.0.962.0, package:
AADRMConnectorPackage
[0DB8:1D50][2013-04-01T13:44:34]i325: Registering dependency:
{2f499eb8-d97c-46c0-8528-4146414b608d} on package provider:
{1EE6FAA1-542C-4450-BFC9-223FC2E50C69}, package: AADRMConnectorPackage
[18BC:1C48][2013-04-01T13:44:34]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[18BC:1C48][2013-04-01T13:44:38]i500: Shutting down, exit code: 0x0
[18BC:1C48][2013-04-01T13:44:38]i410: Variable: ADDLOCAL =
AADRMConnectorWebService
[18BC:1C48][2013-04-01T13:44:38]i410: Variable: Netfx4FullVersion = 4.5.50709
[18BC:1C48][2013-04-01T13:44:38]i410: Variable: Netfx4x64FullVersion = 4.5.50709
[18BC:1C48][2013-04-01T13:44:38]i410: Variable: VersionNT64 = 6.1.0.0
[18BC:1C48][2013-04-01T13:44:38]i410: Variable: WixBundleAction = 4
[18BC:1C48][2013-04-01T13:44:38]i410: Variable: WixBundleElevated = 1
[1
Re: [WiX-users] problem on setting passing selected feature from burn to msi
I think I found the issue.
In bundle msipackage definition I need to define the following. Property to
make it work
Sent from my Windows Phone
From: Nan Zang<mailto:naz...@microsoft.com>
Sent: 2/13/2013 7:15 PM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)<mailto:wix-users@lists.sourceforge.net>
Subject: [WiX-users] problem on setting passing selected feature from burn to
msi
My MSI has two dummy feature as listed below.
And I am using customize UI to collect user feature selection, then pass it
into through Engine by using following code
this.Bootstrapper.Engine.StringVariables["ADDLOCAL"] =
featureList;
this.Bootstrapper.Engine.Plan(LaunchAction.Install);
This is my log, the "addlocal" variable doesn't seem work. Anything I am
missing here? Thank you for help.
[3B40:1788][2013-02-13T19:02:26]: Detected package: NetFX40, state: Present,
cached: None
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, state: Absent, cached: None
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, feature: FULLPRODUCTION, state: Absent
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, feature: ADMINCONFIGURATIONTOOL, state: Absent
[3B40:1788][2013-02-13T19:02:26]: Detect complete, result: 0x0
[3B40:25E8][2013-02-13T19:02:38]: Add property name ADDLOCAL with
valueADMINCONFIGURATIONTOOL
[3B40:25E8][2013-02-13T19:02:38]: Setting string variable 'ADDLOCAL' to value
'ADMINCONFIGURATIONTOOL'
[3B40:1788][2013-02-13T19:02:38]: Plan 2 packages, action: Install
[3B40:1788][2013-02-13T19:02:38]: Skipping dependency registration on package
with no dependency providers: NetFX40
[3B40:1788][2013-02-13T19:02:38]: Plan 2 msi features for package:
RMSSetupInstallationPackageId
[3B40:1788][2013-02-13T19:02:38]: Planned feature: FULLPRODUCTION, state:
Absent, default requested: Unknown, ba requested: Unknown, execute action:
None, rollback action: None
[3B40:1788][2013-02-13T19:02:38]: Planned feature: ADMINCONFIGURATIONTOOL,
state: Absent, default requested: Unknown, ba requested: Unknown, execute
action: None, rollback action: None
[3B40:1788][2013-02-13T19:02:38]: Setting string variable
'WixBundleRollbackLog_RMSSetupInstallationPackageId' to value
'e:\wix\Dev\wix37\setup_0_RMSSetupInstallationPackageId_rollback.log'
[3B40:1788][2013-02-13T19:02:38]: Setting string variable
'WixBundleLog_RMSSetupInstallationPackageId' to value
'e:\wix\Dev\wix37\setup_0_RMSSetupInstallationPackageId.log'
[3B40:1788][2013-02-13T19:02:38]: Planned package: NetFX40, state: Present,
default requested: Present, ba requested: Present, execute: None, rollback:
None, cache: No, uncache: No, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned package:
RMSSetupInstallationPackageId, state: Absent, default requested: Present, ba
requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache:
Yes, dependency: Register
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{4d72440b-3501-4b0c-9ee3-2fae6b7e4716}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{63379848-f823-4d73-9364-83bebc1528b2}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{886235b4-2f08-4c05-916f-d75266a07525}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{f08b430f-3d9c-4d8e-a160-708f9be5827e}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Plan complete, result: 0x0
[3B40:1788][2013-02-13T19:02:38]: Apply begin
[3554:1888][2013-02-13T19:02:38]: Creating a system restore point.
[3554:1888][2013-02-13T19:02:38]: System restore disabled, system restore point
not created.
[3554:1888][2013-02-13T19:02:38]: Caching bundle from:
'C:\Users\nazang\AppData\Local\Temp\{34d831eb-4e21-4fed-9502-58ee48298d6f}\.be\BootstrapperSetup.exe'
to: 'C:\ProgramData\Package
Cache\{34d831eb-4e21-4fed-9502-58ee48298d6f}\BootstrapperSetup.exe'
[3554:1888][2013-02-13T19:02:38]: Registering bundle dependency provider:
{34d831eb-4e21-4fed-9502-58ee48298d6f}, version: 1.0.0.0
[3554:21F0][2013-02-13T19:02:38]: Verified acquired payload:
RMSSetupInstallationPackageId at path: C:\ProgramData\Package
Cache\.unverified\RMSSetupInstallationPackageId, moving to:
C:\ProgramData\Package
Cache\{5DE269D0-9B
[WiX-users] problem on setting passing selected feature from burn to msi
My MSI has two dummy feature as listed below.
And I am using customize UI to collect user feature selection, then pass it
into through Engine by using following code
this.Bootstrapper.Engine.StringVariables["ADDLOCAL"] =
featureList;
this.Bootstrapper.Engine.Plan(LaunchAction.Install);
This is my log, the "addlocal" variable doesn't seem work. Anything I am
missing here? Thank you for help.
[3B40:1788][2013-02-13T19:02:26]: Detected package: NetFX40, state: Present,
cached: None
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, state: Absent, cached: None
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, feature: FULLPRODUCTION, state: Absent
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, feature: ADMINCONFIGURATIONTOOL, state: Absent
[3B40:1788][2013-02-13T19:02:26]: Detect complete, result: 0x0
[3B40:25E8][2013-02-13T19:02:38]: Add property name ADDLOCAL with
valueADMINCONFIGURATIONTOOL
[3B40:25E8][2013-02-13T19:02:38]: Setting string variable 'ADDLOCAL' to value
'ADMINCONFIGURATIONTOOL'
[3B40:1788][2013-02-13T19:02:38]: Plan 2 packages, action: Install
[3B40:1788][2013-02-13T19:02:38]: Skipping dependency registration on package
with no dependency providers: NetFX40
[3B40:1788][2013-02-13T19:02:38]: Plan 2 msi features for package:
RMSSetupInstallationPackageId
[3B40:1788][2013-02-13T19:02:38]: Planned feature: FULLPRODUCTION, state:
Absent, default requested: Unknown, ba requested: Unknown, execute action:
None, rollback action: None
[3B40:1788][2013-02-13T19:02:38]: Planned feature: ADMINCONFIGURATIONTOOL,
state: Absent, default requested: Unknown, ba requested: Unknown, execute
action: None, rollback action: None
[3B40:1788][2013-02-13T19:02:38]: Setting string variable
'WixBundleRollbackLog_RMSSetupInstallationPackageId' to value
'e:\wix\Dev\wix37\setup_0_RMSSetupInstallationPackageId_rollback.log'
[3B40:1788][2013-02-13T19:02:38]: Setting string variable
'WixBundleLog_RMSSetupInstallationPackageId' to value
'e:\wix\Dev\wix37\setup_0_RMSSetupInstallationPackageId.log'
[3B40:1788][2013-02-13T19:02:38]: Planned package: NetFX40, state: Present,
default requested: Present, ba requested: Present, execute: None, rollback:
None, cache: No, uncache: No, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned package:
RMSSetupInstallationPackageId, state: Absent, default requested: Present, ba
requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache:
Yes, dependency: Register
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{4d72440b-3501-4b0c-9ee3-2fae6b7e4716}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{63379848-f823-4d73-9364-83bebc1528b2}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{886235b4-2f08-4c05-916f-d75266a07525}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{f08b430f-3d9c-4d8e-a160-708f9be5827e}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Plan complete, result: 0x0
[3B40:1788][2013-02-13T19:02:38]: Apply begin
[3554:1888][2013-02-13T19:02:38]: Creating a system restore point.
[3554:1888][2013-02-13T19:02:38]: System restore disabled, system restore point
not created.
[3554:1888][2013-02-13T19:02:38]: Caching bundle from:
'C:\Users\nazang\AppData\Local\Temp\{34d831eb-4e21-4fed-9502-58ee48298d6f}\.be\BootstrapperSetup.exe'
to: 'C:\ProgramData\Package
Cache\{34d831eb-4e21-4fed-9502-58ee48298d6f}\BootstrapperSetup.exe'
[3554:1888][2013-02-13T19:02:38]: Registering bundle dependency provider:
{34d831eb-4e21-4fed-9502-58ee48298d6f}, version: 1.0.0.0
[3554:21F0][2013-02-13T19:02:38]: Verified acquired payload:
RMSSetupInstallationPackageId at path: C:\ProgramData\Package
Cache\.unverified\RMSSetupInstallationPackageId, moving to:
C:\ProgramData\Package
Cache\{5DE269D0-9B2D-4AAE-A330-56410E9AFA11}v1.0.0.0\RMSSetupInstaller.msi.
[3554:21F0][2013-02-13T19:02:38]: Verified acquired payload:
cab889C4727BDD85A0DB399FF3308DF872E at path: C:\ProgramData\Package
Cache\.unverified\cab889C4727BDD85A0DB399FF3308DF872E, moving to:
C:\ProgramData\Package
Cache\{5DE269D0-9B2D-4AAE-A330-56410E9AFA11}v1.0.0.0\cab1.cab.
[3554:1888][2013-02-13T19:02:39]: Applying execute package:
RMSSetupInstallationPackageId, action: Install, path: C:\ProgramData\Package
Cache\{5DE269D0-9B2D-4AAE-A330-56410E9AFA11}v1.0.0.0\RMSSetupInstaller.msi,
arguments: ' MSIFASTINSTALL="7"'
[3554:1888
Re: [WiX-users] questions on bootstrapper
After some investigation, it seemsdefine Id="WixMbaPrereqPackageId" will
accomplish what I need, however, I cannot get it work.
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";>
This is the log, this is modfied from the sample code. There is no prerequisite
step gets invoked, Anything wrong here?
[1F40:1700][2013-02-12T23:07:48]: Burn v3.6.3303.0, Windows v6.1 (Build 7601:
Service Pack 1), path:
C:\Users\nazang\Desktop\RMSSetupBA\BootstrapperSetup\bin\Debug\BootstrapperSetup.exe,
cmdline: '/install /log setup.log /runas:administrator -burn.unelevated
BurnPipe.{F434AAE5-B80D-43FF-8859-670E1B3D483E}
{E175F3B6-186C-445D-A861-3BDC024177A4} 12900'
[1F40:1700][2013-02-12T23:07:48]: Setting string variable 'WixBundleLog' to
value 'e:\wix\Dev\wix37\setup.log'
[1F40:1700][2013-02-12T23:07:48]: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\nazang\Desktop\RMSSetupBA\BootstrapperSetup\bin\Debug\BootstrapperSetup.exe'
[1F40:1700][2013-02-12T23:07:48]: Setting string variable 'WixBundleName' to
value 'My Test Application'
[1F40:1700][2013-02-12T23:07:48]: Loading managed bootstrapper application.
[1F40:1700][2013-02-12T23:07:49]: Creating BA thread to run asynchronously.
[1F40:3B48][2013-02-12T23:07:49]: Launching custom TestBA UX
[1F40:1700][2013-02-12T23:07:49]: Detect 2 packages
[1F40:1700][2013-02-12T23:07:49]: Detected related bundle:
{4d72440b-3501-4b0c-9ee3-2fae6b7e4716}, type: Upgrade, scope: PerMachine,
version: 1.0.0.0, operation: None
[1F40:1700][2013-02-12T23:07:49]: Detected related bundle:
{63379848-f823-4d73-9364-83bebc1528b2}, type: Upgrade, scope: PerMachine,
version: 1.0.0.0, operation: None
[1F40:1700][2013-02-12T23:07:49]: Detected related bundle:
{886235b4-2f08-4c05-916f-d75266a07525}, type: Upgrade, scope: PerMachine,
version: 1.0.0.0, operation: None
[1F40:1700][2013-02-12T23:07:49]: Detected package: OrgIdSignInAssistant,
state: Absent, cached: None
[1F40:1700][2013-02-12T23:07:49]: Detected package: DummyInstallernPackageId,
state: Present, cached: Complete
[1F40:1700][2013-02-12T23:07:49]: Detect complete, result: 0x0
From: Nan Zang
Sent: Tuesday, February 12, 2013 8:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] questions on bootstrapper
Jocob,
Thank you for your detailed answer. I have another question related to 1.
Besides .Net 3.5, I need another dependency (eg. CredUI.msi) for my BA UX. I
need to use this dependency in one of my BA UX. Is there possible I get it
installed automatically before my BAUX gets launched. I tried the chained
package approach, and found the installation of the credUI.msi will be invoked
when the MSI is launched. That doesn't meet my requirement. Is that possible to
invoke the installation action early?
Thanks,
Nan
From: Hoover, Jacob
Sent: Tuesday, February 12, 2013 7:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] questions on bootstrapper
1.
. Because this is a feature on 2008R2, this method fails and says need to
enable the feature to install the framework.
http://blogs.msdn.com/b/sqlblog/archive/2010/01/08/how-to-install-net-framework-3-5-sp1-on-windows-server-2008-r2-environments.aspx
And a previous discussion:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-NET-3-5-on-Windows-2008-R2-td7580032.html
And I believe this is the feature Rob was speaking of:
http://sourceforge.net/p/wix/feature-requests/643/
In short, burn currently doesn't gracefully support this. One could modify the
WixStdBA to detect the OS level, and if the OS is 2008R2 then enable the
feature instead of invoking the default installer. From a quick dive, it looks
to me that a MBA will fall back to WixStdBA using a mbapreq theme, but I can't
seem to find the specific fragments they are feeding in for installing 3.5 (I
can find 4.0+). From a high level, I don't know how Wix identifies which
prerequisite maps to the .Net framework. If I were a betting man, they are
relying on the .Net framework install requesting a reboot. And that it's the
first PackageGroup/PackageGroupRef in the chain.
Some people have fallen back to using a stub exe with command line parameters
to enable the feature. You then can use conditions to only invoke the stub on
your target OS's (I would include this in the PackageGroup you created for the
3.5 framework).
2.
BA's should not modify system state for anything other than what the engine
already does. If you need to modify system s
Re: [WiX-users] questions on bootstrapper
Jocob, Thank you for your detailed answer. I have another question related to 1. Besides .Net 3.5, I need another dependency (eg. CredUI.msi) for my BA UX. I need to use this dependency in one of my BA UX. Is there possible I get it installed automatically before my BAUX gets launched. I tried the chained package approach, and found the installation of the credUI.msi will be invoked when the MSI is launched. That doesn't meet my requirement. Is that possible to invoke the installation action early? Thanks, Nan From: Hoover, Jacob Sent: Tuesday, February 12, 2013 7:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] questions on bootstrapper 1. . Because this is a feature on 2008R2, this method fails and says need to enable the feature to install the framework. http://blogs.msdn.com/b/sqlblog/archive/2010/01/08/how-to-install-net-framework-3-5-sp1-on-windows-server-2008-r2-environments.aspx And a previous discussion: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-NET-3-5-on-Windows-2008-R2-td7580032.html And I believe this is the feature Rob was speaking of: http://sourceforge.net/p/wix/feature-requests/643/ In short, burn currently doesn't gracefully support this. One could modify the WixStdBA to detect the OS level, and if the OS is 2008R2 then enable the feature instead of invoking the default installer. From a quick dive, it looks to me that a MBA will fall back to WixStdBA using a mbapreq theme, but I can't seem to find the specific fragments they are feeding in for installing 3.5 (I can find 4.0+). From a high level, I don't know how Wix identifies which prerequisite maps to the .Net framework. If I were a betting man, they are relying on the .Net framework install requesting a reboot. And that it's the first PackageGroup/PackageGroupRef in the chain. Some people have fallen back to using a stub exe with command line parameters to enable the feature. You then can use conditions to only invoke the stub on your target OS's (I would include this in the PackageGroup you created for the 3.5 framework). 2. BA's should not modify system state for anything other than what the engine already does. If you need to modify system state, use a lite weight MSI with your registry keys in them and property drive any variables you need to assign. Jacob -----Original Message- From: Nan Zang [mailto:naz...@microsoft.com] Sent: Tuesday, February 12, 2013 5:10 PM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Subject: [WiX-users] questions on bootstrapper Hi, I am working on a setup program which needs to meet the following requirements. I tried to use bootstrapper to accomplish those, but, didn't figure out a way to do so. Thank you in advance for any help or hint. 1. Is that possible to install a dependency automatically which will be used by the customize BA UI? For example, my customize UI is written in WPF and will require .Net 3.5 is enabled on 2008R2. My question is, is there possible to detect if the feature is enabled, and if not enable it automatically? I am using the .Net 4 bootstrapper sample code as an example, and found the installation of the packages will be invoked when the MSI is launched. That doesn't meet my requirement, since I need it before the UI. Is that possible to invoke the installation action early? 2. Is there possible to launch Bootstrapper as elevated? I am following the UAC guide to create a manifest for my bootstrapper.exe, as follows, but whenever I add the following line to the wixproj, and the dialog asking for admin permission shows up but the BAUX doesn't get launched any more. Is there any guidance how to deal with this? My custom UI setup requires write a bunch of regkeys. Thank you, Nan -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get
[WiX-users] questions on bootstrapper
Hi, I am working on a setup program which needs to meet the following requirements. I tried to use bootstrapper to accomplish those, but, didn't figure out a way to do so. Thank you in advance for any help or hint. 1. Is that possible to install a dependency automatically which will be used by the customize BA UI? For example, my customize UI is written in WPF and will require .Net 3.5 is enabled on 2008R2. My question is, is there possible to detect if the feature is enabled, and if not enable it automatically? I am using the .Net 4 bootstrapper sample code as an example, and found the installation of the packages will be invoked when the MSI is launched. That doesn't meet my requirement, since I need it before the UI. Is that possible to invoke the installation action early? 2. Is there possible to launch Bootstrapper as elevated? I am following the UAC guide to create a manifest for my bootstrapper.exe, as follows, but whenever I add the following line to the wixproj, and the dialog asking for admin permission shows up but the BAUX doesn't get launched any more. Is there any guidance how to deal with this? My custom UI setup requires write a bunch of regkeys. Thank you, Nan -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] question: how to build localized (japanese) msi from wix
My problem is solved. I found I used a wrong cultureid (jp-jp) but not ja-jp, also with adding the codepage=932 definition in wixlocalization, it built correctly. Thanks for your time, Nan From: Nan Zang Sent: Thursday, January 05, 2012 5:40 PM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Cc: Nan Zang Subject: question: how to build localized (japanese) msi from wix HI, I have a simple msi only use wixui_installdir dialog set. I need to build a Japanese version of the msi. When I specify the -cultures JP-JP parameter when running light.exe, I got hundreds of error complaining $(Loc.X) is not defined. Where can I find the Japanese strings for the standard dialog and error, how can I use them? A sample error I got e:\test \1>c:\delivery\dev\wix35\src\ext\uiextension\wixlib\errorprogresstext.wxs(241) : error LGHT0102: The localization variable !(loc.Error1937) is unknown. Please ensure the variable is defined. [e:\test\test.wixproj] e:\test\1>e:\test\localizablelicenseagreementdialog.wxs(25) : error LGHT0102: The localization variable !(loc.WixUIBack) is unknown. Please ensure the variable is defined. [e:\test\test.wixproj] Many thanks in advance, Nan -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] question: how to build localized (japanese) msi from wix
HI, I have a simple msi only use wixui_installdir dialog set. I need to build a Japanese version of the msi. When I specify the -cultures JP-JP parameter when running light.exe, I got hundreds of error complaining $(Loc.X) is not defined. Where can I find the Japanese strings for the standard dialog and error, how can I use them? A sample error I got e:\test \1>c:\delivery\dev\wix35\src\ext\uiextension\wixlib\errorprogresstext.wxs(241) : error LGHT0102: The localization variable !(loc.Error1937) is unknown. Please ensure the variable is defined. [e:\test\test.wixproj] e:\test\1>e:\test\localizablelicenseagreementdialog.wxs(25) : error LGHT0102: The localization variable !(loc.WixUIBack) is unknown. Please ensure the variable is defined. [e:\test\test.wixproj] Many thanks in advance, Nan -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] change the default wixui dialog color
Hi All, I tried using ExitDialog (WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT) to allow the user to control whether our application is run at the end of the install. However, the entire checkbox control has a gray background. Is it possible to change the background color to white or make it transparent? Thanks, Nan -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to change the installed config file after msi setup
Hi Pie, thanks for replying. I am trying to change the configuration file after msi, because, I have to collect a lot of data (about 30, and some of them are arrays) from the user and add those data to the configuration file. So, right now, after using msi laying down the bits, another exe configuration.exe will be launched which will read the data and generate a new config file. But the problem is: I cannot launch the application with administrator rights, so I always get "Access denied" error, and there is also no "prompting window for admin rights". Thanks a lot, Nan -Original Message- From: Pierson Lee (PIE) [mailto:pierson@microsoft.com] Sent: Monday, March 02, 2009 1:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to change the installed config file after msi setup Is there a reason you don't want to do it through the MSI? You can edit the config file directly using XMLConfig/ -Original Message- From: Nan Zang [mailto:naz...@exchange.microsoft.com] Sent: Friday, February 27, 2009 5:29 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to change the installed config file after msi setup Hi, I am not sure if this is a wix question. But I prefer to get some advise from the setup expert here. I want to make an msi to install files (application.exe and application.exe.config) into Program Files Folder, and then from msi to launch another application to modify the application.exe.config file. However, I found my installed folder is "read only", so the user will get "access denied error" when modifying the config file. Is it possible to make the folder (or the config file) to be writable? Or is there any regular rules for this scenario? Thanks a lot, Nan -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question: how to Launch an application which requires administrator privilege
Hi, I found the answers to the launching application thread are really helpful. And I did my msi following those instructions. However, I still got a question: I got an msi file, and an application which requires administrator privilege to launch. 1. If I run the msi through the cmd line by msiexec, then it works as I expected. 2. If I double click the msi, then the application will not be launched (Nothing happened after pushing "finish" button, no prompting window for rights). If I double click the application directly, the prompting window will show up and the application runs ok. 3. I am running as a domain user, and I never configure the UAC settings on my machine, and it is default setting. How can I get the prompting window for rights when launching the application by msi? Any help will be appreciated. Thanks a lot, Nan -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to change the installed config file after msi setup
Hi, I am not sure if this is a wix question. But I prefer to get some advise from the setup expert here. I want to make an msi to install files (application.exe and application.exe.config) into Program Files Folder, and then from msi to launch another application to modify the application.exe.config file. However, I found my installed folder is "read only", so the user will get "access denied error" when modifying the config file. Is it possible to make the folder (or the config file) to be writable? Or is there any regular rules for this scenario? Thanks a lot, Nan -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question: How to get the complete value of target dir
I am going to write a registry key value which is supposed to be "c:\program files\my product\eventmessages.dll". My target dir is "c:\program files\my product". However, when I use the following statement in the wix: The regkey value is set to be "\EventMessages.dll". The value of targetdir is omitted. Is there any way I can retrieve the complete value of targetdir. Thanks a lot, Nan -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error code 0x654 thown by light.exe on x64 machine
Here is my wxs file which gives the error.
Thanks a lot,
Nan
http://schemas.microsoft.com/wix/2006/wi";
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";>
From: Nan Zang
Sent: Wednesday, February 18, 2009 2:44 PM
To: 'wix-users@lists.sourceforge.net'
Subject: Error code 0x654 thown by light.exe on x64 machine
Hi All,
I am new to wix, and got stuck to get my first wix project run. I need some
help.
Here is my problem:
I have a Windows server 2008 x64 machine and I used wix 3.0.5006.0 x64
binaries.
When I build my wix project, I got the following error:
light.exe : error LGHT0216 : An unexpected Win32 exception with error code 0x654
occurred: This installation package could not be opened. Contact the
application vendor to verify that this is a valid Windows Installer package
NMAKE : fatal error U1077: '.\light.exe' : return code '0xd8'
I met the same error when I built the project in VS2008 with x64 target
platform. But it works fine, when I change the target platform to x86.
Any help will be appreciated.
Thanks,
Nan
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Error code 0x654 thown by light.exe on x64 machine
Hi All, I am new to wix, and got stuck to get my first wix project run. I need some help. Here is my problem: I have a Windows server 2008 x64 machine and I used wix 3.0.5006.0 x64 binaries. When I build my wix project, I got the following error: light.exe : error LGHT0216 : An unexpected Win32 exception with error code 0x654 occurred: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package NMAKE : fatal error U1077: '.\light.exe' : return code '0xd8' I met the same error when I built the project in VS2008 with x64 target platform. But it works fine, when I change the target platform to x86. Any help will be appreciated. Thanks, Nan -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
