What is the most efficent way to iteratively debug custom SSIS component?

I'm iteratively writing a custom SSIS component.  I have two Visual Studio 2013 sessions open. One for the custom SSIS component and one that has a test SSIS package to test the custom data flow component. When I compile the SSIS component, it does the usual uninstall/install to the GAC and places new copies of the assemblies in the appropriate SQL pipeline directories.

In order for the new version of the component to be reflected in the test SSIS package, I have to close Studio and reopen the test project.  Is there an easier way to do this?  Seems tedious to do that every time I make a new change to the SSIS component.  Simply refreshing the toolbox does not work.

T

March 26th, 2015 4:45pm

I think reopen SSDT and reopen the project should be the most efficent way.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2015 2:15am

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

Other recent topics Other recent topics