Create setup exe file C# with Microsoft Visual Studio 2015 Installer Projects (1)
Why Stack Overflow recommends it
Stack Overflow users link it when someone needs a quick walkthrough for packaging a C# app into an installer with Visual Studio Installer Projects.
Recommended by 1 people across 1 different months, 2016 to 2018.
What it is
A short screencast showing how to install the Visual Studio 2015 Installer Projects extension and use it to build a setup.exe for a C# application. It is part one of a two-part series by the channel Thanh Ly.
What people said
Recommends Philipp Marquardt · 2018-10 · Stack Overflow · on “Find program using Cortana/Search bar in C#”
If you don't want to type the .exe you can add an installer project to your program and install your program. Assuming you are using Visual Studio you can install the project here [LINK] . Note that this is the installer project for Visual Studio 2017. Here [this video] is a video on how to set up this installer. After you have build it, you can simple right click on it and install your program.
Cites David · 2016-10 · Stack Overflow · on “Visual Studio Installer Projects including too many DLLs?”
I am attempting to use Visual Studio Installer Projects to make an installer for my app. I am using Visual Studio 2015, and my app is built using WPF and .NET 4.5. I was following this general tutorial on how to make a Visual Studio Installer Project: [this video] When I include the "primary output" of each of my projects in the installer, it goes out and identifies the dependencies of these projects and includes them as files that need to be in the installer. I am puzzled, however, because it even seems to be including several standard "system" .NET DLL files, as you can see in this image below: [LINK] I tried building it, and then running the installer that it builds, and sure enough it install
Cites Laki · 2017-05 · Stack Overflow · on “Unable to Load SQLite.Interop.dll”
Thank you for answering. It gave me an idea how to workaround this. I copied x86 and x 64 folders to the output folder but then I bumped to the new issue - my config file had a different computed hash than specified in manifest. I decided to got away from publishing and decided for another option - to create setup file ( [this video] ). Once the setup was created and application was installed, I manually copied x86 and x64 folders to the application folder (where the application was installed). The final step was to set up a new path to the SQLite database in config file of the application.