Does anybody know what causes VS to open and validate all SSIS packages in a solution when only one package is being debugged?I have the impression that this problem occurs only after building and deploying the solution. I did find a workaround for it: delete the entire solution from your local disk, then get it again from SourceSafe. It therefore seems that after building and/or deploying a solution, something is stored locally that tells VS to do what it does...As removing everything locally is a rather unwanted thing to do each time after building and deploying, I would like to know what exactly causes this to happen and how to prevent it.Thanks, Hans.

I am not sure if I have the "complete" answer.However, when you build your solution, VS "opens" all packages in the solution for validation. Henceforth, since all packages are open, VS will always load them all on startup and validate them (unless you go into 'work offline' mode). But, you can "close" open packages simply by right clicking the tab for it on the top. For me, if I close all packages except the one I am debugging, VS only brings up the desired package next time (is this not the case for you?)HTH,Nitesh

As long as you have CreateDeploymentUtility set to True in your project VS will keep opening all your packages. There is no need to remove anything. Simply set the property to False when you don't need it.

OK, so it's over five years old, but thank you Nick for your reply. Finally solved a problem that has been bugging me for ages. Just in case you're alerted to replies - thanks! Anyone else finding this through search, setting CreateDeploymentUtility go False works.