Clarifications On Debugging And Deployment Strategy

Hi,

I'm currently developing an Integration Service Solution using Visual Studio 2005. In this solution I have 4 packages. The first one call the second one that call the third one and so on.

To be able to debug those packages, the child packages are executed by Execute Package tasks, using a file system connection that point to the .dtsx file located in my project folder. It works great.

My problem is that I now need to deploy my packages on SQL Server. Since the deployment server is not the same as the development one, my Execute Package tasks fail - this is logical, they are looking for a file that doesn't exist on the deployment server. I'd like my parent package to execute the child packages located on SQL Server.

Of course, I could modify all my Execute Package tasks to use SQL Server instead of a file system connection before deployment but this is very painful (mainly because I have to do the opposite when I need to debug my solution).

Is there a way to streamline that process so that my Execute Package tasks automatically use SQL Server when I set Deployment configuration and file system connection when I set Development configuration ?

Thanks for your help,


Eric.