I have created a WPF app on Visual Studio 2015. I have created installer using WIX toolset. Now I need to add an external exe file into setup.
Please, let me know the way, How to add exe file into my installer package.
Related
I'm building a windows form in Visual Studio 2015, I'm trying to add font-awesome.sharp tools in my project. I've installed font-awesome.sharp using NuGet package manager but it doesn't add it to my tools menu.
I tried to find some .dll file for it but can't find the correct file. How can I do the installation?
you can find the dll file (FontAwesome.Sharp.dll) in (YourProjectFolder\packages\FontAwesome.Sharp.5.15.1\lib\net40)
I am trying to change the default installation directory of my projects when I publish them but I seem to have no choice over where the published setup.exe actually puts the program. It seems after setup.exe running and application installed, all the processed files are under the folder of C:\Users\{username}\AppData\Local\Apps\2.0\ (Something like that, I dont remember the exact directory as it is very long). This is not what i want as I installed the program in the C:\Program Files\ but all the log files go to the C:\Users\{username}\AppData\Local\Apps\2.0\. This is really really annoying.
The application I published is C# Windows Form Application
And I have looked through online and found that somebody suggested to create an MSI package for C# Windows Application Using a Visual Studio Setup Project instead of publishing the program:
Publish Windows form application how change the installation path
It is supposed that the above website can solve this problem. Are there any other suggestions to solve this redirection problem after publishing the C# Windows Form Application? Thank you.
When you use the Publish funtion in Visual Studio, you are creating click-once publication. This type of deployment has relatively fixed rules and not everything can be configured. It allways installs into an obfuscated folder under windows user profile. It is similar to the fact, that you cannot change location where windows-store modern apps are installed under Windows 8.1.
You can create MSI setup project for your app - but in Visual Studio 2012 this type of project is missing and it was re-introduced againg in Visuals Studio 2013. There you can specify install folder. You can also use Install Shield Lite with Visual Studio 2012.
You wrote:
This is not what i want as I installed the program in the C:\Program
Files\
It is not possible to install ClickOnce application using Publish button in Visual Studio into C:\Program Files\.
If you have just problem with the location of your log files, you need to specify a different folder within your application code. Make sure that user, who is running your app, has write access to that folder - it should be in some user's profile folder or in a public folder. Avoid %ProgramFiles% as a folder for your log files - it is not a good practice.
Instead of Application.StartupPath you should use path accessible to all users including non-admin, like:
Path.Combine(Environment.GetFolderPath(SpecialFolder.CommonApplicationData),"MyCompanyName")
You can use InstallShield to create installation wizards/Setup.
Here's the free version for Visual Studio
I am using Visual Studio 2013. I have a .NET application that is getting deployed via Visual Studio Setup Project. Right now I have the Primary Output of the application begin used in the setup project. I want to use the Dotfuscator tool to obfuscate my code and then used the dotfuscated output for my setup project. Can someone lead me in the right direction?
I have tried the following
1: On my application post-build event, pass my .xml configuration file from Dotfuscator to the Dotfuscator application. This created an obfuscated exe, but it was still deploying the regular exe with my setup project
On my application post-build event, pass my exe to the Dotfuscator command line tool with the community edition...it would create a obfuscated exe in the Dotfuscated folder and then copy it over to my Release folder. However, the setup project was still deploying the regular exe with my setup project.
Any suggestions?
Found the answer via another thread...I was not aware the Visual Studio Setup Project pulled the 'Primary Output' from the obj folder instead of the bin folder. I copied by obfuscated exe to the obj folder before the setup project was built and this worked.
Hi guys i have a c# project that i want to create an installer.I want the installer to do the following:
Copy all the files that my application is using to a user chosen path (copy the files to the chosen path).
Ask for a specific Path(my c# program requires Google Drive Application to be installed and need its path)
Create Folders and Text files in that Path.
Please help me guys thanks.
Project Setup & Install was dropped after Visual Studio 2010. You'll either have to go the WiX route, or if you have Visual Studio 2013, you can create an InstallShield Limited project. There are several alternatives as well, just do a search.
Here's a link to a page that gives a video walkthrough of how to create an application installer with InstallShield Limited from Visual Studio 2013:
http://learn.flexerasoftware.com/content/IS-EVAL-InstallShield-Limited-Edition-Visual-Studio
I am working on a C# application that currently has a simple WiX installer to generate an MSI file. This application requires prerequisite software (such as the .NET Framework 4) and I would like to build a WiX Bootstrapper that will install the prereqs before installing my MSI file. I know Visual Studio has a Bootstrapper project template that is capable of creating a WiX bootstrapper executable, however I am developing with SharpDevelop 4.3.
I am wondering if there is a way to create and compile a burn bundle into a bootstrapper executable without using Visual Studio?
To create a Burn based bootstrapper/chainer bundle, you only need WiX v3.6+. The Bundle element in a .wxs file is the place to start. It's just like the Product element in a .wxs file is the place to start a .msi file.
Visual Studio has a bootstrapper system but it has nothing to do with Burn.