|
I am developing a Winforms add-in for a major CAD package. I have incorporated EMAB throughout the add-in, which is comprised of 11 forms. All of the forms are encapsulated in 4 separate .dll assemblies. When I invoke the add-in from my test harness, the app.config for the harness is referenced so my custom publishers work flawlessly.
However, when the add-in is invoked from the CAD program, the assemblies are loaded as interops by the program. No app.config is read, so the custom publishers don't work. The default publisher works (application Event Log), but I have built user interaction (via MsgBox and email) into the custom publishers. Any handled error during runtime goes unnoticed by the user.
I have searched the web extensively for a solution, but haven't seen anything substantive. I have seen instances of custom configuration "loaders", but I can't seem to get my head around how to implement in the invoked assembly. Has anyone else encountered/overcome this issue?
TIA,
Eric |