Re: [WiX-users] Invoke asp_regiis.exe
Simon Burgess wrote: Thanks Bob, do you have an idea of the syntax needed were I to do that as obviously here the value of one property is required for the DirectorySearch’s path So the DirectorySearch picks up the value from RegistrySearch as the start path. -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Invoke asp_regiis.exe
Thanks Bob, do you have an idea of the syntax needed were I to do that as obviously here the value of one property is required for the DirectorySearch’s path From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 07 October 2006 03:54 To: Simon Burgess Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Invoke asp_regiis.exe Simon Burgess wrote: I have seen a previous thread in the archives that suggests the following wix source for trying to run .NET’s asp_regiis.exe utility: Key="SOFTWARE\Microsoft\.NETFramework" Name="InstallRoot" Type="raw" /> Depth="1"> MinVersion=" 2.0.50727"/> MSI doesn't guarantee a particular order for evaluating AppSearch records (which is what *Search elements turn into). So if FindAspRegExe happens before FindFrameworkDir, it won't have a FRAMEWORKBASEPATH value to start from. I'd suggest nesting the DirectorySearch and FileSearch elements under RegistrySearch. -- sig://boBhttp://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Invoke asp_regiis.exe
Simon Burgess wrote: I have seen a previous thread in the archives that suggests the following wix source for trying to run .NET’s asp_regiis.exe utility: Key="SOFTWARE\Microsoft\.NETFramework" Name="InstallRoot" Type="raw" /> Depth="1"> MinVersion=" 2.0.50727"/> MSI doesn't guarantee a particular order for evaluating AppSearch records (which is what *Search elements turn into). So if FindAspRegExe happens before FindFrameworkDir, it won't have a FRAMEWORKBASEPATH value to start from. I'd suggest nesting the DirectorySearch and FileSearch elements under RegistrySearch. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Invoke asp_regiis.exe
I have seen a previous thread in the archives that suggests the following wix source for trying to run .NET’s asp_regiis.exe utility: Key="SOFTWARE\Microsoft\.NETFramework" Name="InstallRoot" Type="raw" /> Depth="1"> MinVersion=" 2.0.50727"/> Then build the command line in a property: Value=""[ASPNETREGPATH]" -ga [DOMAIN]\UA_Quotes" /> Define the action that runs the command line: DllEntry="CAQuietExec" Execute="deferred" Return="check"/> Then schedule both custom actions in InstallExecuteSequence ….. I schedule just after InstallInitialize, however when my msi runs, just FRAMEWORKBASEPATH is evaluated successfully, there is not even a mention of ASPNETREGPATH in the verbose log. At the point at which I think it is doing the FileSearch all I see is: MSI (c) (60:08) [10:14:41:482]: PROPERTY CHANGE: Adding FRAMEWORKBASEPATH property. Its value is 'C:\WINNT\Microsoft.NET\Framework\'. MSI (c) (60:08) [10:14:41:482]: Note: 1: 1325 2: aspnet_regiis.exe MSI (c) (60:08) [10:14:41:482]: Note: 1: 1325 2: aspnet_regiis.exe MSI (c) (60:08) [10:14:41:482]: Note: 1: 1325 2: aspnet_regiis.exe MSI (c) (60:08) [10:14:41:482]: Note: 1: 1325 2: aspnet_regiis.exe MSI (c) (60:08) [10:14:41:482]: Note: 1: 1325 2: aspnet_regiis.exe MSI (c) (60:08) [10:14:41:498]: Note: 1: 1325 2: aspnet_regiis.exe And when the AspNetAssign custom action runs I see: MSI (s) (38:F8) [09:49:09:180]: Executing op: CustomActionSchedule(Action=""> CONFIGWEBSITEASPNET,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData="[ASPNETREGPATH] aspnet_regiis.exe" -ga \UA_Quotes) Any ideas why there is no mention of ASPNETREGPATH in the msi’s log file and why the command line I need to execute isn’t getting the variables it requires to run successfully? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
