I can't reproduce your results. Then:
- Are you using 20090315?
- Have you installed any 2.0 SP# version previously before running the script?
- What's the exact set of 1.1 hotfixes did yo use?
- Anything else you consider relevant.

Now it's OK!

It was probably some problem with my Windows! CCleaner corrected the errors!

I have some errors messages when i launch the script, and snmsynth di not create any files

'


In english it means

*this one change each time i launch the script
precedent version did not throw any errors.

Your problems are caused by your windows installation.

findstr is a native win command for win OSs since W2K. Why your system doesn't has it is a mistery for me, maybe you trimmed down your system in excess, or some problem occurs since you installed. If your system still runs find command I think you can safely subtitute all ocurrences of findstr command with find command in the script without changing anything else, check it first obviously.

About cscript, it could be the same issue as above. Seems you don't have installed windows scripting host.

To avoid the 3rd error with WIC open the task manager and kill pending tasks from unsuccesfull previous building process.

good tools! But about KB928416 and KB829019 in PTBR

I don't get it... you want 2.0 and 3.0 in pt-BR, what's the problem?

I dont quite understand : do you have all in one installer available from 1.1-3.5 with all SP's and hotfixes integrated?

In what whay is it different from silent installer addon from ryanvm forum?

I don't have AIO installer, I have a script that builds it if you want, and is different in a way that:
- You can split each framework in a single installer/add-on or merge the combination of them you want, allowing you to apply different install strategies, that could allow you to avoid Event Viewer errors, if you want.
- You can include the different langpacks for each framework you process, and absolutely all the hotfixes for each framework in a flexible way, ryanvm's doesnt integrate restricted ones and is not flexible.
- It hides all hotfixes and subcomponents useless entries in Add Remove Programs, ryanvm's only hides subcomponents.
- It accepts old framework versions in case you need it.
- In case you need it you can choose the 3.0 SP# subcomponents you want to process.
- You can build installers for W2K.
- Ryanvm's don't precompile assemblies, so it finish pending tasks after install finish, in spare times.
- You can avoid KB951847 in case you don't want to install all set 2.0 SP2+3.0 SP2+3.5 SP1, and you can make remove and install operations of each one to you liking, seamlessly.
- You can avoid KB928416 trying to install wrong 3.0 SP0 langpack for some languages.
- You can choose the switchless verbosity level of the install process and change them if you want with switches.
- It is compatible with HFSLIP.

And the pleasure of doing it yourself with a transparent process, of course.

Hi Strel! I tried the new version but in WU it keeps asking for KB928416 and it fails to install.

Updated again!

I though MS had fixed this issue. Thx bfc_xxx

I used the fix I had reserved based in mickmack' solution, and fix a couple of things more.

Thanks strel for your hard work on this .NET Framework mess! A real timesaver...
But please strel....add quotes to make the changes to the registry valid.
From line 315to

Sorry I should have tested it.

Fixed now!

Thx CEoCeo.
More than this. It needed !VARIABLES! for delayed expansion.

And there were 3 lines out of place in the previous version.

Thx strel for your quick fix!
Tested and working as intended now. The KB928416 struggle is finally over.

Have used this when on x32, but have since upgraded to x64 for learning.
Was wondering, would this work for x64?

I'm almost sure is not possible at this moment.
I don't have x64 machine to adapt it, but It's probably I can have access to one soon.

ok thanks, strel.
will wait with baited breath as found it really useful for x32 machine.

strel, in the "20090316b" version WU asking for KB829019 Pt-BR

Thank you Strel, with your updated version everything is fine.

Thanks for this

i have DFN11fr.exe DFN20SP2fr.exe DFN30SP2fr.exe and DFN35SP1fr.exe

how to integrate it to hfslip ?

thanks

Use HFSVCPACK folder for switchless installers.

I'm using HFSLIP and have .net 1.1 & 2 run at T13 via HFSVCPACK
.3 & 3.5 run via RUNONCEEX or HFGUIRUNONCE

Thanks for the fast reply, i test it ....

Ok let's say I want to install all .NET Framework versions 1.1-.3.5 with all SP's and hotfixes.

If I just use .cmd file to install , everything is installed properly (installation progress), but when I look after restart, it shows that e.g. SP's didnt install and some hotfixes, beacuse restart is required after installing main .NET package e.g. .NET 1.1 main package. SP's and some hotfixes show up as not being installed in add/remove section and on windows update (probly beacuse it uses same values for establishing that)

How did you address this issue - requirement of restarts, so that everything IS installed properly and displayed properly?

You're are taking as a fact something that is not real. This supposedly needed restarts doesn't take place when you installed .NET normally with ms original files, and doesn't happen with this installers. For your serenity, this method uses administrative install technique, that is something ms implements in its installer technollogy, .msi files, that is kind of a preinstall. This method is not inventing the wheel.

About hotfixes, with this script are not showed as installed, i.e not listed in Add Remove Programs, but are identified by MBSA and win/ms update system as installed. But as you can reach the building script code and/or installing script code, you can remove this feature in one of them manually to your liking.

And SNMsynth.cmd is not used to install but to start the SMNsynth installer(s)/add-on(s) building process.

Thanks very much for this excellent script

Thanks to Strel (and TC76 and all the people involved) for this useful tool.

I was trying to use only the .NET 1.1 part, and I got small pitfalls.

First, while my targets include Win2000 and Vista stations, I was building on XP64, which is seen as NT5.2 i.e. 2003 server (they share the same kernel). Even if I use WIN2K=YES in the .ini, the logic which discovers WIN2K3 according to the VER command operates, and then prevents the 1.1 installer to be built. The fix is obviously to check about the version only if there are no explicit settings in the .ini. See attached patch to this effect Click to view attachment (GNU unidiff, against the version 20090316b.)
I am guessing the setting WINXP=YES will do the job to build a 1.1 installer for Vista, but I do not have checked it yet.

Second, for bare bones W2k targets (SP4 w/o IE6, which only have 2.0 Windows Installer), the /passive and /quiet and /norestart switches are not acceptable. It took me quite more time to come with a acceptable patch , which doubles the %VERBOSITY% stuff with a %QSWITCH% (either qb or qn). It is still not perfect , since for example it enables the Cancel button (and I do not know what /passive does, but I guess it doesn't). Also I broadly replaced throughout the script, but an educated guess is taht .NET 2.0 might require Installer 3.x at least, thus making it moot. Anyway I attach it in case anyone is interested. Click to view attachment

Much more complex was the aim to have several 1.1 language packs (of course I am thinking about servers here, or MUI-enabled workstations). I succeded at manually building an installer which does that (by manually renaming the langpack.msi after their adminstrative installation), but I did not even try to enhance the script this way. Is there any interest?

Hey,

I assume that all the restricted hotfixes are multilanguage?

Something else:
.NET 3.5 full redistributable package (dotnetfx35.exe 197MB)
.NET 3.5 SP1 full redistributable (dotnetfx35.exe 231 MB)

Same file names, can't put them together in one directory withouth changing the name of 1 of them?

Or does .NET 3.5 SP1 full redistributable (dotnetfx35.exe 231 MB) include everything from .NET 3.5 full redistributable package (dotnetfx35.exe 197MB) ?

Are different SP# steps of the same #.# versions. Are incompatible.

I am trying to make an all in one of dotnet.

I downloaded everything except:

- .NET 3.5 full redistributable package (dotnetfx35.exe 197MB), contains 2.0 SP1, 3.0 SP1 and 3.5 frameworks. 3.# frameworks are not processed for W2K installer(s)/add-on(s).

- .NET 3.5 langpack (dotnetfx35langpack_x86XX.exe -- note it has the same filename as 3.5 SP1 langpack), contains 2.0 SP1, 3.0 SP1 and 3.5 framework langpacks. 3.# framework langpacks are not processed for W2K installer(s)/add-on(s).

-All the restricted hotfixes.

If i know make the installer , I wont get anything on MU?

Those are not last versions so you're going to see KB951847 as a high priority update (including in this case 3.5 SP1 redistributable (2.0 SP2+3.0 SP2+3.5 SP1)+ hotfixes + langpacks for these versions). KB951847 fix is not applied for these versions, it's only applied if you build updated installers.

Strel is there any way to install KB961118 unattended after .NET is installed since it cannot be slipstreamed with Silent .NET Maker??

No, the script handle .NET and its updates, this is a windows update, it's only mentioned for completeness.
But if you pretend to build an unattended windows set integrate it as you used to do; and if you're using the installers on a installed windows, then simply let update system do its job.

I think I can install AIO .NET from svcpack and then at first logon I can install KB961118 with "/Passive /NoRestart" switches. I'll try that later today.

I think I can install AIO .NET from svcpack and then at first logon I can install KB961118 with "/Passive /NoRestart" switches. I'll try that later today.
[/quote]


I have done this at Runonce and it works great. No updates needed afterwards!


------my RunOnceEx.cmd------
cmdow @ /HID
@echo off
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D "Installing Applications" /f

REG ADD %KEY%\005 /VE /D "Install all DotNET(s)" /f
REG ADD %KEY%\005 /V 1 /D "%systemdrive%\Temp\NETFXAIO.EXE" /f

REG ADD %KEY%\010 /VE /D "Install KB961118" /f
REG ADD %KEY%\010 /V 1 /D "%systemdrive%\Temp\KB961118.exe /q /n /z" /f

REG ADD %KEY%\055 /VE /D "Cleaning Up temp files!" /f
REG ADD %KEY%\055 /V 1 /D "%systemdrive%\Temp\cleanup.cmd" /f

EXIT

strel, KB829019 (Pt-BR) keeps showing in Windows Update.
Installation is ok.

Please, fix this.

Sorry if this question has been answered, but I don't understand all the information in this topic because I don't speak english.

I created the installers and I tried to install them using SVCPACK method, the problem is that it doesn't work and I don't know why. I added the installers this way:



When I excecute them after Windows installation they work perfectly. Any suggestions ???

2 Brazillian language users for .NET 2.0 SP#
Until I release a new version, to fix KB829019 showing in win/ms update, open a console and type this command: I fixed a typo error sorry.

2 hipo_loco
Have you copied the installers to ..\i386\SVCPACK folder?

A lot of thx for your fixes. I hadn't read your post until now, sorry. I'll review all this for the next version.
And:
- Yes, /passive don't show cancel button, at least for win installer 4.5.
- .NET 2.0 requires win installer 3.x
- The .ini file OS setting is only to define the target OS version for the installers bypassing default target that is host OS version from which they are built; so even if you change .ini file OS version setting and bypass in-script OS version checking, you cannot build installers for vista or 7 but from this versions for win2K/XP/2K3 x86.
- There's interest in having a script that cover all needs, at least mine.

Ok strel, tanx for the answer, will try the installation implementation of .NET using your method, it seems easy enough.

Yes, I copied the installers to SVCPACK folder.

Hi, I got something wrong, when i made NET 3.5 sp1 alone or pack ?
Net Framework 1.1 2.0 3.0 3.5 are installed

files in folder

_SNMsynth.ini
7za.exe
7zsd.sfx
dotnetfx.exe
dotnetfx35.exe
KB951847_FIX.mst
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
ndp20sp2-kb958481-x86.exe
ndp30sp2-kb958483-x86.exe
ndp35sp1-kb958484-x86.exe
SNMsynth.cmd

==============================
Processing .NET 3.5 SP1 installer...
Processing .NET 3.5 SP1 portion...
Processing NDP35SP1-KB958484-x86.exe...
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.

Creating .NET 3.5 SP1 silent installer...

Done!

Press any key to quit.
=============================

something is missing after NDP35SP1-KB958484-x86.exe
Thanks

You're not using the latest version 20090316b, isn't it?

Yes, i download all again, same error message. DNF 1, 2 ,3 ok but 3.5 error

dotnetfx35.exe 231mb

==============================
Processing .NET 3.5 SP1 installer...
Processing .NET 3.5 SP1 portion...
Processing NDP35SP1-KB958484-x86.exe...
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.

Creating .NET 3.5 SP1 silent installer...
Creating .NET 3.5 SP1 silent nLite add-on...

Done!

Press any key to quit.

=============================

I'm not getting your results and I'm pretty sure you're missing the version, check you're using SNMsynth.cmd last modified 16-03-2009 19:29.

This happen to me too. I'm using potuguse (portugal) language packs!

Check SNMsynth.cmd is last modified 16-03-2009 19:29. Are you using this version? If not, download again.

newbie here, nice to meet all of you.
@strel & all helping people: excelent work, thank you very much.

i have a problem similar to the reported in post 191 when creating an AIO:

==============================================================
Processing .NET 1.1 installer...
Processing NDP1.1sp1-KB867460-X86.exe...
Processing NDP1.1sp1-KB928366-X86.exe...
Processing langpack.exe...

Processing .NET 3.5 SP1 installer...
Processing .NET 2.0 SP2 portion...
Processing NDP20SP2-KB958481-x86.exe...
Processing .NET 3.0 SP2 portion...
Processing NDP30SP2-KB958483-x86.exe...
Processing .NET 3.5 SP1 portion...
Processing NDP35SP1-KB958484-x86.exe...
Processing dotnetfx35langpack_x86es.exe...
Processing .NET 2.0 SP2 language portion...
Processing .NET 3.0 SP2 language portion...
Processing .NET 3.5 SP1 language portion...
The system cannot find the file specified. (originaly it said: "El sistema no puede hallar la ruta especificada." in spanish)
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.

Creating merged .NET 1.1 es, .NET 2.0 SP2 es, .NET 3.0 SP2 es, .NET 3.5 SP1 es passive installer...
Creating .NET 1.1 es, .NET 2.0 SP2 es, .NET 3.0 SP2 es, .NET 3.5 SP1 es passive nLite add-on...

Done!
==============================================================

the script creates DNF11es20SP2es30SP2es35SP1es.7z of 59.5 Mb and after installed add/remove programs shows:

- .Net Framework 1.1 no size
- .Net Framework 1.1 Spanish Language Pack 2.99 Mb
- .Net Framework 2.0 Service Pack 2 183.00 Mb
- .Net Framework 2.0 Service Pack 2 Language Pack - ESN 6.21 Mb
- .Net Framework 3.0 Service Pack 2 169.00 Mb
- .Net Framework 3.0 Service Pack 2 Language Pack - ESN 22.75 Mb
- .Net Framework 3.5 SP1 38.13 Mb

although should appear something like "3.5 SP1 Language Pack - ESN" in the list above WU/MU doesn´t complain about any pack/addon missing.
since so many people works winth no problems or errors, am i doing something wrong???

my .ini:

===================
PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
PROCESS_LNG_DNF1=YES
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=YES
PROCESS_LNG_DNF35_DNF3=YES
PROCESS_LNG_DNF35_DNF35=YES
OUTPUT=ADDON
MERGE_FRAMEWORKS=YES
VERBOSITY=
COMPRESSION_RATIO=
===================

files in folder:

===================
dotnetfx.exe
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
langpack.exe
dotnetfx35.exe (231 Mb)
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
dotnetfx35langpack_x86es.exe (32.1 Mb)

7za.exe
7zsd.sfx
KB951847_FIX.mst
SNMsynth.cmd
_SNMsynth.ini
===================

and by the way, yes i have the latest version, modified 16-03-2009 19:29

any help will be appreciated.

EDIT:

OK, now that it's confirmed, I've got to tell you DON'T WORRY, those error messages only mean the unused 3.5 SP# installer locale files (very small size, and related only to 3.5 SP# install process messages, not to 3.5 SP# framework at all) are not being removed from installer including 3.5 SP#. This is a new feature of the latests script versions not working properly, but it's not a real problem for the installer.

2 egd
Check again, the langpack for 3.5 SP1 should be in the ARPrograms list, but not inmmediately after the .NET group.

Hello,

I've also encountered a warning of my AVG Free 8.5 after downloading your tool, but as said this should be a false positive. However, the affected file was send to AVG's Research Lab (via virus fault -> send to analysis) and here are the results:





Maybe you should try to contact AVG's technical support manually to solve this problem; my other machine running AntiVir Personal along with other scanners don't report anything. Apart from that, thank you for this .NET setup maker - much more comfortable then to use six MSI packages at T-13. ;)

As far as I know AVG would generate false positives on every .exe embedded on a file that has been compressed with UPX as the .exe embedded in this file. That kind of contact with AVG is suggested in the link you provide but should be done by an AVG license holder as stated in the contact link therein. All the info AVG needs is in this forum, so up to you.