advanced-installer

I have created an Installation Package using Advanced Installer . How can I implement following features If I install a software, and then install a newer version of the same software A.msi,I want the older version to automatically get uninstalled and overwritten. 2.If the framework for eg framework 4.0 or 3.5 does not exist,it should give a message to user to download it from the right location. Please help Thanks 1) Its the default configuration in all projects you create with Advanced Installer, of course as long as you increase your product version. The next article has more details about

Can anyone give me some documentation link/tutorial which could help me create .exe windows installer for Java Web Application. I have a Java Web Project which runs on tomcat server and I want to run theproject on windows with a single click. So for the same I want to create .exe file which I could use as installer to run on any machine. I couldn't find any proper document to create .exe file with the use of popular installers like Install4J and Advanced Installer . Please let me know if somebody has document or any kind help is highly appreciable. Thanks in advance. According to my

I am looking for suggestions to an alternative setup application from Install Shield. We are currently using Install Shield and I have never been impressed with it. It's way too bulky and the scripting system sucks. Has anyone had any better luck with any of the other products like WiX, Inno Setup, NSIS or InstallAware, etc? I am not worried about the cost, but what I am looking for is a very lightweight, easy to use application to bundle up our .exe and about 20 support DLLs, registering a few, setting up some registry values and install help. Can anyone recommend something they are using? It

How do I avoid distributing sensitive information in my WiX / MSI by accident? I distributed a password, machine name or login credentials by accident with my MSI file. How do I best deal with this problem? After deployment my application connects erronously to my QA / UAT systems instead of my production systems - because of a faulty debugging construct in my setup's custom action code. How can I detect and avoid this? How do I avoid distribution such information in general? This is a Q/A-style question with the simplest possible approach to avoid spreading sensitive information via your MSI