I'll see if I can come up with a [simple] reproducible case.
I used an invalid format string in string.Format()
and the exception was caught by the loader, and
the Initialize() function was reentered, with a
somewhat different call stack, but still coming from
acdbmgd.
I may have overstated the significance of this as
it does not really make debugging difficult, so long
as you know that the exception can result in a
second call to Initialize().
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy" wrote in message news:4943728@discussion.autodesk.com...
Are you saying that IExtensionApplication.Initialize gets called multiple
times? I can't repro this. Does this happen in all apps?
Albert
"Tony Tanzillo" wrote in message
news:4943615@discussion.autodesk.com...
When I load a debug build of an assembly into AutoCAD
with the debugger (using NETLOAD), and an exception is
raised in IExtensionApplication.Initialize(), that method
is called a second time, by the interop runtime.
This is making it very difficult to debug initialization code.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com