Nabble - Windows Installer XML (WiX) toolset

Re: Debugging ExecuteSqlStrings

2008-12-01T18:06:49Z

Rui Fan (MDT InfoTech) wrote:
> Error 26204. Error -2147217900: failed to execute SQL string, error detail: Incorrect syntax near the keyword 'with'. ……
> MSI (s) (68!24) [15:49:56:154]: Product: Microsoft MAA - Core Database -- Error 26204. Error -2147217900: failed to execute SQL string, error detail: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon., SQL key: CoreDBSBSQLScript SQL string: riginal error information.
> ……
>

The error message is coming from SQL, not the custom action. You'll have
better luck debugging the SQL strings.

> I found a function called “ExecuteSqlStrings” under serverca\scaexec. I can’t find the generated scaexec.dll in wix3-binaries.zip.

It's embedded in WixSqlExtension.dll. If you want to debug the code,
you'll need to rebuild the scaexec.dll and WixSqlExtension.dll.

--
sig://boB
http://joyofsetup.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Permanent Component being removed on uninstall

2008-12-01T18:02:39Z

Dylan Moline (Volt) wrote:
> Un-registering it shouldn't remove it should it?
>

No, it's merely indicating that this product is going away, so should no
longer be considered a "client" of the component. Look elsewhere in the
log for that registry key. Also look at custom actions that directly
manipulate the registry.

--
sig://boB
http://joyofsetup.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: cannot find VCProjectEngine (again, ignore the previous one if it went through)

2008-12-01T18:01:32Z

Jason Ding wrote:
> Thanks for the reply.
> I guess you misunderstood my question - I am using VC2008 and .Net
> Framework 3.5, but when I build I got error message about missing
> VCProjectEngine and suggest to install VC2005 and .Net Framework 2.0.
>

I understand that. I'm asking if you're trying to create a .sln that
contains a .wixproj that refers to project variables from a .vcproj. If
so, it's a known limitation with .vcproj support in .wixprojs.

--
sig://boB
http://joyofsetup.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: How would people handle this situation

2008-12-01T17:49:24Z

Sean Farrow wrote:
> do a registry search for the uninstallation executable, if the exe is
> found run it.
> I can accomplish the first part (registry search), but I need the custom
> action to come before any ui dialogues. Wher should I sequence this ca?
>

Unless the uninstaller runs with limited user privileges, it's going to
fail on Windows Vista and Server 2008, because it won't be able to get
elevated privileges.

--
sig://boB
http://joyofsetup.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Install Localisation

2008-12-01T17:47:42Z

Neil Sleightholm wrote:
> 2. Every time I run light it will create a new product code but I don't
> want that, I want one product code and simply install with a different
> UI language. From what I have read this seems to be a valid approach.
>

The MSI SDK disagrees. In fact, it's unusually unambiguous [emphasis mine]:

A localized product is considered a different product. For example, the
German and English versions of an application are considered two
different products and /must /have different product codes.

--
sig://boB
http://joyofsetup.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Permanent Component being removed on uninstall

2008-12-01T16:44:01Z

Yes, with or without a KeyPath there, is still is removed.

~Dylan

-----Original Message-----
From: Wilson, Phil [mailto:Phil.Wilson@...]
Sent: Monday, December 01, 2008 4:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Permanent Component being removed on uninstall

And the Component table has something in KeyPath?

Phil Wilson

-----Original Message-----
From: Dylan Moline (Volt) [mailto:a-dylanm@...]
Sent: Monday, December 01, 2008 3:01 PM
To: wix-users@...
Subject: [WiX-users] Permanent Component being removed on uninstall

Trying to create a registry key which is edited by an application, and keep the entire key after the program is uninstalled (incase it is re-installed, want the stored data to remain)

Here is the sample code. However, every time I install, it creates the proper key, but when I uninstall via ARP, it removes the entire key.

<Component Id="foo" Guid="xxx" Permanent="yes">
<Registry Action="createKey" Root="HKLM" Key="SOFTWARE\foo\blah"/>
</Component>

I've checked the package with ORCA, and it shows the component table with the attribute of 16, which should translate properly to "permanent".

Even if I manually go in an add a string/Dword, it still all gets removed on uninstall.

Am I missing something? (using wix 2)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Permanent Component being removed on uninstall

2008-12-01T16:32:28Z

The log is showing this:
MSI (s) (98:20) [16:09:09:028]: Disallowing uninstallation of component: {5703B886-7D29-45D1-9EFF-35198D58EC20} since another client exists

And then this:
MSI (s) (98:2C) [16:18:48:399]: Executing op: ComponentUnregister(ComponentId={5703B886-7D29-45D1-9EFF-35198D58EC20},,BinaryType=0,PreviouslyPinned=1)

Un-registering it shouldn't remove it should it?

I'm not seeing anywhere else where its being called to remove (except RemoveRegistryValues, and even if I suppress that (which I don't want to have to do)) it still removes it.

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: Monday, December 01, 2008 3:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Permanent Component being removed on uninstall

Verbose log file will explain why it is being uninstalled.

-----Original Message-----
From: Dylan Moline (Volt) [mailto:a-dylanm@...]
Sent: Monday, December 01, 2008 15:01
To: wix-users@...
Subject: [WiX-users] Permanent Component being removed on uninstall

Trying to create a registry key which is edited by an application, and keep the entire key after the program is uninstalled (incase it is re-installed, want the stored data to remain)

Here is the sample code. However, every time I install, it creates the proper key, but when I uninstall via ARP, it removes the entire key.

<Component Id="foo" Guid="xxx" Permanent="yes">
<Registry Action="createKey" Root="HKLM" Key="SOFTWARE\foo\blah"/>
</Component>

I've checked the package with ORCA, and it shows the component table with the attribute of 16, which should translate properly to "permanent".

Even if I manually go in an add a string/Dword, it still all gets removed on uninstall.

Am I missing something? (using wix 2)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Debugging ExecuteSqlStrings

2008-12-01T16:25:58Z

Hi experts,
I’m using WiX 3. I’m trying to debug a possible error in the sql custom action:
MSI (s) (68:B4) [15:49:43:129]: Executing op: CustomActionSchedule(Action=ExecuteSqlStrings,ActionType=25601,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) (68:F8) [15:49:43:139]: Invoking remote custom action. DLL: D:\Windows\Installer\MSI612C.tmp, Entrypoint: ExecuteSqlStrings
ExecuteSqlStrings: CustomActionData: CoreSqlDatabase€RUIFANRED280B\MAA€€CoreDB€3€1€€€GrantNetworkServiceAdmin€17€EXEC sp_addsrvrolemember "NT AUTHORITY\NETWORK SERVICE", ……
MSI (c) (58:30) [15:49:45:118]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

Error 26204. Error -2147217900: failed to execute SQL string, error detail: Incorrect syntax near the keyword 'with'. ……
MSI (s) (68!24) [15:49:56:154]: Product: Microsoft MAA - Core Database -- Error 26204. Error -2147217900: failed to execute SQL string, error detail: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon., SQL key: CoreDBSBSQLScript SQL string: riginal error information.
……
Action ended 15:49:56: InstallFinalize. Return value 3.

I found a function called “ExecuteSqlStrings” under serverca\scaexec. I can’t find the generated scaexec.dll in wix3-binaries.zip. But I can find it in the msi package. Where did this file come from? And I also tried to add “DebugBreak()” in “ExecuteSqlStrings” but it doesn't work.
Which can I find the correct entry point of ExecuteSqlStrings? Which is the correct file and line to set break points?
And do you have any best practice to debug a running custom action?

Thanks,
Rui
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Permanent Component being removed on uninstall

2008-12-01T16:25:45Z

And the Component table has something in KeyPath?

Phil Wilson

-----Original Message-----
From: Dylan Moline (Volt) [mailto:a-dylanm@...]
Sent: Monday, December 01, 2008 3:01 PM
To: wix-users@...
Subject: [WiX-users] Permanent Component being removed on uninstall

Trying to create a registry key which is edited by an application, and keep the entire key after the program is uninstalled (incase it is re-installed, want the stored data to remain)

Here is the sample code. However, every time I install, it creates the proper key, but when I uninstall via ARP, it removes the entire key.

<Component Id="foo" Guid="xxx" Permanent="yes">
<Registry Action="createKey" Root="HKLM" Key="SOFTWARE\foo\blah"/>
</Component>

I've checked the package with ORCA, and it shows the component table with the attribute of 16, which should translate properly to "permanent".

Even if I manually go in an add a string/Dword, it still all gets removed on uninstall.

Am I missing something? (using wix 2)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: any tips on why the following xmlfile machine.config install changes are not working

2008-12-01T16:23:58Z

Btw - I was using initially using the following to arrive at my NetFramework20ConfigDir setting for use referencing machine.config file. registry search result.

<PropertyRef Id="NETFRAMEWORK20INSTALLROOTDIR" />

<Directory Id="NETFRAMEWORK20INSTALLROOTDIR">
<Directory Id="NetFramework20ConfigDir" Name="CONFIG" />
</Directory>

In case of $(var.Platform) = "x64" build output the installer was given me a systems is was giving me a WixNetFxExtensions property NETFRAMEWORK20INSTALLROOTDIR result that was using System\Wow6432Node for the installRoot registry key lookup. Is that expected?

I locally implemented the following and in the local implementation case I get the desired non-Software\Wow6432Node result using the exact same registry search entry.
<Property Id="NFX20INSTALLROOTDIR">
<RegistrySearch Id="NfxInstallRootForNetfx20Search" Type="raw" Root="HKLM" Key="Software\Microsoft\.NETFramework" Name="InstallRoot">
<DirectorySearch Id="Nfx20InstallRootSearch" Path="v2.0.50727" Depth="0" />
</RegistrySearch>
</Property>
<Property Id="NFX20X86INSTALLROOTDIR">
<RegistrySearch Id="NfxX86InstallRootForNetfx20Search" Type="raw" Root="HKLM" Key="Software\Wow6432Node\Microsoft\.NETFramework" Name="InstallRoot">
<DirectorySearch Id="Nfx20X86InstallRootSearch" Path="v2.0.50727" Depth="0" />
</RegistrySearch>
</Property>

-----Original Message-----
From: Robert O'Brien
Sent: Monday, December 01, 2008 4:17 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] any tips on why the following xmlfile machine.config install changes are not working

Got this to work switching XmlFile entry for install pass to following XmlConfig entry.

<util:XmlConfig Id="AddBehaviorExtensionsEnableBizTalkHeaderInspector" File="[NetFramework20ConfigDir]machine.config"
ElementPath="/configuration/system.serviceModel/extensions/behaviorExtensions"
Action="create" Node="document" On="install"><![CDATA[

<add name="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
]]></util:XmlConfig>

-----Original Message-----
From: Robert O'Brien [mailto:Robert.OBrien@...]
Sent: Monday, December 01, 2008 11:39 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] any tips on why the following xmlfile machine.config install changes are not working

Any tips on why the following xmlfile machine.config install changes are not working?

I'm using the following component entries:
<util:XmlFile Id="AddBehaviorExtensionsEnableBizTalkHeaderInspector" File="[NetFramework20ConfigDir]machine.config"
ElementPath="/configuration/system.serviceModel/extensions/behaviorExtensions"
Name="add" Value="name="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94""
Action="createElement" />

<util:XmlConfig Id="RemoveBehaviorExtensionsEnableBizTalkHeaderInspector" File="[NetFramework20ConfigDir]machine.config"
ElementPath="/configuration/system.serviceModel/extensions/behaviorExtensions"
VerifyPath="/configuration/system.serviceModel/extensions/behaviorExtensions/add[\[]@name="enableBizTalkHeaderInspector" && @type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94"[\]]"
Action="delete" Node="element" On="uninstall" />

To try and get this new <add /> element created during install but finding that no machine.config changes exist after setup completes.
<configuration>
<system.serviceModel>
<extensions>
<behaviorExtensions>
.
. .
. . .
<add name="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94" />
</behaviorExtensions>

The verbose logs show the following ExecXmlFile property setting and execution of a similarly named custom action
Property(S): ExecXmlFile = 2EUR0EURC:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.configEUR5EUR0EUR/configuration/system.serviceModel/extensions/behaviorExtensionsEURaddEURname="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94"

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: any tips on why the following xmlfile machine.config install changes are not working

2008-12-01T16:16:52Z

Got this to work switching XmlFile entry for install pass to following XmlConfig entry.

<util:XmlConfig Id="AddBehaviorExtensionsEnableBizTalkHeaderInspector" File="[NetFramework20ConfigDir]machine.config"
ElementPath="/configuration/system.serviceModel/extensions/behaviorExtensions"
Action="create" Node="document" On="install"><![CDATA[

<add name="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
]]></util:XmlConfig>

-----Original Message-----
From: Robert O'Brien [mailto:Robert.OBrien@...]
Sent: Monday, December 01, 2008 11:39 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] any tips on why the following xmlfile machine.config install changes are not working

Any tips on why the following xmlfile machine.config install changes are not working?

I'm using the following component entries:
<util:XmlFile Id="AddBehaviorExtensionsEnableBizTalkHeaderInspector" File="[NetFramework20ConfigDir]machine.config"
ElementPath="/configuration/system.serviceModel/extensions/behaviorExtensions"
Name="add" Value="name="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94""
Action="createElement" />

<util:XmlConfig Id="RemoveBehaviorExtensionsEnableBizTalkHeaderInspector" File="[NetFramework20ConfigDir]machine.config"
ElementPath="/configuration/system.serviceModel/extensions/behaviorExtensions"
VerifyPath="/configuration/system.serviceModel/extensions/behaviorExtensions/add[\[]@name="enableBizTalkHeaderInspector" && @type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94"[\]]"
Action="delete" Node="element" On="uninstall" />

To try and get this new <add /> element created during install but finding that no machine.config changes exist after setup completes.
<configuration>
<system.serviceModel>
<extensions>
<behaviorExtensions>
.
. .
. . .
<add name="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94" />
</behaviorExtensions>

The verbose logs show the following ExecXmlFile property setting and execution of a similarly named custom action
Property(S): ExecXmlFile = 2EUR0EURC:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.configEUR5EUR0EUR/configuration/system.serviceModel/extensions/behaviorExtensionsEURaddEURname="enableBizTalkHeaderInspector" type="Microsoft.IT.RelationshipManagement.Services.WcfExtensions.HeaderInspectorBehaviorElement, Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e2c282dc0883bc94"

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: WixDIFxAppExtension and MergeModules

2008-12-01T15:53:26Z

Hmm, that really surprises me. I thought that mergemod.dll was smarter than that. There are no differences on those rows where the merge conflicts happen? Hmm.

-----Original Message-----
From: Moradi, Ari [mailto:arastoo.moradi@...]
Sent: Thursday, November 06, 2008 11:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixDIFxAppExtension and MergeModules

Mergemod.dll doesn't like trying to merge rows with identical primary keys (even if they are really supposed to be the same thing. Here's some log output since you asked for it :)

I created my two merge modules, then I ran:
Orca.exe -f ProductFeature -m DriverMergeModule1.msm -l merge.log -c Test.msi

I checked Test.msi and merge.log and sure enough, DriverMergeModule1.msm was successfully merged.

Then I deleted merge.log and ran:
Orca.exe -f ProductFeature -m DriverMergeModule2.msm -l merge.log -c Test.msi

Here's some snippets from the merge.log:
Opened MSI Database: Test.msi
Opened Merge Module: DriverMergeModule2.msm
...
Merging Table: Binary
o Merging row: DIFxApp.dll.B913F2A8_9BB5_40E4_9D7E_2541BC55A38D
o Merging row: DIFxAppA.dll.B913F2A8_9BB5_40E4_9D7E_2541BC55A38D
...
Merging Table: CustomAction
o Merging row: MsiProcessDrivers
>> Error: Failed to merge Row: MsiProcessDrivers into Table: CustomAction
o Merging row: MsiInstallDrivers
>> Error: Failed to merge Row: MsiInstallDrivers into Table: CustomAction
o Merging row: MsiUninstallDrivers
>> Error: Failed to merge Row: MsiUninstallDrivers into Table: CustomAction
o Merging row: MsiRollbackInstall
>> Error: Failed to merge Row: MsiRollbackInstall into Table: CustomAction
o Merging row: MsiCleanupOnSuccess
>> Error: Failed to merge Row: MsiCleanupOnSuccess into Table: CustomAction
...
>> Error: Merge conflict in Database Table: `InstallExecuteSequence` - Action: `MsiProcessDrivers`
>> Error: Merge conflict in Database Table: `InstallExecuteSequence` - Action: `MsiCleanupOnSuccess`
>> Error: Merge conflict in Database Table: `CustomAction` & Module Table: `CustomAction` - Row(s): `MsiProcessDrivers`
>> Error: Merge conflict in Database Table: `CustomAction` & Module Table: `CustomAction` - Row(s): `MsiInstallDrivers`
>> Error: Merge conflict in Database Table: `CustomAction` & Module Table: `CustomAction` - Row(s): `MsiUninstallDrivers`
>> Error: Merge conflict in Database Table: `CustomAction` & Module Table: `CustomAction` - Row(s): `MsiRollbackInstall`
>> Error: Merge conflict in Database Table: `CustomAction` & Module Table: `CustomAction` - Row(s): `MsiCleanupOnSuccess`

Total merge conflicts: 7

Closed Merge Module.
> Warning: Changes were not saved to MSI Database.
Closed MSI Database.

-Ari

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: Thursday, November 06, 2008 1:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixDIFxAppExtension and MergeModules

If the rows are duplicate, I thought mergemod.dll would let them through. Is it more accurate to say that the DIFxApp actions Id's have been modularized and that is colliding?

Can you maybe share out a merge.log that shows the merge problems?

-----Original Message-----
From: Moradi, Ari [mailto:arastoo.moradi@...]
Sent: Thursday, November 06, 2008 11:16
To: wix-users@...
Subject: [WiX-users] WixDIFxAppExtension and MergeModules

Hi folks,

I'm having a problem with the WixDIFxAppExtension when I'm using it in merge modules, and I'm wondering if someone can offer me a simpler workaround than what I'm currently planning on doing :)

The problem is caused when we try to build two different merge modules using WIX (v3.0.4624.0) that include drivers and then include both those merge modules in one MSI.

Both merge module projects link with difxapp_<platform>.wixlib, which adds the DIFx custom actions in the merge module custom action table: MsiProcessDrivers, MsiInstallDrivers, etc.

When those two merge modules are then merged into the same MSI, we obviously get duplicate row errors and the merge fails.

My hope would really be that if WIX builds a merge module using WixDifxAppExtension, instead of adding the DIFx custom actions directly if it instead would add a ModuleDependency on the DIFxApp merge module. Then we could merge multiple merge modules that all depend on DIFxApp, and then the DIFxApp merge module would be merged in too to get the custom actions. But that's not what it does, so I'm looking for a workaround...

One option we have is to build wixlibs instead of merge modules, but since I'm not guaranteed that consumers of our merge modules are going to use WIX (they might be using InstallShield) that doesn't really work well for our team.

The other option I think I have is that instead of using WixDIFxAppExtension, I'll add a <CustomTable
Id="MsiProcessDrivers">... and "manually" add the rows I need to the table, and then add the Dependency on the DIFxApp merge module too. The problem here is that every merge module we create has to add the CustomTable, and we have to go look up the column definitions again, and then we have to look up the documentation to figure out the bit values we need to set in the Flags column. I'd like a way where we get to continue to use the nice xml schema and can still merge everything successfully.

I've also considered modifying the WIX DIFxAppExtension source to do what I want too... but my workaround is easy enough to do, and since I'm unfamiliar with the WIX source, I figure it's a lot faster for me to work around the problem for now.

Any other ideas?

Thanks,

-Ari

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Application Installation and Patching Survey for Windows

2008-12-01T15:15:02Z

The Windows SDK blog is asking:

How should installation and patching work in future versions of Windows?

<http://tinyurl.com/55uwr4>

--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>

Legalize Adulthood! <http://blogs.xmission.com/legalize/>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Permanent Component being removed on uninstall

2008-12-01T15:04:42Z

Verbose log file will explain why it is being uninstalled.

-----Original Message-----
From: Dylan Moline (Volt) [mailto:a-dylanm@...]
Sent: Monday, December 01, 2008 15:01
To: wix-users@...
Subject: [WiX-users] Permanent Component being removed on uninstall

Trying to create a registry key which is edited by an application, and keep the entire key after the program is uninstalled (incase it is re-installed, want the stored data to remain)

Here is the sample code. However, every time I install, it creates the proper key, but when I uninstall via ARP, it removes the entire key.

<Component Id="foo" Guid="xxx" Permanent="yes">
<Registry Action="createKey" Root="HKLM" Key="SOFTWARE\foo\blah"/>
</Component>

I've checked the package with ORCA, and it shows the component table with the attribute of 16, which should translate properly to "permanent".

Even if I manually go in an add a string/Dword, it still all gets removed on uninstall.

Am I missing something? (using wix 2)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Permanent Component being removed on uninstall

2008-12-01T15:01:08Z

Trying to create a registry key which is edited by an application, and keep the entire key after the program is uninstalled (incase it is re-installed, want the stored data to remain)

Here is the sample code. However, every time I install, it creates the proper key, but when I uninstall via ARP, it removes the entire key.

<Component Id="foo" Guid="xxx" Permanent="yes">
<Registry Action="createKey" Root="HKLM" Key="SOFTWARE\foo\blah"/>
</Component>

I've checked the package with ORCA, and it shows the component table with the attribute of 16, which should translate properly to "permanent".

Even if I manually go in an add a string/Dword, it still all gets removed on uninstall.

Am I missing something? (using wix 2)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Install Localisation

2008-12-01T14:43:16Z

Most people that are attempting to do what you are doing, care about their ProductCodes so they can tightly manage upgrades in the future.

-----Original Message-----
From: Neil Sleightholm [mailto:neil@...]
Sent: Monday, December 01, 2008 14:33
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I guess it is laziness on my part :-) I am just going to have to write
some code.

I just strikes me as a common requirement to generate a transform
without a different ProductCode - I guess that makes it a feature
request. May be it should be a torch change rather than light.

I'll look at that package code issue and see what I can find.

Neil

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: 01 December 2008 22:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. The PackageCode should be regenerated with every run of light. If
not, that would be a bad bug. There is no scope like you are asking
for. IMHO, if you want to manage your ProductCode then you should
manage your ProductCode. You could open a feature request if you want.

Nothing in you scenario is completely unexpected. Generating transforms
is complete supported. You'll need something to apply the transforms at
run time, presumably.

The bugs in the WiX toolset are being fixed, BTW.

-----Original Message-----
From: Neil Sleightholm [mailto:neil@...]
Sent: Monday, December 01, 2008 13:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. Is there any scope for making this optional or replacing
Product/@Id="*" on the first pass of light? The PackageCode is not
regenerated on every run of light, is this not the same?

I can't find any good documentation on Windows Installer localisation,
do you think I am doing the right thing to localise my install or is it
my approach that is floored.

Thanks

Neil

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: 01 December 2008 20:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

1. Don't know.

2. If you use Product/@Id="*" then it always generates a new
ProductCode. If you don't want that, don't use "*".

3. No. There are cases where you'll end up with a binary .wixout even
if you don't use -bf, especially around the use of CustomActions.

-----Original Message-----
From: Neil Sleightholm [mailto:neil@...]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
neil@...

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0. *Every* MSI should have a different PackageCode. Even two builds of
the same MSI.

1. You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2. The most efficient way I've seen this done is:

a. Link to ".wixout" files. This will get you everything but the final
localized build.

b. Use cab cache to minimize the number of cabinets rebuilt. If you
are really careful with your Media elements this can lead to huge
savings.

c. Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d. Use torch to build transforms from all of the MSIs.

There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts. This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong. It might be a bug. <smile/>

-----Original Message-----
From: Neil Sleightholm [mailto:neil@...]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.

I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1. Set the CAB file as not embedded as the files are the same for
all languages.

2. Run candle for wxs files

3. Run light against the wixobj files but specifying a different
culture each time I ran it

4. This creates an msi for each language with an external CAB
file.

This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.

Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.

Thanks

Neil

Neil Sleightholm
X2 Systems Limited
neil@... <mailto:neil@...>

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users

Re: Install Localisation

2008-12-01T14:33:22Z

I guess it is laziness on my part :-) I am just going to have to write
some code.

I just strikes me as a common requirement to generate a transform
without a different ProductCode - I guess that makes it a feature
request. May be it should be a torch change rather than light.

I'll look at that package code issue and see what I can find.

Neil

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: 01 December 2008 22:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. The PackageCode should be regenerated with every run of light. If
not, that would be a bad bug. There is no scope like you are asking
for. IMHO, if you want to manage your ProductCode then you should
manage your ProductCode. You could open a feature request if you want.

Nothing in you scenario is completely unexpected. Generating transforms
is complete supported. You'll need something to apply the transforms at
run time, presumably.

The bugs in the WiX toolset are being fixed, BTW.

-----Original Message-----
From: Neil Sleightholm [mailto:neil@...]
Sent: Monday, December 01, 2008 13:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. Is there any scope for making this optional or replacing
Product/@Id="*" on the first pass of light? The PackageCode is not
regenerated on every run of light, is this not the same?

I can't find any good documentation on Windows Installer localisation,
do you think I am doing the right thing to localise my install or is it
my approach that is floored.

Thanks

Neil

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: 01 December 2008 20:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

1. Don't know.

2. If you use Product/@Id="*" then it always generates a new
ProductCode. If you don't want that, don't use "*".

3. No. There are cases where you'll end up with a binary .wixout even
if you don't use -bf, especially around the use of CustomActions.

-----Original Message-----
From: Neil Sleightholm [mailto:neil@...]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
neil@...

-----Original Message-----
From: Rob Mensching [mailto:Rob.Mensching@...]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0. *Every* MSI should have a different PackageCode. Even two builds of
the same MSI.

1. You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2. The most efficient way I've seen this done is:

a. Link to ".wixout" files. This will get you everything but the final
localized build.

b. Use cab cache to minimize the number of cabinets rebuilt. If you
are really careful with your Media elements this can lead to huge
savings.

c. Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d. Use torch to build transforms from all of the MSIs.

There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts. This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong. It might be a bug. <smile/>

-----Original Message-----
From: Neil Sleightholm [mailto:neil@...]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.

I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1. Set the CAB file as not embedded as the files are the same for
all languages.

2. Run candle for wxs files

3. Run light against the wixobj files but specifying a different
culture each time I ran it

4. This creates an msi for each language with an external CAB
file.

This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.

Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.

Thanks

Neil

Neil Sleightholm
X2 Systems Limited
neil@... <mailto:neil@...>

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

From forum: wix-users