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
Using Exception Management Application Block with CAD program add-in...
Hot Topic
- Webbrowser controls doesn't work on Windows XP SP2
- How to use EnableDesignMode in VS 2005 ??
- datagrid tablestyle
- HeaderClick to select all rows in DGV
- Please post here if you are running a Terrarium server.
- Creating a Bindable Control
- Size of PrintPreview window
- Do the controls that Visual Studio comes with suck, or am I being unfair?
- Functional keys are not woking in datagrid
- Event for Dynamically Created Controls
Windows Forms
- Taskvision Source install problems
- Control TextChanged Event Question
- scheduling
- Binding ComboBox and DataTable including a None entry.
- Tab Leave Event
- Mouse pointer disappears behind form
- c# to Vb.net
- MDI Maximized children forms without controlbox?
- Opening a file with double click
- ClickOnce file names for security list
Using Exception Management Application Block with CAD program add-in...
Baldaris
Also have you tried putting the config files in the same directory as the CAD exe
Neil M Thompson
I actually took over this project, and the previous developer had implemented some poor error-handling. I have been using the EMAB for quite awhile; I like it's ease of use/maintainability, and the flexibility it gives you to customize your error handling. I am trying to establish use of the Application Blocks (and eventually the new Enterprise Library) as the standard for development here. They greatly speed up development, and since they are built on best practices by MS you can be confident that they are bomb-proof.
That being said, I find it hard to understand why deployment for DLL's was not incorporated into the Block frameworks. I will keep trying to find a solution, but would appreciate anyone's input.
Thanks!
Eric