Packages

A 'package' can consist of any or all of the following:

• one or more solution .zip files
• flat files or exported data files from the Configuration Migration tool
• custom code that can run during or after the package is deployed to CDS
• HTML content specific to the package that can display at the beginning and end of the package deployment process
  • this is useful only if you want the customer to deploy the package on their own - guided setup dialog

Microsoft's advice is to create packages by using the package deployment template in Visual Studio.

We would like the option to dynamically build these packages because we want to build custom packages for every customer. We are not able to unify this, since every customer has different solutions on their environment.

There's second option - we will be building multiple packages for one customer which can be build in advance and deploy in specific order.