Using the Visual Studio Windows Installer Deployment Project Template, also known as Setup Project Template: this has been the 'standard' way to perform such task since Visual Studio 2002 and (officially) available up to Visual Studio 2010, which is the last VS version that came out before Mirosoft chose stop supporting it in 2012.

If you're using Visual Studio, there are mostly three ways to achieve such goal: Now, the question is: how can we pull it off? In other words, what's the best way to create these installer packages for the aforementioned ASP.NET projects in order to grant our end-users a decent user-friendly 'installing experience', possibly using the standard Windows Installer API? You click on it, it prompts you to accept the software license and/or EULA, then (if you accept) asks you to confirm the installation path where it will unpack the files, create the desktop/start menu shortcuts, and so on. Such need is usually handled by creating an installer package which would arguably have the form of either a MSI file (acronym for MicroSoft Installer) or a EXE file, just like any typical software application or tool you can download from the web.

NET Core Desktop App project (and so on), you most likely know that sooner or later you'll have to find a way to deploy your work to your end-users. If you're an ASP.NET developer working with client applications using either Windows Forms (aka WinForms) projects, WPF Projects, Windows Console applications, Windows Service projects and/or any. How you can use the open-source WiX toolset to create a MSI or Setup.exe installer package for your ASP.NET projects to ensure a smooth GUI-based install experience to your users.

Advanced installer visual studio 2019