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[
<!-- this line was added by rxp eventing v2.0 service deliverable installer
-->
<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:[EMAIL PROTECTED]
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/[EMAIL
PROTECTED]"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@lists.sourceforge.net
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
