How to build an install package without Visual Studio?

Visual Studio Community can build the app, but it doesn’t include a full installer designer by default. There are several supported ways to create an installer without needing Visual Studio Professional:

1. Use WiX Toolset with Visual Studio Community
   • Install the WiX Toolset Visual Studio 2022 Extension from the Marketplace.
   • This lets creation of an MSI-based installer package (MSI or EXE) for a Windows desktop app from within Visual Studio Community.
   • WiX is a command-line toolset, so the build can also be automated outside Visual Studio.
2. Use the Visual Studio Installer Projects extension
   • Install the Visual Studio Installer Projects extension.
   • This enables creation of Setup projects (.vdproj) that build MSI or EXE installer packages for the Windows Forms app.
   • This works with Visual Studio 2017 and later, including Community.
3. Use third-party installer tools (no Visual Studio required) These tools can wrap the existing EXE and dependencies into a proper installer:
   • Advanced Installer
     • GUI-based tool that can generate MSI and Windows app packages from existing projects.
     • Can import an existing installer or binaries and build an installer with only a few clicks.
   • InstallAware
     • Builds MSI, EXE, APPX, and other package types from a single source.
     • Can import existing setups (even without source) and convert them.
   • InstallShield
     • Creates MSI, EXE, APPX, and MSIX installers.
     • Can convert existing MSI projects to MSIX and supports multiple deployment scenarios.
   • PACE Suite
     • Can create MSI, patches (MSP), transforms (MST), App-V, and Windows app packages.
     • Useful if a full packaging environment is needed, including publishing to tools like Configuration Manager.
4. Use MakeAppx.exe / packaging API (advanced)
   • For advanced scenarios, the MakeAppx.exe tool or the Windows packaging API can be used to create an app package manually.
   • This is more low-level and typically used when building UWP/MSIX-style packages rather than classic MSI installers.

For a straightforward Windows Forms deployment from Visual Studio Community, the most direct options are:

• Install WiX Toolset Visual Studio Extension or Visual Studio Installer Projects extension and create an MSI/EXE setup project, or
• Use a third-party GUI installer tool (Advanced Installer, InstallAware, InstallShield, PACE Suite) to wrap the EXE and any required dependencies into an installer.

References:

• First look at deployment in Visual Studio
• Package a desktop app using third-party installers
• How to create an app package (C++)

You can create an installer without Visual Studio by using tools like Inno Setup or NSIS. They let you package your EXE along with all required dependencies.

Also, consider publishing your app as a self-contained build so it includes the .NET runtime and avoids missing dependency issues on the target machine.

Hi @Saga ,

Thank you for being one of our valued contributors on the platform — we truly appreciate your engagement and input.

Based on your description of the issue, your assumption that missing dependencies may be the root cause seems to be a step in the right direction. Since you already have Visual Studio Community installed on your device, I would recommend installing the Visual Studio Installer Projects extension This extension may help address issues related to:

• Missing .NET Framework 4.8 components
• Inconsistent Visual Studio installations
• Scenarios where the application works on one machine but fails on another

Given the information you’ve shared in your post, this appears to be one of the most straightforward approaches to resolving the issue. If the problem persists after trying this solution, please feel free to reach out — I’d be more than happy to assist you further. Additional details may be required to help identify a more accurate resolution if needed.

Once again, thank you for your contribution, as well as to everyone participating in this thread. Your collaboration helps make this platform a supportive and trusted community for all users.

Wishing you a great day ahead!

Use a standalone installer tool

The simplest and most practical option is Inno Setup. It does not require Visual Studio at all.

Basic workflow:

• Build your app in Visual Studio (Release mode)
• Collect your EXE and all output files from bin\Release
• Write a small script that defines what to install
• Compile the script into a setup EXE

Example minimal script:

[Setup]

This produces a proper installer that Wine can run.

If you want more control

Use NSIS. It is also standalone, but more scripting heavy. Good if you need custom install logic.

Thanks for the follow up... some answers to your questions:

@Viorel : I had not considered this option. I will give it a go and report back. Thanks!

@Castorix31 : There was no message at all. I double click on the icon and nothing happens. I suspect that I am missing a dependency, just not sure which one.

@RLWA32 : I am targeting .NET 4.8I submitted this question before a big trip and upon rereading, I left out an important issue. I am trying to run this app in Linux under Wine. From the information that I've seen, applications that are installed in this environment are installed through an installer, not by just copying the EXE file. I figured that I could resolve this by generating the install package.

Again, thanks for your suggestions and time. Saga