Skip to main content

Abstract

In the previous chapters, you created some very useful Script Tasks to help you with all kinds of tasks. The downside of using a Script Task is that the code is stored in the package itself. If you have multiple packages using the same Script Task, then you end up with a whole bunch of Script Tasks—each using its own copy of the code. When you need to fix a bug or add some extra functionality, you first have to find all the packages that use that particular Script Task and then change them all, one by one.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 69.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 89.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Electronic Supplementary Material

Below is the link to the electronic supplementary material.

978-1-4842-0638-6_16_MOESM1_ESM.zip (zip 1 kb)

Rights and permissions

Reprints and permissions

Copyright information

© 2015 Joost van Rossum and Régis Baccaro

About this chapter

Cite this chapter

van Rossum, J., Baccaro, R. (2015). Create a Custom Task. In: Extending SSIS with .NET Scripting. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-0638-6_16

Download citation

Publish with us

Policies and ethics