I think I understand the big picture of using external dlls in the package. I've added a Script component to my data flow task, added the references and using statements to it, and can create new instances of my objects (a Customer, for example). And since I will probably never 'deploy' this package , I don't need to worry aboutthe GAC.
My question is more to do with the mechanics of saving the data once the Customer is created. Do I let the business/Data layer in the dlls handle that by creating a connection provider within the Script component, then saving that object to the provider and let it handle the table updates? Or do I need to set up a destination connection in the package and somehow take the Customer and break it out and insert records into the appropriate tables?
I haven't been able to find an example of a Script Component that does this. The examples I've found all take data into the S.C., transform it, then send it back to the packageas output, then the package proceeds on.
Ideally, my package would read the data from an input source, then send that data to the Script Task. The Script Task would create the object (Customer) using the input data, then persist that object into the database using the Data layer dlls. Is something like that possible?