Hi all

Apologies if this has been asked before, but I have an application (Office), that has multiple deployment types which all reside in the same folder on the data source and are dependencies of each other.  Eg DT1 -> DT2 -> DT3.

If I specify the content location as the data source for each of the DTs, the size of the application is multiplied.  However, if I specify the content location once (ie on the first DT), the subsequent DTs fail because the path to the exe's isn't found.

What's the correct way of setting this up so that the size of the application isn't multiplied (which causes massive downloads to the client) and that all the DTs are deployed.

Cheers

Simon

Each DT must have a data source location. Why are you making the DTs dependent on each other though? I'm not clear why you would do this? Why not use a script that runs all three command-lines from a single DT? The whole point of a DT is for a client to dynamically choose one DT within an application at deployment type.

Hi Jason

Thanks for the reply.  The reason is to deploy Office, then perform a couple of configuration changes afterwards which happen to be stored in the same data source location.

Customer doesn't want to use any scripts in deployments because 'it complicates things'.  We didn't really want to use a separate application for the deployment of office, then one for configuration change '1' and another for configuration change '2'.

Essentially the customer just wanted it to work in a similar way to a traditional package with multiple dependant programs within the package, but with the added benefits of detection criteria.

Cheers

Simon

If you really want to do this, do separate apps for everything you want to to:

App1 (DT1) => Content location that App1 needs

App2 (DT2) => Content location that App2 needs

...

Configure the dependencies for apps.

For the source locations, create own source folder for every app and copy only the NEEDED files for that specific app to the according source folder.

• Proposed as answer by narcoticoo Sunday, January 12, 2014 8:52 AM

Essentially the customer just wanted it to work in a similar way to a traditional package with multiple dependant programs within the package, but with the added benefits of detection criteria.

That's simply not the way applications are designed to work though so they can "want" all day long.

As for scripts complicating things, well, it's time to open the customer's eyes to the real world. A three line script is much simpler than three applications, three DTs, and three dependencies. It's also simpler than a single package, and three programs, and three dependencies. (I'll stop there before I characterize an IT admin who's afraid of scripting ... too late).