Hi, thanks for that. It looks like a useful tool and i've also taken a look at a publish from Artis Consulting (http://www.artis consulting.com/blogs/greggalloway/Lists/Posts/Post.aspx?ID=15) on how they publish packages, which seems to predominately use xml configuration files.

It all seems to be a case of what way you want to bodge it.

It's quite disappointing really from a product that in other areas, performs so well and yet in areas of deployment it lets itself down so badly, with something that really isn't new functionality.

I'm starting to understand why so few people have a made comment here........

Personally, I think I might stick the using SQL configuration tables to set the package path in the live environment, when using File Systems Execute Package Tasks.

If using an SQL MSDB as your PROD package store though with the original scenario of Package C calling Packages A & B, then it would seem that you have no alternative but to develop and publish A & B, deploy these and then develop and deploy package C - albeit the BI Helper looks like it would help in the process as you could singularly deploy a package as opposed to just the whole project.