How to create an installer for your custom extension

re: How to create an installer for your custom extension

toddmcdermid — Wed, 10 Dec 2008 22:05:48 GMT

Hi Matt,

Thanks for the primer - it will help tons.

One more favor to ask though - is there any way you could walk over to the Visual Studio Extensibility guys and have them help with the "last mile" of making an installer? How can an installer place the component into the BIDS toolbox?

I've tried myself by looking at archives of Chetan Chudasama's blog, and a derivative of that work on CodePlex (the Visual Studio Toolbox Manager) that is so tantalizingly close to working... but doesn't.

Thanks!

re: How to create an installer for your custom extension

toddmcdermid — Mon, 02 Feb 2009 21:38:15 GMT

If you'd like to know how to add an SSIS custom Task or Component to the VS toolbox with an installer (so you don't have to Add Items), vote for this Connect issue: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=407817

re: How to create an installer for your custom extension

tfreedman — Thu, 05 Feb 2009 18:17:52 GMT

Matt,

Thanks, this was extremely helpful. However, I would suggest one change. As per the MSDN's advice on deploying custom SSIS objects(http://msdn.microsoft.com/en-us/library/ms403356.aspx#deploying), we should check the registry for the proper installation folder. With tips from KB article 827026 (http://support.microsoft.com/kb/827026), I was able to use a Launch Condition to search the registry for the key I needed (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\Setup\DtsPath for SQL Server 2005) and store it in a variable I named DTS_PATH. Then, in my ApplicationFolder's DefaultLocation property, I put [DTS_PATH]\Tasks (since I was installing a custom task). Now my installer will work even if SQL Server isn't installed in the default location.

Thanks again for the post - it was a huge help!

re: How to create an installer for your custom extension

mmasson — Fri, 06 Feb 2009 21:46:33 GMT

This is a great point - using the registry keys is definitely a good idea. In 2008, the key was moved from the MSDTS hive to the main Microsoft SQL Server path -

HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS\Setup\DTSPath

When I have time, I'll update the blog post with this information, as well as any tips about controlling the Toolbox I can dig up.