I have an SSIS project containing multiple packages and multiple
..dtsConfig files. Each package, depending on the connection
requirements, may use a different .dtsConfig file to set the connection
string for the Connection Managers.

These packages perform several different loads. Some load data from
Oracle to SQL Server (connection string for Oracle source Connection
Manager stored in ora.dtsConfig, connection string for SQL Server
destination Connection Manager stored in etl.dtsConfig). Another set
of packages load data from SQL Server stage tables to the relational
table star schema (connection strings for SQL Server source and
destination Connection Managers stored in dw.dtsConfig).

What I have found is that the Build fails when the SSIS project is set
to create the deployment utility. If the SSIS project is set to NOT
create the deployment utility, the Build succeeds.

The errors are stating that the Connection Manager configuration found
in dw.dtsConfig cannot be found in a package that loads data from
Oracle to SQL Server. Sorry, I am away from the office so I cannot
specify the exact error message. There are also errors stating that
the Connection Manager configuration found in ora.dtsConfig cannot be
found in the packages that load data from the staging tables to the
star schema.

My questions are:

1. Does the Deployment Utility creation process try to create one
dtsConfig file for all of the packages within an SSIS project?

2. Alternatively, is the Deployment utility creation process trying to
validate the first dtsConfig file it finds in the project so that when
the project Builds, it fails because the Connection Managers in the
dtsConfig are not found in one of the packages?

I am struggling with this because I thought the deployment utility
would be able to create the manifest file for multiple packages even if
the packages may have different Connection Managers and different
dtsConfig files.

Any help is most appreciated.

-Eric