To my knowledge, there are 2 ways to install dotnet 3.5 SP1
1 easy way using the command %INST%\dotnetfx35.exe /q /norestart.
And a bit more complicated way by extracting all msi's and creating an administrative install point.
Both are described here.

From a simplicity point of view if prefer the first option, but does it have any disadvantages in comparison with using the command line dotnetfx35.exe /q /norestart ?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I had success w/ extracting the files from the Microsoft file I downloaded, which I think was called dotnetfx35.exe, then using this command line:

%TEMP%\dotNet35SP1\setup.exe /qb /norestart

We then pushed it out to our users via SCCM.
I reckon it wouldn't be that much more difficult to make an admin install point; kind of depends on your environment as to how you achieve the end result of what you're trying to accomplish.
Answered 03/26/2010 by: RonW
Green Belt

Please log in to comment
The EXE extracts and executes the MSIs in exactly the same way as you would so there is a minor time penalty while they get extracted. That's it.
Answered 03/27/2010 by: VBScab
Red Belt

Please log in to comment