slipstream .net

[ctpooon]

hi,

is there a way to slipstream .net using hfslip?

I have read through the forum and created a silent 1.1 .net installer using SNM

and create a silent 3.5 .net installing using winrar with a install.bat in the following

@echo off
title Microsoft .NET Framework 3.5
echo.
echo Installing Windows Installer 3.1...
start /wait WindowsInstaller-KB893803-v2-x86.exe /passive /norestart
echo.
echo Installing Microsoft .NET Framework 3.5...
start /wait dotnetfx35.exe /q:a /c:"setup.exe /q /norestart" /norestart

both installers have been tester on a normal xp and working fine.

then I put the .net3.5 installer into the HFGUIRUNONCE

and the .net11 installer into the HFSVCPACK and run the hfslip

However, the hfslip doesn't seen able install those 2 frameworks..

anyone know what I have done wrong?

thanks a lot for the help and have a good weekend

HFSLIP.zip

[johndoe74]

in one word, no!

up to this point in time, there's no known way to slipstream any version of .net framework into the windows setup. you have to install .net framework via switchless installers, .net 1.1 and 2 through hfsvcpack (t13) and .net 3 or 3.5 via guirunonce (first logon)

Edited December 1, 2007 by johndoe74

[ctpooon]

um.. how am I gonna install .net framework via switchless installers ?

I created a switchless .net1.1 and put it into hfsvpack

and

a switchless .net35 and put it into guirunonce

however, it doesn't seem like have been run by the system.

did i miss anything?

[johndoe74]

you are putting the correct file in the correct location, however, the switchless installers you made might not be working properly. you could try the switchless installers made by roguespear instead. you can download them here. you will have to register on the forums to access them.

Edited December 1, 2007 by johndoe74

[Tomcat76]

Is there a reason why you're letting HFSLIP slipstream Windows Installer 3.1 and then install it again in your .NET 3.5 silent installer? Remove Windows Installer from your .NET 3.5 package and try again.

I can't say anything on the switches for .NET 3.5 because I haven't tested it yet.