Microsoft says: "Using PowerShell 2.0 with .NET Framework 4.0 is not supported. While it is possible to force PowerShell 2.0 to run with .NET Framework 4.0 using various mechanisms such as creating a config file for PowerShell or editing the registry, these mechanisms aren't supported and can have negative side effects on other PowerShell functionality such as PowerShell remoting and cmdlets with mixed-mode assemblies."
-- Nicolás 2013/10/8 Steven Ogilvie <steven.ogil...@titus.com>: > The installer is not blowing anything away... > > I have a custom action that first backs up any powershell.exe.config to .bak > (both x86/x64) then I try to copy over the modified version over it is set as > perm so it won't remove it > > Steve > > -----Original Message----- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: October-08-13 2:13 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Can't compile Install getting ICE30 error... > > The more I think about this the more I think the "right" way is to try to > modify the existing file (if it exists) using XmlFile/XmlConfig. If the file > doesn't exist, I would want to create an empty one and then have the custom > actions run to modify it. > > As an end user, I know I would be angry if I had a few other applications > which politely modified the config, and then had your installer blow it away. > > With that, I would have a bare minimum config file and a component condition > on it to only install if the file doesn't exist. > > -----Original Message----- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: Tuesday, October 08, 2013 1:04 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Can't compile Install getting ICE30 error... > > Well it compiles now but won't overwrite the file :( > > How do I force a file to be overwritten when it is a "system" file... > > I am adding .net 2.0 and 4.0 to the powershell.exe.config file so I can run a > powershell script that requires .NET 4.0 (i.e. on Windows 2008R2 server) > > Steve > > -----Original Message----- > From: John Cooper [mailto:jocoo...@jackhenry.com] > Sent: October-08-13 1:54 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Can't compile Install getting ICE30 error... > > It is. On my Server 2012 install, that is exactly how Windows place > PowerShell 3.0. I have both x86 and x64 versions installed. > > -- > John Merryweather Cooper > Build & Install Engineer -- ESA > Jack Henry & Associates, Inc.(r) > Shawnee Mission, KS 66227 > Office: 913-341-3434 x791011 > jocoo...@jackhenry.com > www.jackhenry.com > > > > > -----Original Message----- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: Tuesday, October 8, 2013 12:21 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Can't compile Install getting ICE30 error... > > Or install to a common location this file, and utilize the CopyFile element > to stick it in the destination based on bitness. I'm not 100% certain, but is > it not possible to have both X86 and X64 versions of powershell on the same > system? > > -----Original Message----- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: Tuesday, October 08, 2013 12:15 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Can't compile Install getting ICE30 error... > > Solved it... > > I created a customaction to populate a property with the powershell folder > > <CustomAction Id="CA_Set_PowerShellx86_Path" Directory="POWERSHELLX86_DIR" > Value="[POWERSHELLPATH_X86]"/> > <CustomAction Id="CA_Set_PowerShellx64_Path" > Directory="POWERSHELLX64_DIR" Value="[POWERSHELLPATH_X64]"/> > > I use the Directory "property" Directory="POWERSHELLX86_DIR" as the directory > for the component... > > Sigh.. > > Steve > > -----Original Message----- > From: StevenOgilvie [mailto:sogil...@msn.com] > Sent: October-08-13 1:05 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Can't compile Install getting ICE30 error... > > Hi guys, > > I am trying to install 1 file to 2 different locations by using 2 different > directory elements, 2 different component elements and 2 different file > elements. > > Before I do this I have a custom action that copies the powershell.exe.config > to powershell.exe.config.bak (I try both the system32 and the SysWOW64 > powershell folders. > > Here is my WIX code for the file copy.. > > <Property Id="POWERSHELLPATH_X86" Value="0"> > <RegistrySearch Id="Find_POWERSHELLPATH_x86" > Type="directory" > Root="HKLM" > > Key="SOFTWARE\Wow6432Node\Microsoft\PowerShell\1\PowerShellEngine" > Name="ApplicationBase" > Win64="no"/> > </Property> > <Property Id="POWERSHELLPATH_X64" Value="0"> > <RegistrySearch Id="Find_POWERSHELLPATH_x64" > Type="directory" > Root="HKLM" > Key="SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine" > Name="ApplicationBase" > Win64="yes"/> > </Property> > > <ComponentRef Id="cmp_PSConfig_System32"/> <ComponentRef > Id="cmp_PSConfig_SysWOW64"/> > > <Directory Id="TARGETDIR" Name="SourceDir"> > > <Directory Id="POWERSHELLPATH_X64" Name="PowerShell X64" DiskId="1"> > <Component Id="cmp_PSConfig_System32" > Guid="{BC51F641-03C1-4477-9976-F464A61A3921}" KeyPath="yes" Permanent="yes" > Shared="no"> > <File Id="file_PSConfig_System32" Name="powershell.exe.config" > Source="$(var.resourcePath)\powershell.exe.config" /> > </Component> > </Directory> > <Directory Id="POWERSHELLPATH_X86" Name="PowerShell x86" DiskId="1"> > <Component Id="cmp_PSConfig_SysWOW64" > Guid="{51F24D8C-FE09-4FEA-8F8D-5C645A3F9D40}" KeyPath="yes" Permanent="yes" > Shared="no"> > <File Id="file_PSConfig_SysWOW64" Name="powershell.exe.config" > Source="$(var.resourcePath)\powershell.exe.config" /> > </Component> > </Directory> > > here are the two errors: > > Error 13 ICE30: The target file 'j47lduzx.con|powershell.exe.config' is > installed in '0' by two different components on an LFN system: > 'cmp_PSConfig_System32' and 'cmp_PSConfig_SysWOW64'. This breaks component > reference counting. C:\Dev\Core > Technologies\Main\Setup\Services_Setup_x64\Product.wxs 290 1 > Services_Setup_x64 > Error 14 ICE30: The target file 'j47lduzx.con|powershell.exe.config' is > installed in '0' by two different components on an LFN system: > 'cmp_PSConfig_System32' and 'cmp_PSConfig_SysWOW64'. This breaks component > reference counting. C:\Dev\Core > Technologies\Main\Setup\Services_Setup_x64\Product.wxs 285 1 > Services_Setup_x64 > > > What the heck am I doing wrong? > > thanks, > > STeve > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
