Best practice with respect to wcf configuration files for SSIS

Question

So after reading a lot of posts and blogs on how to configure SSIS to read from configuration files , I am still not clear and would like any expert to provide a definitive stance. In my case the WCF service consumption is wrapped into a separate assembly.
I am referencing the assembly in an embedded C# script within my SSIS package.
When I make the helper class call to the webservice , I get the endpoint not found WCF exception.
Keep in mind I am running this from VS 2012 IDE and did the following to make sure the WCF call works:
1. Googled and found that you need to have config entries in DtsDebugHost.exe.config file. But it still did not work
2. Had the same entries in the associated app.config file for C# script but it still did not work.
It seems like SSIS is very fragile w.r.t consuming WCF entires in a config file. Is the best practice to just have the end point created in code and externalize the end point as a SSIS variable / xml file or is there really a way to get these config files working.
Attached is the wcf snippet of my config file.
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="ITransactionProcessor">
<security mode="TransportWithMessageCredential" />
</binding>
</basicHttpBinding>
</bindings>
<client>
<endpoint address="https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor" binding="basicHttpBinding" bindingConfiguration="ITransactionProcessor" contract="CyberSource.ITransactionProcessor" name="portXML" />
</client>
</system.serviceModel>
SM

Answer 1

I have the code working without use of config files. I am just disappointed that it is not working using the configuration files. That was one of the primary intents of my code re-factoring. 
 Katherine
Xiong , If you are proposing this as an answer then does this imply that Microsoft's stance is not to use configuration files with SSIS?? Please answer.
SM