Calling a pkg from managed code and then using reflection to call a method from a script task

Question

Hi we run 2012 std.  I have some pretty good evidence that when I call my pkg from a .net service, a script component in that pkg fails when trying 2 use reflection to load and invoke our .net message history method.  The exception is either on
the invoke or in the message history method.  I suspect its in the method but will take additional steps 2 verify.
But when I run the pkg stand alone, it has no problem and the method does what it is supposed 2 do.
There r no vars passed from the service to the pkg.  I wonder if its a managed to unmanaged to managed issue that the community is already aware of.  If not, my apologies 4 posting this quickly.
I'll post more info here as I collect it. 

Answer 1

we have 2 theories after showing the exception trace to folks who r more adept at managed code.
the first is related to the fact that our 3rd party dlls (I think entity framework is included in these) r older versions.  I don't want to discount this theory but we have some evidence already that this might not be true.
I hope I can do justice to the 2nd theory but will make it clearer and clearer as I get a better understanding.  I believe this is what Arthur was saying and I applaud his instincts.  They explained that .net is so "smart" that it detected
a change in namespace  (ie context as Arthur said) and purposely threw an exception 2 save us from ourselves.  The workarounds discussed were a bit over my head but I will continue trying to better understand it.  The fact that many of the methods
we call after reflection r now merged into one assembly seemed relevant to the discussion and possible workarounds.   
this link came up in their discussion and I believe the bottom line here is that by qualifying assembly names further (in config?)r, a workaround is possible. 
http://msdn.microsoft.com/en-us/library/system.type.assemblyqualifiedname(v=vs.110).aspx  .
This link came up as well and has something to do with ILMerge and workarounds to ILMerge. 
http://elegantcode.com/2011/04/02/dynamically-load-embedded-assemblies-because-ilmerge-appeared-to-be-out/  .
Finally, this link came up and seems to have something to do with embedding your dlls in one assembly without them losing their identity.
http://blogs.msdn.com/b/microsoft_press/archive/2010/02/03/jeffrey-richter-excerpt-2-from-clr-via-c-third-edition.aspx
I'll post more here as we muddle thru this.