Hmm, the original files from MSoft for .NET 1.0 and 1.1 self extract into two files. Each version
for .NET then is netfx.msi and netfx1.cab (two files) so I'd think the switches are different and one
must have the 'cab' files around to make it work.
QUOTE (ckislam @ Jul 26 2006, 04:42 PM)

I used this For dot Net Framework 1.1
CODE
@ECHO OFF
ECHO ( 1 von 4 ) Microsoft .NET Framework 1.1 is installing..
Start /Wait dotnetfx.exe /Q /C:"install.exe /Q"
ECHO ( 2 von 4 ) .Net Framework SP1 is installing..
Start /Wait dotnetsp1.exe /Q
ECHO ( 3 von 4 ) Update KB886903 is installing..
Start /Wait KB886903.exe /Q
ECHO ( 4 von 4 ) German Language pack is installing..
Start /Wait langpack.exe /Q /C:"inst.exe /Q"
ECHO Installtion erfolgreich Abgeschlossen.
EXIT
for dot net 2.0 the same switches are used
CODE
Start /Wait dotnetfx20.exe /Q /C:"install.exe /Q"
it works well
As for .NET v2.0, the file from MSoft is "dotnetfx.exe" and would work the way you said. If you extract
this file, then you get alot of 'eula' and 'res' files plus a few others along withe the netfx.msi, although
the 'cab' file is embedded and compressed within the 'msi' file. Trying to stick these other files into the
msi package like the way the cab file was done.
If one runs the "msi installer validation suite" that comes with ORCA, you'll see that each of the netfx.msi
files for all the various .NET versions have about 5-6 errors each with alot of warnings (mostly
string overflow errors). How, these .NET packages install without error is beyond me!
I'm trying to update each of the msi files with the corresponding ".msp" patch file that MSoft provides.
They patch the msi ok, but the errors still exist and of course now, the .NET framework versions
won't install now......
Now trying to figure out how to repair them.
The other way is through the AIP (Administration install point) with the patches. Everything installs,
but if one has to reinstall or do a repair of the .NET packages, the directories used are where the
AIP is at, and not the default directories that came with the .NET software. Thus, I have to keep the
AIP files around to do reinstalls and repairs. I'd like to get rid of it. Thus, I'm looking into how to
fix the original 'msi' files and how to put all files and patches in only one file (the msi file) for each .NET version.
I can create a patched 'msi' file with ORCA, but the same problems mentioned above about the original
errors occurs, plus new ones due to the patches occur. To get ORCA to create the 'msi' file, one has to trick
ORCA into doing this.