1

This is still an external reference issue. Previously you had issues with external dll not being merged with Event System DLL. And that is the exception you observed previously. Normally, if you just copy/paste your dll and Event system DLLs in bin folder and start Tridion, Event System might work, but you will observe issues with Content Porter, Core ...


1

This could be a problem with assembly probing. To investigate this, you can use Microsoft's Assembly binding log viewer (Fuslogvw) This will be different for each distinct process. If this is the problem, then you can either put a copy of the assembly on the probing path of each process, or register it in the GAC.


Only top voted, non community-wiki answers of a minimum length are eligible