How to prevent overwrite of previous user application deployment.

[Gary_H]

Hi,

I've been using the Teststand 3.1 and 3.5 Deployment Tools for a while now, with success.

However, my deployed applications exist as single entities, by this I mean all the files used

by the target Production PC were deployed by a single installer.

I would now like to structure the deployed application as 2 parts, i.e. create 2 installers.

The first installer creates a main sub-directory on the target PC, and the second installer creates

a sub-directory within the first main sub-directory.

By creating a simple example, I find that the second installer does create a sub-directory containing files

within the main directory created by the first installer, but any files in the main directory are deleted. 

It appears that the second installer performs an automatic un-install of the first installer.

Is it possible prevent this automatic un-install so that I can create a "Main System" installer, which can be

updated or added to by other (several) "Product Type" installers ?

thanks,

Gary.

[Gary_H]

Look's like I 'm having a little finger trouble, a colleague has managed to achieve the installation arrangement in 2 parts, just as required.

The problem was overcome by changing the Upgrade Code for the 2nd installer, within the Deployment Tool - Installer Options tab - Advanced Options.

Should have read the Help file.

thanks,

Gary.