Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I have to create an installation file for ActiveX components. This ActiveX components will be downloaded as an *.exe installer file, executing this installer file will install the required ActiveX components on the user's PC.
To create such an installation file I came across two installer software -
Install Shield
NSIS (Nullsoft Scriptable Install System)
So which of the above option is preferable or any other options?
The only thing InstallShield has going for it is its IDE. And as it turns out, it works decently well for very basic installers when you don't need to write a line of code. However, when you need to create custom tasks and get into InstallShield's scripting language, it's a very clunky and unpleasant experience.
In terms of reliability, flexibility, speed, and size, NSIS is far superior to InstallShield. I know it's a bold claim. But you can read about my install system saga here and what led me to NSIS... http://swortham.blogspot.com/2008/02/nsis-another-gem-from-nullsoft.html
In visual studio, you can also create an installer project for your Active X which uses the windows installer.
InstallShield is superior to NSIS. However, because NSIS is free and enough for your needs, I recommend using it.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I have a few questions about approach for installation of Julia.
1) Julia installation then Atom.
2) JuliaPro installation.
Both approaches seem to result in having Julia on Atom Editor. Juno seems to come along with installation process and first run.
What would be big difference between two approaches? Does JuliaPro include extra packages that are preinstalled?
What might be disadvantages for not using JuliaPro?
Many thanks in advance.
JuliaPro comes with a lot of packages installed. Juno through its normal installation comes bare, but you can add the packages with Pkg.add. JuliaPro has an easy download for MKL-support and easy GPL-free versions, but with standard Julia it requires building from source. JuliaPro has a version with enterprise support, while standard Julia does not. Basically, if you want an easy installation with a bunch of standard stuff or have some enterprise needs, then JuliaPro can be a good option. I personally prefer the freedom of the standard installation.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to know the internal details. How registries are changed? How after installation ,Programs and Features is able to detect uninstall file for uninstall? How files are created. It will be better if you can give some example please.
please refer to : https://www.raymond.cc/blog/tracking-registry-and-files-changes-when-installing-software-in-windows/
above will give : to Track Registry and File Changes by Comparing Before and After Snapshots
About MSI :MSI is an installer package file format used by Windows. Its name comes from the program’s original title, Microsoft Installer, which has since changed to Windows Installer. MSI files are used for installation, storage, and removal of programs. The files are contained in a package, which is used with the program’s client-side installer service, an .EXE file, to open and install the program.
u can check the previous question asked in stackoverflow what happens in the registry when installing with an MSI in Windows 7?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I have tried to build a MSI package for my Windows Service with WiX for a couple of days but have big problems to get it the way I need.
The documentation is very bad and then XML structure just dont feels structured. I really don't see how they could have been doing a worse job at version 3.6.
I dont want to invest all my time in the MSI package, instead I need my time in dev of the main application.
So the questions is, what MSI builder should I use If I need:
Set app.config settings during installation
Install Windows Service
Start Windows Service
Simple install/uninstall
Thats really all I need
WiX can do all those things fairly easily (I have applications that do that and some that I use WiX to install). Problem is you have to have a pretty good understanding of Windows Installer to use WiX, as it does not really hide any of the detail from you.
The obviously alternative is InstallShield (They have a LE version that comes with VS2012 apparently, using VS2012 but not that) and Express is relatively reasonably priced.
You also may want to check out InstallAware, but I have not had good experiences with them personally when I have looked at them.
I have also been told that Advanced Installer is usable, though I have not used it myself personally.
A list and description of other installation products as well as Wix: What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc
And a link to some Wix quick-start suggestions (similar articles):
Wix generate single component id for entire tree
WiX Quick Start Tips
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
Part of our business includes providing a (windows) desktop machine with a pile of Data Acquisition Cards and associated software all set up and working for our customers.
Right now, we package up all our software, dependencies, drivers, etc and a pile of bat scripts, and this is our "install tool". Our production staff run the scripts (in order), choosing options as required and they eventually get the machine configured and tested.
The process isn't great - it's a bit buggy and really should just be a lot easier.
It's occurred to me that there must be an installer technology out there that we can use to replace our bat scripting. Does anyone know of something we could use?
It should:
Be able to install multiple pieces of software (ie run their installers with all default options on).
Be able to have some scripting/customization ability, because we'd want to be able to recreate some of the things our .bat scripts do.
Preferably provide some UI - ie click through installations screens with options.
Thanks in advance!
In the end we have gone with Wix - Installshield looked great - but... in the end it was just calling a whole pile of custom build scripts.
Wix has a high learning curve, but is more like what we need.
There are many installers tools, and different people prefer different tools. You won't find the best one, because some tools fit for one tasks more than others, some expensive, some really bad and expensive and so on.
But in your case, I can recommend use Windows Installer technology and InstallShield tool for it, base on my experience. It has a lot of possibilities to create great and powerful installers. With help of Windows Installer and own InstallShield features.
Also all your requirements could be done with InstallShield.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
We distribute an application that runs only on Window's machines (XP and up). I have been distributing by building an exe with WINRAR that has generally worked well but I have run into a problem as we move to support Vista and Win7 in that the application path is going to be dependent on the OS. So I either have to build an OS dependent WINRAR exe or join the modern age and use an installer.
I have scanned the websites of a couple of the installers for sale and the open source ones but since I have limited programming knowledge I am a bit overwhelmed by the choices.
It could be that the correct answer is that because we are not making any registry changes any of the installers will do.
From your description, the install process of your application is simple: just copy the files. In this case, any install tool would do its job. You can try the following:
Inno Setup
NSIS (Nullsoft Scriptable Install System)
WiX Toolset
The first two are easier to learn. WiX creates Windows Installer packages and has a steep learning curve; although in your case you could merely follow the WiX Tutorial to build your setup package.
If your installation procedure is so simple that it does not require an install, users of your application may like if you just give them a zip package which they can extract to any directory. Of course, this depends on the target users. Anyway, it could be a good option in addition to install package.
Generally the key distinction is whether or not you want to deliver a .msi Windows Installer package or not. Corporates prefer that because it makes large scale deployment easier for them. But .msi packages are harder to create and have a steep learning curve.