Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
I received a question from a customer about how to perform a sequential unattended install of the .NET Framework 2.0 redistributable package and SDK. I have written a couple of different posts in the past about the various command line parameters available for the .NET Framework 2.0 setup and some of the options for silent installs (for example, the posts here, here and here). However, I realized that I've been sort of scattering this information across multiple blog posts and not providing simple, easy to understand examples of real world scenarios like this unattended install, so I'm going to try to start addressing that with this post.
Here are example command lines you can use to perform unattended installations for the .NET Framework 2.0 redistributable and SDK.
These command lines will run the .NET Framework 2.0 redist and SDK setups in fully silent mode. The setup package will extract to a temporary location and installation will begin with no user interaction and no visible UI. The user will see no visible indication that setup is running.
Standard unattended installation
These command lines will run the .NET Framework 2.0 redist and SDK setups in standard unattended mode. The setup package will extract to a temporary location and installation will begin with no user interaction. A progress dialog will appear on the screen during installation, and it will disappear when setup is complete. Errors encountered during installation might pop up message boxes during installation if they occur.
Unattended installation with no cancel button available in the UI
These command lines will run the .NET Framework 2.0 redist and SDK setups in unattended mode with no cancel button. The behavior of setup is the same as with the command lines above except the cancel button will be hidden on the progress page during installation. This allows the user to know that a setup is in progress but prevent them from cancelling it (unless they kill the process in Task Manager).
Important notes to consider
Thanks for the post, is there any way we can suppress the reboot i am using this command line to suppress reboot dotnetfx.exe /q:a /c:"install /l /q /norestart" will it suppress the reboot?
Hi Anuj Mittal - The original version of the .NET Framework 2.0 does not require a /norestart switch. It should automatically suppress reboots if any are required, and it will return exit code 3010 if installation is successful and a reboot is required.
The .NET Framework 2.0 SP2 is a replacement for the original version of the .NET Framework 2.0, and it does require a /norestart switch. You can download the .NET Framework 2.0 SP2 from www.microsoft.com/.../details.aspx, and you can run it with the following command line switches to perform a silent install with reboots suppressed:
netfx20sp2_x86.exe /q /norestart