Leaderboard

Description: The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more. Info: The .NET package will be slipstreamed as pre-installed OS: Windows 7 SP1 Notes: - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last. - Add main addon first before LangPack addon, to get ASP.NET service localization properly. - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later. Windows6.1-KB4019990-x64.msu Windows6.1-KB4019990-x86.msu .NET 4.8: .NET 4.7.2: Languages Codes Reference:

Each new hotfix rollup contain all previous updates, some of them are not even published last rollup have these KBs: KB2901983 KB2908383 KB2925382 KB2931368 KB2936388 KB2937676 KB2938782-v2 KB2954853-v2 KB2972107 KB2972216 KB2974336 KB2978128 KB2979578-v2 KB2996568 KB3009681 KB3011114 KB3018514 KB3022670

To better keep the Win Toolkit discussions together, as its capabilities have grown to include Windows 7, Windows 8.x, and beyond, Win Toolkit has been moved to it's own sub-forum in the WinCert Member Projects section. You can find it here - Win Toolkit. See you there! Cheers and Regards

1-14-2015 Add: 3031985 Rem: 2974335

Updated to IDM 6.22b1

Here is what I am talking about, this is slimmed based on your installer, I rebuilt common.cab and the embedded product.cab's in each MSI installer... Then finally I replaced the ones in the original installer with those I rebuilt Download: http://adf.ly/1713566/vboxrpck MD5: 8cdb56d006f1874fc318d1a09bfe1678 Size: 83.7 MB I hope you don't feel like I am stepping on your toes here, I of course will provide to you how I did this. Maybe you can use this to take your repacking skills a bit further Tools: http://xp.xpdnc.org/files/msi_vbs_examples.zip (Optional)https://dl.dropboxusercontent.com/u/56155351/Tools/MsiTran.Exe (Optional)https://dl.dropboxusercontent.com/u/56155351/Tools/vbox.7zMakeCab (comes with Windows)InstEdRestorator 2007 MSI Instructions: - Extract VirtualBox installer files <installer>.exe -extract -path .\- Edit the MSI to make slim or apply the MST with InstEd or MsiTran (Note: I also remove vc2k10 runtimes) MsiTran.exe -a <mst_name>.mst <x86_and_or_amd64>.msi- Do an admin install of both MSI's, now copy common.DDF into ANYONE of the admin install location and rebuild common.cab makecab.exe /f common.DDF- Do the same to rebuild product.cab's (use 32 DDF for x86 and 64 for amd64)- Now we will add the product.cab back into the MSI, you can use InstEd but I prefer WiStream.vbs <msi_name>.msi product.cab- With InstEd change the admin install MSI's Sumary Information from Admin External. Long filenames to Compressed. Long filenames, you can also use this VBS command WiSumInf.vbs <msi_name>.msi Words=2EXE Instructions:Now that we have both installers repacked with none of the stuff we removed, we need to add them back into the EXE... You can simply open the original VirtualBox installer EXE in Restorator 2007, copy the files from within Windows Explorer and paste them into the RCData BIN's, but I rather add them to a RES file, then apply the res file with Restorator because the EXE date does not change and you wont get those ugly shortcut icons that Restorator leaves behind - Open provided RES file with Restorator 2007 - In Windows Explorer copy (Ctrl+C) x86 MSI and paste (Ctrl+V) in RCData -> BIN_00 - Do the same for x64 MSI (BIN_01) and common.cab (BIN_02) and save RES - Now open VirtualBox installer with Resource Hacker, now choose Action -> Update all Resources (apply the RES file) - Save and you are DONE!!! Bonus: If you are wondering how to get the DDF, you can open the MSI in InstEd, go to Media, right click on CAB and choose Show ddf, I prefer to use WiMakCab.vbs <msi_name>.msi cabname /LIf I use WiMakCab.vbs I have to edit it a littleEdit: I just realized its easier for you to rebuild/embed the CAB's, just open your MSI in InstEd, go to Media, right click on CAB and choose Rebuild selected CAB Edit2: You can also save space if you remove the linux and os2 stuff from VBoxGuestAdditions.iso (28MB after removal)