I don't think you are allowed to suppress the .NEt EULA dialog, as Christopher Painter recently discussed in this blog: http://blog.deploymentengineering.com/2007/03/silently-installing-net-framwork-legal.html
-- Stefan Krueger Microsoft Windows Installer MVP Please post your questions in the newsgroup or vist one of these web sites: Windows Installer FAQ http://www.msifaq.com - http://www.msifaq.de InstallSite - Resources for Setup Developers http://www.installsite.org http://www.installsite.de (GERMAN) "Thomas Bjørnsen" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] Hi again. Yesterday i switched our project over to Wix3.0/Votive 3.0 to get the MSBuild feature and get a boostrapper going from an example a kind individual posted here <ItemGroup> <BootstrapperItem Include="Microsoft.Net.Framework.2.0"> <ProductName>Microsoft .NET Framework 2.0</ProductName> </BootstrapperItem> <BootstrapperItem Include="{511DAC48-6CBB-43a3-A64D-0182F2A9EBC2}"> <ProductName>Microsoft .NET Framework 3.0</ProductName> </BootstrapperItem> </ItemGroup> <Target Name="GenerateBootstrapper"> <GenerateBootstrapper ApplicationName="My Application" ApplicationFile="$(TargetFileName)" BootstrapperItems="@(BootstrapperItem)" ComponentsLocation="HomeSite" OutputPath="$(OutputPath)" Culture="en-US" /> </Target> <Import Project="$(WixToolPath)\Wix.targets" /> <PropertyGroup> <BuildDependsOn> PrepareForBuild; Compile; Link; GenerateBootstrapper </BuildDependsOn> </PropertyGroup> Problem is, when launching the user has to accept/not accept installing NET 2.0, we do not want the users to have this option, we want a forced install of NET if this is possible. Anyway I can edit/create an addendum to the above XML to allow for this? Second problem is MSM/Merge modules. Under directory tag: <Merge Id="Sp5.Msm" Language="1033" DiskId="1" SourceFile="redist\Sp5.Msm" /> <Merge Id=" Sp5CCInt.Msm" Language="1033" DiskId="1" SourceFile="redist\Sp5CCInt.Msm" /> <Merge Id="Sp5Intl.Msm" Language="1033" DiskId="1" SourceFile="redist\Sp5Intl.Msm" /> <Merge Id="Sp5itn.Msm" Language="1033" DiskId="1" SourceFile="redist\Sp5itn.Msm" /> <Merge Id="Sp5SR.Msm" Language="1033" DiskId="1" SourceFile="redist\Sp5SR.Msm" /> <Merge Id="Sp5TTInt.Msm" Language="1033" DiskId="1" SourceFile="redist\Sp5TTInt.Msm" /> <Merge Id="Sp5TTIntXP.Msm" Language="1033" DiskId="1" SourceFile="redist\Sp5TTIntXP.Msm" /> <Merge Id="SpCommon.Msm" Language="1033" DiskId="1" SourceFile="redist\SpCommon.Msm" /> Under Feature tag: <MergeRef Id="Sp5.Msm" /> <MergeRef Id=" Sp5CCInt.Msm" /> <MergeRef Id="Sp5Intl.Msm" /> <MergeRef Id="Sp5itn.Msm" /> <MergeRef Id="Sp5SR.Msm" /> <MergeRef Id="Sp5TTInt.Msm " /> <MergeRef Id="Sp5TTIntXP.Msm" /> <MergeRef Id="SpCommon.Msm" /> Quite the number of warnings in the form of: light.exe : warning LGHT1076 : ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): Registry83.0880F209_45FA_42C5_92AE_5E620033E8EC_O.0880F209_45FA_42C5_92AE_5E620033E8EC Then comes a warning followed by an error light.exe : warning LGHT1076 : ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): Registry115.0880F209_45FA_42C5_92AE_5E620033E8EC_O.0880F209_45FA_42C5_92AE_5E620033E8EC light.exe : error LGHT0204 : ICE27: Action: 'DuplicateFiles' in InstallExecuteSequence table must come after the 'InstallFiles' action. Then several warnings with the following pattern: light.exe : warning LGHT1076 : ICE30: The target file 'Mary.SDF' might be installed in '[CommonFilesFolder]\SPEECH~1\MICROS~1\TTS\1033\' by two different conditionalized components on an SFN system: ' TTSData.A95D6CE6_C572_42AA_AA7B_BA92AFE9EA24' and 'TTSDataXP.8D1ED0D3_2DE5_40CD_83D4_76855A7380E8'. If the conditions are not mutually exclusive, this will break the component reference counting system. Two more errors: :\Documents and Settings\Thomas\Lokale innstillinger\Temp\8ptfefjo\Installasjonsskjelett.msi : error LGHT0204 : ICE32: Possible Mis-Aligned Foreign Keys Feature.1 = s38 Class.Feature_ = s32 C:\Documents and Settings\Thomas\Lokale innstillinger\Temp\8ptfefjo\Installasjonsskjelett.msi : error LGHT0204 : ICE32: Possible Mis-Aligned Foreign Keys Feature.1 = s38 TypeLib.Feature_ = s32 Then some more warnings: warning LGHT1076 : ICE46: Property 'WindowsFamily9X' referenced in column 'LaunchCondition'.'Description' of row 'VersionNT' differs from a defined property by case only. light.exe : warning LGHT1076 : ICE54: Component ' SapiCplHelpEng.0880F209_45FA_42C5_92AE_5E620033E8EC' uses file 'F718_speech.chm.0880F209_45FA_42C5_92AE_5E620033E8EC' as its KeyPath, but the file's version is provided by the file 'F595_sapi.cpl.0880F209_45FA_42C5_92AE_5E620033E8EC'. light.exe : warning LGHT1076 : ICE54: Component 'SapiCplHelpJpn.0880F209_45FA_42C5_92AE_5E620033E8EC' uses file 'F748_speech.chm.0880F209_45FA_42C5_92AE_5E620033E8EC' as its KeyPath, but the file's version is provided by the file 'F595_sapi.cpl.0880F209_45FA_42C5_92AE_5E620033E8EC'. light.exe : warning LGHT1076 : ICE54: Component 'SapiCplHelpChs.0880F209_45FA_42C5_92AE_5E620033E8EC' uses file 'F778_speech.chm.0880F209_45FA_42C5_92AE_5E620033E8EC' as its KeyPath, but the file's version is provided by the file 'F595_sapi.cpl.0880F209_45FA_42C5_92AE_5E620033E8EC'. light.exe : warning LGHT1076 : ICE54: Component 'LexData.FBA4D445_9B9B_4C21_8775_7D876C037CAE' uses file 'F375_lsr1033.lxa.FBA4D445_9B9B_4C21_8775_7D876C037CAE' as its KeyPath, but the file's version is provided by the file 'F428_spsrxui.dll.FBA4D445_9B9B_4C21_8775_7D876C037CAE'. light.exe : warning LGHT1076 : ICE54: Component 'SRData.FBA4D445_9B9B_4C21_8775_7D876C037CAE' uses file 'F390_AF031033.am.FBA4D445_9B9B_4C21_8775_7D876C037CAE' as its KeyPath, but the file's version is provided by the file 'F428_spsrxui.dll.FBA4D445_9B9B_4C21_8775_7D876C037CAE'. light.exe : warning LGHT1076 : ICE54: Component 'DictData.FBA4D445_9B9B_4C21_8775_7D876C037CAE' uses file 'F479_l1033.dlm.FBA4D445_9B9B_4C21_8775_7D876C037CAE' as its KeyPath, but the file's version is provided by the file 'F428_spsrxui.dll.FBA4D445_9B9B_4C21_8775_7D876C037CAE'. warning LGHT1076 : ICE66: Complete functionality of the MsiAssembly table is only available with Windows Installer version 1.5. Your schema is 100. warning LGHT1076 : ICE66: Complete functionality of the MsiAssemblyName table is only available with Windows Installer version 1.5. Your schema is 100. warning LGHT1076 : ICE66: Complete functionality of the MsiFileHash table is only available with Windows Installer version 1.5. Your schema is 100. warning LGHT1076 : ICE66: Complete functionality of the Class table is only available with Windows Installer version 1.1. Your schema is 100. The only real issues here I would assume are the errors created by including the MSM files. I could ofcourse go backto Wix 2.0 and write our own bootloader just for installing dotnetfx.exe but Wix3.0 seems quite nice and I'd like to stick with the MSBuild setup. So what exactly are causing these errors/warnings and what needs to be fixed (Yes I know it's a rather vague question). Sincerely -Thomas ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
