Re: [WiX-users] Deferred custom action creates directories in the installation directory
On 4/14/2010 11:07 AM, Dariel Marlow wrote: That's exactly why it is of concern; it doesn't remove the temp directory after running. The other is not a native-code custom action, both are managed. Probably one is run from an installed assembly and the other is in the Binary table? Please file a bug on the directory not getting deleted. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deferred custom action creates directories in the installation directory
On 4/13/2010 9:52 PM, Dariel Marlow wrote: I have another installer that is running with elevated privileges and its deferred custom actions are executing from the windows\installer directory. I can't find why one runs from the program files directory while the other runs from windows installer directory. Is there a setting or a way to specify? The other is probably a native-code custom action; MSI uses its own directory for temporary files. Is there a reason it matters where it runs from? DTF appears to always clean up the directories it creates. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deferred custom action creates directories in the installation directory
That's exactly why it is of concern; it doesn't remove the temp directory after running. The other is not a native-code custom action, both are managed. I'll investigate further as to why there are differences and see if I can narrow it down. -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Wednesday, April 14, 2010 7:56 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Deferred custom action creates directories in the installation directory On 4/13/2010 9:52 PM, Dariel Marlow wrote: I have another installer that is running with elevated privileges and its deferred custom actions are executing from the windows\installer directory. I can't find why one runs from the program files directory while the other runs from windows installer directory. Is there a setting or a way to specify? The other is probably a native-code custom action; MSI uses its own directory for temporary files. Is there a reason it matters where it runs from? DTF appears to always clean up the directories it creates. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Deferred custom action creates directories in the installation directory
When running the deferred custom action, a directory is created in the installation directory. The log files says that the custom action is being extracted to a temporary folder. Why is it not doing this in the typical temp directory? Here's the pertinent part of the log file: ... MSI (s) (0C:88) [16:06:37:787]: Generating random cookie. MSI (s) (0C:88) [16:06:37:787]: Created Custom Action Server with PID 3476 (0xD94). MSI (s) (0C:98) [16:06:37:819]: Running as a service. MSI (s) (0C:98) [16:06:37:819]: Hello, I'm your 32bit Elevated custom action server. SFXCA: Extracting custom action to temporary directory: C:\Program Files\Product\Product.CA.dll-3\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action Product.DeferredCustomActions! Product.DeferredCustomActions.CustomActions.PostInstall Product: Product event log source started to register event source. MSI (s) (0C:E8) [16:06:39:925]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=8411802) MSI (s) (0C:E8) [16:06:40:143]: User policy value 'DisableRollback' is 0 MSI (s) (0C:E8) [16:06:40:143]: Machine policy value 'DisableRollback' is 0 Action 16:06:40: RollbackCleanup. Removing backup files ... -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deferred custom action creates directories in the installation directory
On 4/13/2010 6:11 PM, Dariel Marlow wrote: When running the deferred custom action, a directory is created in the installation directory. The log files says that the custom action is being extracted to a temporary folder. Why is it not doing this in the typical temp directory? Security: It ensures that the CA DLL is run from an appropriately ACL'd directory, so a nonprivileged user can't overwrite a DLL that the MSI server runs with elevated privileges. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deferred custom action creates directories in the installation directory
I have another installer that is running with elevated privileges and its deferred custom actions are executing from the windows\installer directory. I can't find why one runs from the program files directory while the other runs from windows installer directory. Is there a setting or a way to specify? -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Tuesday, April 13, 2010 7:15 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Deferred custom action creates directories in the installation directory On 4/13/2010 6:11 PM, Dariel Marlow wrote: When running the deferred custom action, a directory is created in the installation directory. The log files says that the custom action is being extracted to a temporary folder. Why is it not doing this in the typical temp directory? Security: It ensures that the CA DLL is run from an appropriately ACL'd directory, so a nonprivileged user can't overwrite a DLL that the MSI server runs with elevated privileges. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
