Re: [WiX-users] CheckBox Value via Custom Action
I have done this thing:
Property Id=ENABLEVIRTUALIZATION Secure=yes /CustomAction
Id=CA_SetProperty_EV Property=ENABLEVIRTUALIZATION Value=0
Execute=firstSequence /
InstallExecuteSequence Custom Action=CA_SetProperty_EV
Before=AppSearchNOT Installed AND NOT
OLDERVERSIONDETECTED/Custom/InstallExecuteSequenceInstallUISequence
Custom Action=CA_SetProperty_EV Before=AppSearchNOT Installed
AND NOT OLDERVERSIONDETECTED/Custom/InstallUISequence
Now when chkbox is disabled, the registry stored value=0 (which is
correct). Again, when I click Verify button (some action performed) and
chkbox gets enabled (and its checked by default even in disabled state) but
still i found registry value to be 0 but actually it should be one.
why is this strange behavior?
On Mon, May 14, 2012 at 7:38 PM, Ravi Raj raviraj.callin...@gmail.comwrote:
I need to perform certain action on my checkbox.
At the start if the installation the chkbox is disabled. There is a button
to call a custom action and verify certain things and assign a value to a
variable.
This variable will decide whether to enable chkbox or not. I have
implemented till this part:
Control Id=ImportCheckBoxType=CheckBoxCheckBoxValue=1
X=35 Y=100Width=160 Height=20Disabled=yes
Text=!(loc.Virtual_ChkBox) Property=ENABLEVIRTUAL Condition
Action=enable![CDATA[INTEGRATED = 1]]/Condition Condition
Action=disable![CDATA[INTEGRATED = 0]]/Condition/Control
So as soon as I launch the installer, the chkbox is disabled and
unchecked. If Verify is OK then its became enable but still unchecked.
Suppose a user does not check this box and proceeds with installation then
what vale gets stored in registry (I am storing this value ENABLEVIRTUALto
registry).
If empty gets stored then it will give error while performing repair or
uninstall. How can I store this value?
Again,
In custom action i have used a string null or empty chk (obtained from
previous installer dialog), if not null then verify works else it give
throw exception:
[CustomAction]
public static ActionResult Check(Session mpSession)
{
mpSession.Log(Begin CustomActions.Check);
String sServerName =
GetSetProperties.GetSessionProperty(mpSession, INSTALLMACHINE, false);
if (!String.IsNullOrEmpty(sServerName))
{
try
{
//Something
GetSetProperties.SetSessionProperty(mpSession,
INTEGRATED, packs.Count != 1 ? 0 : 1);
}
catch (Exception oException)
{
HandleException(mpSession, oException);
return ActionResult.Failure;
}
}
else
{
throw new Exception(SDK Service Machine cannot be empty.);
}
return ActionResult.Success;
}
private static void HandleException(Session mpSession, Exception ex)
{
string errorMsg = Exception during custom action execution: +
ex.ToString();
mpSession.Log(errorMsg);
mpSession.Message(InstallMessage.Error, new Record { FormatString
= errorMsg });
}
Here in this code Catch, else and HandleException are not working properly
and the installer gets interrupted in between. How can I fix this?
Some working code will be very useful as I am new to WiX.
--
Thanks and Regards,
Ravi Raj
--
Thanks and Regards,
Ravi Raj
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX in exit dialog according to the condition?
Hi, My install package contains one feature that require lanuch after install finished, and it's an optional feature. So is it possible to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX when the feature not installed? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-disable-WIXUI-EXITDIALOGOPTIONALCHECKBOX-in-exit-dialog-according-to-the-condition-tp7559368.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] The feature-action state value not correct after CostFinalize stage in Wix 3.6
Accroding to the msdn spec http://msdn.microsoft.com/en-us/library/aa368012.aspx, I could get feature-action value after CostFinalize stage, but in Wix 3.6 I tried to add MyFeature value to condition as below: SetProperty Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 After=CostFinalize/SetProperty It seems the feature-action value is always -1, so does anyone can give me a suggestion? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/The-feature-action-state-value-not-correct-after-CostFinalize-stage-in-Wix-3-6-tp7559587.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0
Upgraded to v3.6.2914.0 from v3.6.2907.0. None of my MSI projects build anymore (7 in the same solution, all fail but my one wixlib in the solution still builds). light.exe(0,0): error LGHT0001: Cannot set column 'Value' with a null value because this is a required field. Exception Type: System.InvalidOperationException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.ColumnDefinition.ValidateValue(Object value) in e:\delivery\Dev\wix36_public\src\wix\ColumnDefinition.cs:line 943 at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 1582 at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 602 at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) in e:\delivery\Dev\wix36_public\src\light\light.cs:line 467 Uninstalling v3.6.2914.0 reinstalling v3.6.2907.0 makes things build again successfully. Palbinder Sandher Software Platform 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 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing the burn bootstrapper
On 24/01/2012 20:09, Paul Fazio wrote: I'm trying to get bundle signing to work and I'm having some issues. I've addedSignOutputtrue/SignOutput, as mentioned. I've also overridden SignBundleEngine and SignBundle, which appear to be working because burn.exe and my bundle do have digital signatures attached. However, when I attempt to install I get the following error: Setup failed while installing the MSIs. Unspecified error. This occurs after I receive the UAC prompt. I'm obviously doing something wrong, but I'm not sure what. Any help would be greatly appreciated. I think that error occurs if you compress packages into the installer executable but don't sign them: I found that if you sign the installer but leave the MSI files unsigned then Burn fails to extract them at runtime. -- Bruce Cran -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Deserialization of wxs file
Hello, I have some automation to fill product.wxs file with fieatures/components.This file has also some ?include some.wxi? When I deserialize our product.wxs file(using wix schema) all the include parts are lost. Thank you -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343
ICE errors aren't WiX errors. Here's your hint as requested - http://msdn.microsoft.com/en-us/library/windows/desktop/aa369206.aspx or if that's not enough how about http://msdn.microsoft.com/en-us/library/windows/desktop/aa369022.aspx I think what you may be missing is basic troubleshooting and a web browser with a search engine. Palbinder Sandher Software Platform 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: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: 15 May 2012 05:26 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 2343 Hi WIX people, Is there any way to get more information when a path is supposedly empty? I've looked at all my paths and they look fine, and it would really help to be able to narrow down WHAT file/directory is missing! WIX pops out with the most astonishing errors sometimes, e.g. LGHT1076: ICE71: The Media table has no entries., and yet for something simple like when a file was not built into the installer, we proceed to build the MSI and then get no idea whatsoever what file that might have been. So we get a fatal failure for something nobody gives a crap about but we can build an entire installer without actually putting the required files into it? This can't be right, I must be missing something. Can anyone give me hint? :-) Thanks, Aaron Oxford Object Trading Pty Ltd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX in exit dialog according to the condition?
According to http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm you should just need to set the WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT property to an empty value for the checkbox to not show. WiX v3.5 sources also show similar. How you do that is up to you. Type 51 Custom Action is probably what I'd use - http://msdn.microsoft.com/en-us/library/windows/desktop/aa368237.aspx Palbinder Sandher Software Platform 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: tzleon [mailto:tzl...@gmail.com] Sent: 15 May 2012 08:15 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX in exit dialog according to the condition? Hi, My install package contains one feature that require lanuch after install finished, and it's an optional feature. So is it possible to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX when the feature not installed? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-disable-WIXUI-EXITDIALOGOPTIONALCHECKBOX-in-exit-dialog-according-to-the-condition-tp7559368.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing the burn bootstrapper
On 15/05/2012 11:35, Bruce Cran wrote: I think that error occurs if you compress packages into the installer executable but don't sign them: I found that if you sign the installer but leave the MSI files unsigned then Burn fails to extract them at runtime. The problem wasn't with the packages, it was with the engine. If the engine isn't signed then Burn fails. -- Bruce Cran -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Any way to debug managed custom action in VS?
This question sounds quite straightforward but I couldn't find a clear solution. I have created one WIX custom action project and one WIX installer project which is using this managed CA dll. It succeeds in calling the function of CA project, but inside the CA function there is some error. So obviously I want to step into my CA function to see what's going on. But I don't know how to do that. I tried to attach to the msiexec process, but still after I put one break point at my CA function, it says no symbol loaded. I take it means my CUSTOM_ACTION.pdb is not loaded or built with the installer project. But it is not like any other project where I can set to include the pdb file in debug mode complication. I did try this: Binary Id=CustomActionDll SourceFile=$(var.CUSTOM_ACTION_PROJ.TargetDir)$(var.CUSTOM_ACTION_PROJ.TargetName).CA.dll / Binary Id=CustomActionDll_dbg SourceFile=$(var.CUSTOM_ACTION_PROJ.TargetDir)$(var.CUSTOM_ACTION_PROJ.TargetName).pdb / But still it doesn't work. I still can't step into my function. Is it even possible to step into a custom project's function? Thanks! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Any-way-to-debug-managed-custom-action-in-VS-tp7559820.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343
Hi Aaron, If you get an error about no Media table, perhaps you are missing a line such as: Media Id=1 Cabinet=media1.cab EmbedCab=yes / in your product.wxs file. I haven't taken the time to verify what errors you get if this line is missing, since I've always included it, but that's a quick stab at it. I generally find the WiX errors (or ICE errors) give me enough information to figure out what's going on. If you give more details, such as the actual build output and excerpts from your product.wxs then I suspect you will get more help. This group is quite active. Sincerely, Daniel Madill -Original Message- From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: 15 May 2012 05:26 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 2343 Hi WIX people, Is there any way to get more information when a path is supposedly empty? I've looked at all my paths and they look fine, and it would really help to be able to narrow down WHAT file/directory is missing! WIX pops out with the most astonishing errors sometimes, e.g. LGHT1076: ICE71: The Media table has no entries., and yet for something simple like when a file was not built into the installer, we proceed to build the MSI and then get no idea whatsoever what file that might have been. So we get a fatal failure for something nobody gives a crap about but we can build an entire installer without actually putting the required files into it? This can't be right, I must be missing something. Can anyone give me hint? :-) Thanks, Aaron Oxford Object Trading Pty Ltd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Any way to debug managed custom action in VS?
Check out the following http://blog.torresdal.net/CommentView,guid,BFEBE347-AD82-4C76-A96E-1C22AA39EFC9.aspx http://blog.torresdal.net/CommentView,guid,BFEBE347-AD82-4C76-A96E-1C22AA39EFC9.aspx -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Any-way-to-debug-managed-custom-action-in-VS-tp7559820p7559889.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deserialization of wxs file
The WiX CodeDom does not understand the preprocessor. On Tue, May 15, 2012 at 4:06 AM, Ilana Girshevich ilana...@yahoo.comwrote: Hello, I have some automation to fill product.wxs file with fieatures/components.This file has also some ?include some.wxi? When I deserialize our product.wxs file(using wix schema) all the include parts are lost. Thank you -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0
Did you rebuild all source? Looks like a field is no longer nullable and you might have stale wixobj or wixlib. Otherwise it's a bug and a repro would be appreciated. On Tue, May 15, 2012 at 3:34 AM, Pally Sandher pally.sand...@iesve.comwrote: Upgraded to v3.6.2914.0 from v3.6.2907.0. None of my MSI projects build anymore (7 in the same solution, all fail but my one wixlib in the solution still builds). light.exe(0,0): error LGHT0001: Cannot set column 'Value' with a null value because this is a required field. Exception Type: System.InvalidOperationException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.ColumnDefinition.ValidateValue(Object value) in e:\delivery\Dev\wix36_public\src\wix\ColumnDefinition.cs:line 943 at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 1582 at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 602 at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) in e:\delivery\Dev\wix36_public\src\light\light.cs:line 467 Uninstalling v3.6.2914.0 reinstalling v3.6.2907.0 makes things build again successfully. Palbinder Sandher Software Platform 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 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0
All I did was Rebuild All in VS 2010 Rob. Clean All followed by Rebuild All exhibits the same behaviour. Palbinder Sandher Software Platform 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: Rob Mensching [mailto:r...@robmensching.com] Sent: 15 May 2012 15:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0 Did you rebuild all source? Looks like a field is no longer nullable and you might have stale wixobj or wixlib. Otherwise it's a bug and a repro would be appreciated. On Tue, May 15, 2012 at 3:34 AM, Pally Sandher pally.sand...@iesve.comwrote: Upgraded to v3.6.2914.0 from v3.6.2907.0. None of my MSI projects build anymore (7 in the same solution, all fail but my one wixlib in the solution still builds). light.exe(0,0): error LGHT0001: Cannot set column 'Value' with a null value because this is a required field. Exception Type: System.InvalidOperationException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.ColumnDefinition.ValidateValue(Object value) in e:\delivery\Dev\wix36_public\src\wix\ColumnDefinition.cs:line 943 at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 1582 at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 602 at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) in e:\delivery\Dev\wix36_public\src\light\light.cs:line 467 Uninstalling v3.6.2914.0 reinstalling v3.6.2907.0 makes things build again successfully. Palbinder Sandher Software Platform 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 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] RE: How to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX in exit dialog according to the condition?
I did something like this: SetProperty Id=WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT Value=Run application After=ExecuteAction Sequence=ui![CDATA[WorkstationFeature = 3]]/SetProperty Where WorkstationFeature is a reference to my optional feature. Neil -Original Message- From: tzleon [mailto:tzl...@gmail.com] Sent: 15 May 2012 08:12 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX in exit dialog according to the condition? Hi, My install package contains one feature that require lanuch after install finished, and it's an optional feature. So is it possible to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX when the feature not installed? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-disable-WIXUI-EXITDIALOGOPTIONALCHECKBOX-in-exit-dialog-according-to-the-condition-tp7559368.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0
On 15-May-12 06:34, Pally Sandher wrote: at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 1582 Definitely a bug, please file. Workaround is to not suppress .wixpdb output. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0
Done - https://sourceforge.net/tracker/?func=detailaid=3526942group_id=105970atid=642714 Cheers Bob. Palbinder Sandher Software Platform 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: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 15 May 2012 15:48 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0 On 15-May-12 06:34, Pally Sandher wrote: at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 1582 Definitely a bug, please file. Workaround is to not suppress .wixpdb output. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] The feature-action state value not correct after CostFinalize stage in Wix 3.6
In cases where the user chooses features from a dialog, that dialog is after CostFinalize in the MSI files I've looked at, so feature-action is unknown. Maybe it's correct after CostFinalize if you've specified features in advance on the command line, but I don't know if that's what you're doing. Phil W -Original Message- From: tzleon [mailto:tzl...@gmail.com] Sent: Tuesday, May 15, 2012 2:56 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] The feature-action state value not correct after CostFinalize stage in Wix 3.6 Accroding to the msdn spec http://msdn.microsoft.com/en-us/library/aa368012.aspx, I could get feature-action value after CostFinalize stage, but in Wix 3.6 I tried to add MyFeature value to condition as below: SetProperty Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 After=CostFinalize/SetProperty It seems the feature-action value is always -1, so does anyone can give me a suggestion? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/The-feature-action-state-value-not-correct-after-CostFinalize-stage-in-Wix-3-6-tp7559587.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. 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). -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Hot do I replace specific files of a wixlib with newer versions in my installer?
Hi, I am using a large wixlib file in my wix installer. Now, I want to include newer versions of a few files in my installer which are included in the wixlib, without rebuilding the wixlib. Instead, I want to include the newer version of these files in my main wxs file. I learned that the Ids of the newer files (files collected by heat) have to be different from the Ids of the old files in the wixlib. This can be done with an xslt called by heat. The problem is now, how do i define or force the order of installed files to be sure that the newer files are indeed installed, and not overwritten by files of same name in the wixlib. In other words, how do I define or modify the order of installed files in wix? Thanks, Michael -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hot-do-I-replace-specific-files-of-a-wixlib-with-newer-versions-in-my-installer-tp7560394.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343
Hi Pally and thanks for the reply, I believe you've missed the point, and subject, of my post: Error 2343 - Specified path is empty. I used the ICE error as an example of getting too much information, as opposed to the Error 2343 which couldn't really be less helpful, even with verbose logging. The other error actually came up as I was _troubleshooting_ Error 2343 and attempting to remove all file deployment in entirety, so that I could slowly eliminate possible causes of Error 2343. It is the Error 2343 - Specified path is empty - that I am trying to solve. I need to find out what path is empty. There are many, many paths, and none of them are listed as empty when I do a verbose log of Error 2343. By the way, it seems I need to explicitly state that I've looked up Error code 2343 using Google. You can read up on Error 2343 here http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. 85%29.aspx before replying if you like. That way you won't be sharing any information that's already available to me, just the new information specific to this case that results from analysing the question (about Error 2343) using your skill and experience. ;-) Perhaps it was the tone of my post about Error 2343 that led you chastise me for not looking up 2343 - Specified path is empty myself, but I don't think my browser and search engine are going to help me extract information from Error 2343 that simply isn't there. What I need to know is what the MSI is actually trying to do when this error occurs. That is why I posted here asking if there is any other way to get information out of the MSI about Error 2343 as it tries to 'get installed' by the Windows Installer. ;-) After even more reading, I also now understand that the lack of information in Error 2343 probably isn't WIX's fault, even if the flawed MSI is. This looks like standard Microsoft behaviour (in the Windows Installer code), where you go to the trouble of allocating unique error codes, like 2343, but never consider making the messages useful, like Specified path is empty. Looks like that one fell straight through the code review; they couldn't even be bothered making it (the error message for Error 2343) a sentence. In addition to that, unlike every other person with this problem on every forum and code sharing site I could Google, I'm not playing with a folder browser dialog when I get my Error 2343. I'm working on top of a large pre-existing library (that I have tested separately as working) and simply deploying a few files that are specific to my project, so I suspect that my 2343 - Specified path is empty is not related to the root installer directory but one of the subdirectories I'm attempting to create. But, I'd have to know WHAT PATH IS EMPTY (Error 2343) to confirm that. :-D Not to worry, I've had to roll back a bunch of changes to a version of the scripts that work OK and don't crash with Error 2343. You live you learn I guess - after all, all the changes compiled (no Error 2343), and how could WIX create an MSI that doesn't install correctly if it compiles without warnings? Hahahaha [cry]. When I work out what caused my Error 2343 - Specified path is empty I'll post back here with my fix in the hopes of maybe helping someone out. ;-) Error 2343 Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, 15 May 2012 21:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 ICE errors aren't WiX errors. Here's your hint as requested - http://msdn.microsoft.com/en-us/library/windows/desktop/aa369206.aspx or if that's not enough how about http://msdn.microsoft.com/en-us/library/windows/desktop/aa369022.aspx I think what you may be missing is basic troubleshooting and a web browser with a search engine. Palbinder Sandher Software Platform 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: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: 15 May 2012 05:26 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 2343 Hi WIX people, Is there any way to get more information when a path is supposedly empty? I've looked at all my
Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0
On 15-May-12 10:53, Pally Sandher wrote: Done - https://sourceforge.net/tracker/?func=detailaid=3526942group_id=105970atid=642714 Thanks. Fixed for Monday's build. I am curious, however: Why do you suppress .wixpdb generation? Is it a question of perf? -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] The feature-action state value not correct after CostFinalize stage in Wix 3.6
Can I adjust the order of CostFinalize and Feature select dialog? Why the CostFinalize after Feature select dialog in Wix? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/The-feature-action-state-value-not-correct-after-CostFinalize-stage-in-Wix-3-6-tp7559587p7561066.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] RE: How to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX in exit dialog according to the condition?
Yes, That's did the trick, thanks! Neil Sleightholm wrote I did something like this: SetProperty Id=WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT Value=Run application After=ExecuteAction Sequence=ui/SetProperty Where WorkstationFeature is a reference to my optional feature. Neil -Original Message- From: tzleon [mailto:tzleon@] Sent: 15 May 2012 08:12 To: wix-users@.sourceforge Subject: [WiX-users] How to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX in exit dialog according to the condition? Hi, My install package contains one feature that require lanuch after install finished, and it's an optional feature. So is it possible to disable WIXUI_EXITDIALOGOPTIONALCHECKBOX when the feature not installed? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-disable-WIXUI-EXITDIALOGOPTIONALCHECKBOX-in-exit-dialog-according-to-the-condition-tp7559368.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-disable-WIXUI-EXITDIALOGOPTIONALCHECKBOX-in-exit-dialog-according-to-the-condition-tp7559368p7561082.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343
Regarding trying to find the cause of an Error 2343 - Specified path is empty. The only way I discovered to deal with this problem was through a process of elimination. Even having now found the exact location of the problem I can see that there would have been nothing in any of the logs that could have led me there any faster. It turned out that I was setting a flag incorrectly which caused this to manifest somewhere within the thousands of lines of third-party wixlib on which my project is built. (An extension directory was unnecessarily declared, which would require me to show a custom browser dialog in order to set its location. Having not done that, the wixlib attempted to use an undefined directory, resulting in the error.) The only thing that could have helped me here is if the MSI had logged what it was trying to do before running into the error. I don't know if that's even possible within the Windows Installer framework, but if WIX could do this it would be incredibly helpful. Thanks for listening everyone. Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: Wednesday, 16 May 2012 09:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 Hi Pally and thanks for the reply, I believe you've missed the point, and subject, of my post: Error 2343 - Specified path is empty. I used the ICE error as an example of getting too much information, as opposed to the Error 2343 which couldn't really be less helpful, even with verbose logging. The other error actually came up as I was _troubleshooting_ Error 2343 and attempting to remove all file deployment in entirety, so that I could slowly eliminate possible causes of Error 2343. It is the Error 2343 - Specified path is empty - that I am trying to solve. I need to find out what path is empty. There are many, many paths, and none of them are listed as empty when I do a verbose log of Error 2343. By the way, it seems I need to explicitly state that I've looked up Error code 2343 using Google. You can read up on Error 2343 here http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. 85%29.aspx before replying if you like. That way you won't be sharing any information that's already available to me, just the new information specific to this case that results from analysing the question (about Error 2343) using your skill and experience. ;-) Perhaps it was the tone of my post about Error 2343 that led you chastise me for not looking up 2343 - Specified path is empty myself, but I don't think my browser and search engine are going to help me extract information from Error 2343 that simply isn't there. What I need to know is what the MSI is actually trying to do when this error occurs. That is why I posted here asking if there is any other way to get information out of the MSI about Error 2343 as it tries to 'get installed' by the Windows Installer. ;-) After even more reading, I also now understand that the lack of information in Error 2343 probably isn't WIX's fault, even if the flawed MSI is. This looks like standard Microsoft behaviour (in the Windows Installer code), where you go to the trouble of allocating unique error codes, like 2343, but never consider making the messages useful, like Specified path is empty. Looks like that one fell straight through the code review; they couldn't even be bothered making it (the error message for Error 2343) a sentence. In addition to that, unlike every other person with this problem on every forum and code sharing site I could Google, I'm not playing with a folder browser dialog when I get my Error 2343. I'm working on top of a large pre-existing library (that I have tested separately as working) and simply deploying a few files that are specific to my project, so I suspect that my 2343 - Specified path is empty is not related to the root installer directory but one of the subdirectories I'm attempting to create. But, I'd have to know WHAT PATH IS EMPTY (Error 2343) to confirm that. :-D Not to worry, I've had to roll back a bunch of changes to a version of the scripts that work OK and don't crash with Error 2343. You live you learn I guess - after all, all the changes compiled (no Error 2343), and how could WIX create an MSI that doesn't install correctly if it compiles without warnings? Hahahaha [cry]. When I work out what caused my Error 2343 - Specified path is empty I'll post back here with my fix in the
Re: [WiX-users] Hot do I replace specific files of a wixlib with newer versions in my installer?
Did you bind the files in the .wixlib? If so, you need to rebuild the .wixlib. Also, order of files installed is not something you control in MSI. You shouldn't need order. Just list the filles you want installed and they will all be installed. On Tue, May 15, 2012 at 11:01 AM, mba mlba...@gmail.com wrote: Hi, I am using a large wixlib file in my wix installer. Now, I want to include newer versions of a few files in my installer which are included in the wixlib, without rebuilding the wixlib. Instead, I want to include the newer version of these files in my main wxs file. I learned that the Ids of the newer files (files collected by heat) have to be different from the Ids of the old files in the wixlib. This can be done with an xslt called by heat. The problem is now, how do i define or force the order of installed files to be sure that the newer files are indeed installed, and not overwritten by files of same name in the wixlib. In other words, how do I define or modify the order of installed files in wix? Thanks, Michael -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hot-do-I-replace-specific-files-of-a-wixlib-with-newer-versions-in-my-installer-tp7560394.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343
What exactly needed to be caught? If we can catch it in the WiX toolset we should. On Tue, May 15, 2012 at 7:09 PM, Aaron Oxford aaron.oxf...@objecttrading.com wrote: Regarding trying to find the cause of an Error 2343 - Specified path is empty. The only way I discovered to deal with this problem was through a process of elimination. Even having now found the exact location of the problem I can see that there would have been nothing in any of the logs that could have led me there any faster. It turned out that I was setting a flag incorrectly which caused this to manifest somewhere within the thousands of lines of third-party wixlib on which my project is built. (An extension directory was unnecessarily declared, which would require me to show a custom browser dialog in order to set its location. Having not done that, the wixlib attempted to use an undefined directory, resulting in the error.) The only thing that could have helped me here is if the MSI had logged what it was trying to do before running into the error. I don't know if that's even possible within the Windows Installer framework, but if WIX could do this it would be incredibly helpful. Thanks for listening everyone. Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: Wednesday, 16 May 2012 09:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 Hi Pally and thanks for the reply, I believe you've missed the point, and subject, of my post: Error 2343 - Specified path is empty. I used the ICE error as an example of getting too much information, as opposed to the Error 2343 which couldn't really be less helpful, even with verbose logging. The other error actually came up as I was _troubleshooting_ Error 2343 and attempting to remove all file deployment in entirety, so that I could slowly eliminate possible causes of Error 2343. It is the Error 2343 - Specified path is empty - that I am trying to solve. I need to find out what path is empty. There are many, many paths, and none of them are listed as empty when I do a verbose log of Error 2343. By the way, it seems I need to explicitly state that I've looked up Error code 2343 using Google. You can read up on Error 2343 here http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. 85%29.aspx before replying if you like. That way you won't be sharing any information that's already available to me, just the new information specific to this case that results from analysing the question (about Error 2343) using your skill and experience. ;-) Perhaps it was the tone of my post about Error 2343 that led you chastise me for not looking up 2343 - Specified path is empty myself, but I don't think my browser and search engine are going to help me extract information from Error 2343 that simply isn't there. What I need to know is what the MSI is actually trying to do when this error occurs. That is why I posted here asking if there is any other way to get information out of the MSI about Error 2343 as it tries to 'get installed' by the Windows Installer. ;-) After even more reading, I also now understand that the lack of information in Error 2343 probably isn't WIX's fault, even if the flawed MSI is. This looks like standard Microsoft behaviour (in the Windows Installer code), where you go to the trouble of allocating unique error codes, like 2343, but never consider making the messages useful, like Specified path is empty. Looks like that one fell straight through the code review; they couldn't even be bothered making it (the error message for Error 2343) a sentence. In addition to that, unlike every other person with this problem on every forum and code sharing site I could Google, I'm not playing with a folder browser dialog when I get my Error 2343. I'm working on top of a large pre-existing library (that I have tested separately as working) and simply deploying a few files that are specific to my project, so I suspect that my 2343 - Specified path is empty is not related to the root installer directory but one of the subdirectories I'm attempting to create. But, I'd have to know WHAT PATH IS EMPTY (Error 2343) to confirm that. :-D Not to worry, I've had to roll back a bunch of changes to a version of the scripts that work OK and don't crash with Error 2343. You live you learn I guess - after all, all the changes
Re: [WiX-users] Error 2343
Hi Rob, I don't believe you'd be able to catch this, based on my very limited understanding of WIX and the installer services. Since the directory path in question was supposed to be dynamically set, there would be no way to be sure at compile time that the directory will exist (or that the path var exists/is valid). And since the Windows Installer doesn't give any information about what was missing from where, the only way we could know what went wrong is if we had logged what we were trying to do just before we attempted to do it. Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, 16 May 2012 13:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 What exactly needed to be caught? If we can catch it in the WiX toolset we should. On Tue, May 15, 2012 at 7:09 PM, Aaron Oxford aaron.oxf...@objecttrading.com wrote: Regarding trying to find the cause of an Error 2343 - Specified path is empty. The only way I discovered to deal with this problem was through a process of elimination. Even having now found the exact location of the problem I can see that there would have been nothing in any of the logs that could have led me there any faster. It turned out that I was setting a flag incorrectly which caused this to manifest somewhere within the thousands of lines of third-party wixlib on which my project is built. (An extension directory was unnecessarily declared, which would require me to show a custom browser dialog in order to set its location. Having not done that, the wixlib attempted to use an undefined directory, resulting in the error.) The only thing that could have helped me here is if the MSI had logged what it was trying to do before running into the error. I don't know if that's even possible within the Windows Installer framework, but if WIX could do this it would be incredibly helpful. Thanks for listening everyone. Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: Wednesday, 16 May 2012 09:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 Hi Pally and thanks for the reply, I believe you've missed the point, and subject, of my post: Error 2343 - Specified path is empty. I used the ICE error as an example of getting too much information, as opposed to the Error 2343 which couldn't really be less helpful, even with verbose logging. The other error actually came up as I was _troubleshooting_ Error 2343 and attempting to remove all file deployment in entirety, so that I could slowly eliminate possible causes of Error 2343. It is the Error 2343 - Specified path is empty - that I am trying to solve. I need to find out what path is empty. There are many, many paths, and none of them are listed as empty when I do a verbose log of Error 2343. By the way, it seems I need to explicitly state that I've looked up Error code 2343 using Google. You can read up on Error 2343 here http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. 85%29.aspx before replying if you like. That way you won't be sharing any information that's already available to me, just the new information specific to this case that results from analysing the question (about Error 2343) using your skill and experience. ;-) Perhaps it was the tone of my post about Error 2343 that led you chastise me for not looking up 2343 - Specified path is empty myself, but I don't think my browser and search engine are going to help me extract information from Error 2343 that simply isn't there. What I need to know is what the MSI is actually trying to do when this error occurs. That is why I posted here asking if there is any other way to get information out of the MSI about Error 2343 as it tries to 'get installed' by the Windows Installer. ;-) After even
