Hi, We use AI to distribute our flagship product which comes in standalone, server and client flavours. We use a single installer with a feature for each version. This is important as some customers can have more than one feature and they must be able to install in one process. We need the ability t...
Hi Cosmin, If you have two packages with the same Product Version and a different Product Code, the newer package will not automatically upgrade the older one. Although they may use the same installation folder, in the "Add or Remove Programs" applet in the Control Panel there will be two ...
Hi Cosmin, I'm afraid that this is not supported by Advanced Installer or by Windows Installer. A new version of the product needs to have a different Product Code and a higher version in order to automatically upgrade older versions. I don't belive this is true! As I've already said (and there is a...
Hi Cosmin, What would work best for us would be if there was a setting to make AI give a new Product Code to each build of the installer (even better if it could generate a new code for each build configuration). This would allow us to keep our installer version constant with our product version. As...
Hi Cosmin, Our installer uses x.x (although we have to use x.x.x with Active installer which isn't a major problem for us) but the software uses x.x.x.x so we cannon keep incrementing the installer version. My work around shows that the problem can be solved, it just leaves the possibility of error....
Hi Cosmin, This may be a deal breaker for us! Our software is released with major minor and build remaining constant for months at a time. The revision number is incremented for each indervidual build of our software. Our installers are released with the X.X version and this will stay the same for a...
Hi, We have been building our installation projects with InstallAware but are currently in the process of moving over to use Advanced Installer. InstallAware uses two guids to refer to an MSI; the product id and the revision id. This allows up to release more then one installer with the same version...
Hi Cosmin, I acheived the correct registration by manually adding the registry values as a shared component and using a property for the code base value. I set the code base property in the InstallInitialize using two custom actions; one action if feature A is installed and one action if feature B i...
Hi, We have to register a .Net assembly so it is recognised by COM. It is a non signed assembly so it is registered with its code base. Our software is split into versions that are installed as features (Standalone, Client or Server) as it is perfectly legitimate to have more than on version on a co...
Hi Cosmin, Do you have a rough time frame on when we will see this feature? It would be very useful in our deployment model. It would allow us to build a single installer that deployed SQL Express 2005 on Windows 2000 SP4 machines, SQL Express 2008 on Windows XP SP2 and Vista SP1 and SQL Express 200...
Blonde moment, please ignore the first part of my question as it's the first part of the launch conditions.
It would be nice if I could chose to block the installation if the operating system is greater than Windows 2000 and it's service pack level isn't what we require.
Hi, I'm currently evaluating Advanced Installer. So far I'm very happy with what I have seen and will be placing an order for Enterprise once I've ironed out the last few issues. I'm trying to install prerequisites based on the operating system version and service pack level. I can get the operating...