I am trying to create a windows installer which will include both the application setup files as well as the setup file for the Postgresql Database(if not present in the installed system) with some ddl scripts which will run post installation.
Request you to please guide me on how should i go ahead with meeting the requirement.
WiX allows you to create installer bundles. This means you can package PostgreSQL and your application in a single installer and let it install PostgreSQL (and other prerequisites) before your application. Other installer solutions have similar capabilities.
Related
I am trying to deploy a WPF Project that uses MongoDB. I want to create a One-Click installation system for the client who does not have any idea about computers. I tried creating a batch file but the best it does is, it starts the MongoDB setup file. Is there any possible way, I can install MongoDB without using their installer and bundle it with my deployed project?
You can install mongoDB unattended on Windows.
Just use the msi installer like this
msiexec.exe /l*v mdbinstall.log /qb /i mongodb-win32-x86_64-2008plus-ssl-4.0.9-signed.msi
For more details check out their official documentation on this regard here
I'm coding a C# Console Application that connects to a database and runs some queries where my database Engine is Microsoft SQL Server 2016 and I code in Visual Studio 2015. I have already installed and activated InstallShield Limited Edition on my visual studio and I'm able to make an installation(setup) file for my C# Console Application.
I don't want to to install Sql Server on my customer's PC and attach the database to that manually, instead I want to give everything in an installation file that includes .Net framework 4.5 and my database. The first part(.Net Framework) is done by InstallShield easily, but I don't know how to attach my database to the installation file.
Please explain how to do this and if any other version of InstallShield(Express, Professional or Premier) is needed let me know and explain the steps in that version.
Note that I want to give the installation file to the customer and make every feature of the app function well after he/she installs the program without needing to do anything manually.
Sql server 2016 cannot be installed automatically as it needs to be configured by the user, he must set the instance names, permissions and so on, which makes it unusable for your scenario.
What you need to use is Sql Server LocalDB, this is a subset of Sql Server Express for your concrete scenario, something which can be installed without the need of configuration and capable of attaching a database file also without user interaction.
You can find information about LocalDB here, as you see it can be downloaded as a .msi, in this way you can add this msi to your installshield project and chain it (more info on how to chain an installer here), it will not ask to the user about complex configurations, just a simple installer. To download the .msi you get the sql server express installer on your development machine and instruct it to download media and select the LocalDB package, that will give you the .msi.
Finally you will add the database file as part of your project files, then you only need to specify on the connection string the path to the file.
I have completed my windows application. I have used SQL Server 2008 as database server. Now, I want to prepare an installation file for my project. The Installshield is not working either. Isn't there an alternative way to prepare the installation file?? Also, I've been running the database in windows authentication mode. As I have set my laptop name as the data source, will it work after making the installation file??? I need help. Can anyone get me out of this problem???
The preferred way to create installers is the Windows Installer Xml Toolset (Wix). There are a lot of tutorials on the net that will help you create your installer.
I created a WPF C# application and using entity framework to connect to an SQL database, and read write data to it.
My application have multiple library projects and the main project that contains the UI.
I want to build the application in order to sell it. I want to have something similar to a normal application, where you have a main exe executable and .dll diles that represent the other projects and libraries used.
I also need to have a setup file that will setup the application as normal applications do.
How can I do that?
Will I have to do something with the SQL database in order to build with the project or that is done automatically?
If you have VS2010 you can use VS2010 based "Setup and Deployment" project template to create a Setup project and chose any of the given type i.e. CAB with Setup.exe or MSI or web Deployment which is suitable for your distribution. The UI is as below:
You can also try 3 party Installation project i.e. InstallShield etc also.
For SQL DB there are separate ways to distribute the database. If you have SQL Express or SQL CE then you can package it and ship with main project as described here. However for SQL Server, you just need to create a database deployment script and documentation about your data base first and then package it with main distribution. Or it can be done separately.
I am trying to make the setup file of my appllication. i already made the deployment process and also been success to build the setup file as .msi file. but to run my application on other computer there need othe software to install like SQL server 2005 so that my database file can support on that system. also it need some other software to install. so i want to embed on my software the all necessary s/w and suppossed to install during installing my application. so i need to know what to do during deployment to attach these software.
what the solution for it in C#?
Usually you'll do this through your application's installer (ie, InstallShield, Inno-Setup, etc). Installers generally have the capability to launch other programs and/or incorporate other install scripts. Also, some installers will allow for hands-off installations (usually done with command-line switches), so that the install of the dependent program is seamless.