I just ran the .cmd and the msp's apply in seconds... surely this can't be right... I would expect something like that to take a while... So I can't see it did anything. I only populated the x64 client hotfix folder, and the cmd windows shows it runs each msp, but they take less than a second each to integrate...hmmm EDIT: I just populated the x86 client hotfix folder as well, ran the .cmd, and the cmd window reads "Applying Hotfix "" to netfx_Core_x64/x86", as it's supposed to, but it happens really quickly, and the netfx_Core .msi's stay the same size, like nothing happens.
Thats all the time it needs and the files are not stored in the MSI they are stored in the MZZ but those are not the ones used/updated...the only files that matter are the files that are in the sub folders \ProgramFilesFolder and \Windows
I screwed up; I didn't run the ApplyHotfixes.cmd in SoLoR's program after refreshing the hotfix folders' contents. NDP40-KB2468871.msp integrates perfectly. You must run this command whenever you subtract or add any updates to the hotfix folders. Then, when you run the msi's all is good.
Well, I don't understand how this is supposed to work at all... I just extracted the original net4 .exe, and the netfx_Core.mzz file is in there is IDENTICAL in size to the one I just supposedly updated... but Ricktendo you said not those files are used by actually the ones in the ProgramFilesFolder and the Windows folder are used. Well, the original installer does not have those folders in it, so how then do I know how to make all this into one installer? I just can't see anything change after running the .cmd either, literally not one file in there changes size or anything, so I don't understand what is going on at all.... I have no interest in installing from an open folder, I am only interested in making an installer that is updated. Sigh... if I knew how to do this I would have had this stuff uploaded so people can use it... why is no one doing this, seriously? Seems like the people who have the skills aren't interested, but the people that don't are... that doesn't help OK, I'm dumping this, taking me too much time and I don't know what the hell I'm supposed to do with this.
.mzz does _NOT_ get updated when you apply .net hotfixes... files in windows folder of .net gets updated and its installed from there...
Yes, it works for me now to install via the .msi's. Like you say, the .mzz does not change after updating with the .msp's, but what I was further looking into was making it all into a silent installer again, or maybe one for x86 and another one for x64. But what I'm finding is that the .exe gets huge because it needs to have the .mzz AND the ProgramFilesFolder and Windows folders there too, so the smallest I could get was still bigger than 100mb. So I don't understand how to make a reasonably sized updates net4 installer out of it all. I tried dividing up 64 and 86 files and make exe's for each, but then it was complaining about missing files so I'm not sure what to use and what not. But as far as installing from the open folder of your .7z package it is working fine now. Maybe the 1 .exe silent installer is not easy to do or gets to big, or otherwise surely someone would have put it up on the net somewhere by now...
It does not "need" the MZZ and setup stuff, you can delete them from the MSI if you know how to edit the installer Edit: MSI editing instructions -After integrating the MSP's open the MSI in InstEd MSI editor -Go to the 'Feature' table and delete following features: For netfx_core_*.msi: Installer_Setup_ddf, Netfx_SetupUtility, MSICache_Core_*, F_Installer_IndentityARP (redundant uninstall entries), Netfx_NetFxRepair and MSUCache_Core_* For netfx_extended_*.msi: Installer_Setup_ddf, Netfx_SetupUtility, MSICache_Extended_* and F_Installer_IndentityARP (redundant uninstall entries) -Because we removed Setup.exe and its uninstall entries, we have to unhide the uninstall entries for the MSI...we do this by going to the 'Property' table and delete the ARPSYSTEMCOMPONENT. I also add (but you dont have to because SoLoR applied the MST from Aaron Stebner) EXTUI with a value of 1 in the Property table to enable direct MSI install -Save and do another admin install (uniextract to subdir) and you will see all the setup crap left behind
Thanks Rick, I'm slowly but surely getting a grip on all this (currently I'm playing with the sfx files, replacing icons, editing the version info, etc. I did the admin install and was left with only the needed files, great. It took me a bit to understand what you were saying there, but now I understand better. The patched mst files were a great help, thank you for those, or I don't know if I could have done it. I dl'd several free msi editors and they don't have the features as you mention for Installshield, so I was having a hard time at first trying to find what I was supposed to delete. I'll let you know once I got a functional installer, but it's fun so far working at it EDIT: OK, I got it to work, I now have a 40mb NET4 (v4.0.30320) Client x64 silent installer Thanks for your patience, and those videos you made really helped a lot. I'm gonna try to make a x86 version too (hope I don't need to be on x86 OS to do so...?)
You know what, I had not realized but InstEd gets the job done. I updated the above instructions so if you want to you can edit the installer manually with InstEd
Cool... I just made a NET4 x86 silent installer too, and it's only 28mb! This is GREAT man, thank you for all your help on this!!! I need to do a real world test install with this x86 on a x86 machine, I'll do that now but everything looks really good. EDIT: real world tests pass, looks like we got ourselves working silent installer of the latest net4
Thanks for the info, but I'm not sure what the latest is on that site you referred to, there are so many files and I don't know which one I need. Could you provide a direct link to the files I would need to update for the LZMA2 / x64 support? I used My Silent Switch Builder for both of the installers, but I did not try to make one single installer that handles both x64 and x86. Is that what you were referring to? I would like to make an dual-arch one too. I did not use SFX Builder for the above 2 installers. Before watching your 3d video tutorial I already got the installers to work so I did not get to the last video yet But I think that one deals with SFX Builder, right? I will look into that too, thanks.
No i dont go into sfx builder 140 is the latest stable and 150 is alpha, to dl the version you want go to Code: /tags/<version_number>/bin/<archive>.7z In it you will find a bunch of 7zsd*.sfx, I reccomend the LZMA2 or the ALL flavors (they both supprot LZMA 1+2) Now for the multi arch installer I suggest you use a cmd script to call the installers, there is a variable build into windows called %PROCESSOR_ARCHITECTURE% (translates to x86 or amd64), if you zip both the x86 and x64 MSI installers in the same archive (this is good because they share files in common resulting in a smaller footprint) and rename the x64 MSI to say amd64 and use this in your cmd Code: start /wait netfx_core_%PROCESSOR_ARCHITECTURE%.msi So whatever architecture pc you launch it from, the correct MSI will be called Your config.txt would go like this Code: ;!@Install@!UTF-8! RunProgram="hidcon:<name_of_cmd>.cmd" GUIMode="2" ;!@InstallEnd@! hidcon: will hide the cmd window Edit: try this in config.txt without the need for a .cmd, it might also work (you can do as many RunPorgrams as you like, here is how you do a full version) Code: ;!@Install@!UTF-8! RunProgram="netfx_core_%PROCESSOR_ARCHITECTURE%.msi" RunProgram="netfx_extended_%PROCESSOR_ARCHITECTURE%.msi" GUIMode="2" ;!@InstallEnd@!
as well here is another approach with 7zsd.sfx if %PROCESSOR_ARCHITECTURE% is not used or the filenames ;!@Install@!UTF-8! RunProgram="x86:filenameOfx86installer.exe" RunProgram="x64:filenameOfx64installer.exe" GUIMode="2" ;!@InstallEnd@!
Niiiice, I did not know that feature @Trinket, this is what user_hidden is talking about (make sure you use a updated .sfx, older one may not suppor this feature) Code: ;!@Install@!UTF-8! RunProgram="x86:netfx_core_x86.msi" RunProgram="x86:netfx_extended_x86.msi" RunProgram="x64:netfx_core_x64.msi" RunProgram="x64:netfx_extended_x64.msi" GUIMode="2" ;!@InstallEnd@!
Nice, thanks for that! As for the 7zsd.sfx files, I downloaded the latest versions, but like you say there a bunch in there. I notice there is a ALL and a All64... now, do I place both arch versions of these in the SilentSwitchMaker folder, or how does this work? As I was able to make the 64-bit NET4 without a 64sfx I was wondering what it's use is...
No issues you only need one, if you want to make a installer that supports both arch's use any of the x86's. If youre installer is only for x64 you can (but you dont have to) use the x64 What happens is the 7zsd.sfx + config.txt + <archive>.7z are all combined into ONE SINGLE EXE file...The 7z contains the files, the SFX is what is able to extract the files and the TXT contains the instructions