Bundling .NET Desktop Runtime Prerequisites in Visual Studio Deployment Projects

Question

Bundling .NET Desktop Runtime Prerequisites in Visual Studio Deployment Projects

Anonymous

Good day! We're finalizing a proprietary WinForms utility for internal corporate distribution, but we've encountered a hurdle where target machines lack the necessary .NET Desktop Runtime environments. Instead of requiring our employees to manually fetch these dependencies from the web, I'm looking for a way to bundle the redistributable directly into our MSI or Setup.exe bootstrap. Could someone guide me through the configuration steps in Visual Studio to include these runtimes as mandatory prerequisites so the installer handles the deployment of the framework automatically during the initial setup?

0 comments

2 answers

Your answer

Answer 1

To have the .NET Desktop Runtime installed automatically with a WinForms app deployed via a Visual Studio installer (MSI/Setup.exe), configure prerequisites in the setup/installer project so the bootstrapper handles the runtime before your app installs.

For Visual Studio Installer Projects (vdproj) targeting .NET (WinForms/WPF):

Open the solution that contains both the WinForms project and the Setup project.
In Solution Explorer, select the Setup project (the .vdproj).
Open the Properties window for the Setup project.
Select the Prerequisites… button.
In the Prerequisites dialog:
- For a WinForms app, select .NET Desktop Runtime… (this is the appropriate prerequisite for WPF/WinForms apps; .NET Core Runtime… is for console apps).
Choose how the prerequisite is obtained:
- From the vendor’s site, or
- From the same location as the application (if the redistributable is packaged alongside your installer).
Build the Setup project.

The resulting bootstrapper (Setup.exe) will then:

Check for the required .NET Desktop Runtime on the target machine.
Download or install it (depending on the option chosen) before installing the WinForms application.

If more complex installation logic is required (for example, multiple chained prerequisites or custom logic), consider:

Using the WiX Toolset Visual Studio Extension to build MSI-based installers with explicit .NET prerequisites.
Using InstallShield integrated with Visual Studio to define .NET Framework/runtime dependencies.

These options allow building MSI/EXE installers that ensure the .NET runtime is present before the application is installed.

References:

Answer 2

Hi Jason,

You’ll want to configure your installer to act as a bootstrapper that checks for and installs the required .NET Desktop Runtime before your WinForms utility runs. In Visual Studio, this is done through the Setup Project’s Prerequisites dialog. Open your installer project, go to Project Properties, then click Prerequisites. From there, select the appropriate .NET Desktop Runtime version (for example, “.NET Desktop Runtime 6.0.x”) from the list. Visual Studio will then embed the bootstrapper logic into your MSI/Setup.exe so that during installation it checks the target machine, and if the runtime is missing, it automatically downloads and installs it.

If you want to avoid external downloads entirely, you can package the offline installer for the runtime alongside your setup files. Place the redistributable in the same output directory and configure the bootstrapper to use the “Download prerequisites from the same location as my application” option. This ensures the runtime installer is bundled and deployed locally without requiring internet access. Microsoft’s official documentation on Visual Studio bootstrapper packages confirms this is the supported method for distributing .NET runtimes internally.

If the above response helps answer your question, please hit "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Harry.