What does all that nerd lingo mean?

Basically I have some data I need to take out of the database and pass it to another server for processing in a service oriented architecture.
When this remote process is complete it will pass me back the results that I will save in the database.
The transport mechanism we will use is WCF or windows communication foundation.  To use this on the client side, which happens to be a database process. We will create a proxy class.
SQL SSIS is SQL Server's new DTS on steroids performance enhanced DTS. SSIS allows scripting in VB.net only (don't ask), and to use outside compiled dll's you have to register them in the Global Assembly Cache with a strong name, this is just a fancy way of making sure your dll's are unique.
This will happen on a timed interval.  Seams pretty simple huh?

In order to leverage windows communication foundation within SQL Server SSIS there are a number of things you have to do to make this happen. 

Build your client proxy WCF service model bindings from WCF service.

1. Build an assembly that will wrap the logic for your WCF call.
2. Sign the assembly with a strong name. (sn.exe or VS IDE).
3. GAC your new assembly on the SQL box by copying into C:\WINDOWS\assembly.
4. Merge your proxy app settings into DtsDebugHost.exe.config and DTExec.exe.config.
5. Welding in custom assemblies in SSIS with configuration variables.

 Make sure your dll is GAC'ed and refernced in your SSIS script project.

 Make sure your dll is added to your Package.dtsx.

 Welding in custom assemblies in SSIS with configuration variables. 

(I will pop a GAC in your CACHE !!!!)

Pre-requisites

SQL Server 2005 (including SSIS), Microsoft Visual Studio 2005 / 2008, .NET Framework v2.0-3.5

Prep the Assembly

Adding a reference to the Assembly in SSIS script designer

 Intuitively one would think your next step is to open your SSIS script editor and within your project explorer simply add a reference to your newly GAC’ed assembly.  However when you right click on References -> Add Reference and browse the list of available assemblies - yours is not there.I will not spend time trying to explain the intricacies of why this is, instead I will focus on how to get your .dll registered so you can get up and working.  The bottom line is your going to have to modify the Package.dtsx manually edit the *.dtsx script file to add additional paths to look for your defined assemblies. For example:  Open the file and first search for “<Build>”.

Add yours to the end of the ReferencePath attribute. 

<Build>         
ReferencePath = "C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ScriptTask\9.0.242.0__89845dcd8080cc91\;
C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\9.0.242.0__89845dcd8080cc91\;
C:\WINDOWS\assembly\GAC_MSIL\ myAssembly \1.0.0.0__5d6caf3fc6396ac3\"

Then you can define you assemblies in the References Tags a little further down: 

<References>           
<Reference Name=" myAssembly " AssemblyName=" myAssembly " /> 
            *Next time you fire up the script in Visual Studio of Applications it will be referencing Next Search for “<References>”.  

<References>               
            <Reference Name = "myAssembly" AssemblyName = " myAssembly "/> 
</References>

Using a configuration varibles.