Ignore not found definitions in config files
Hello, I have a project with several packages and they have a shared config file, but the problem is that some of the packages do not include all the components that are referenced in the config file, resulting in failure when I try to run these packages. Is there any way to make the packages just ignore invalid references in the config? Thanks.
November 7th, 2010 11:09am

No, there's no way to do this. But the "best practice" in your situation would be to divide what's in that configuration file into multiple files. You would then use whichever configuration files you needed for each specific package. Talk to me now on
Free Windows Admin Tool Kit Click here and download it now
November 7th, 2010 3:00pm

Crazy, ain't it? I wonder if it's worth the effort to build a custom task that all packages call first to pull in all values, just to avoid these kinds of troubles. Josh
November 7th, 2010 8:46pm

If you want to have a single master config file then you can add all the configurable properties in each package. Ex: If package1 has 2 configurable properties (var_P1 and conn_P1) and package2 has only 1 configurable property (conn_P2), then you can add a connection manager conn_P2 in package1 and conn_P1 to package2. Also, add a variable var_P1 in package2.Nitesh Rai- Please mark the post as answered if it answers your question
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2010 12:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics