Hi Brian,
That sounds like Excel crashing, and it would be worthwhile to try to find.
Maybe you can check in the Windows event log for some more information, particularly the error code.
Are you also using the IntelliSense extension?
If so, it might be worth checking whether this is related, as I think that’s a more fragile part than the main add-in library.
-Govert
From: exce...@googlegroups.com <exce...@googlegroups.com> On Behalf Of bpie...@gmail.com
Sent: 16 August 2021 16:06
To: Excel-DNA <exce...@googlegroups.com>
Subject: [ExcelDna] Possible very minor v 1.5 issue?
Hi Govert,
More an FYI than anything else, but I've recently updated to v1.5 and I've seen a couple times where a few moments after closing an Excel workbook that was using ExcelDna a new Excel instance would open. This isn't something I can easily recreate, and it may just be coincidence that it has happened a couple times after the upgrade. I'm going to spend a little more time attempting to recreate, but just letting you know in case you're aware of any changes that might result in such behavior.
Best,
Brian
--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/972a3114-5ee0-4eb9-90bb-f89332e37d18n%40googlegroups.com.
Hi Brian,
> I'll disable IntelliSense and report back
Thank you – that would be the first area to identify or eliminate.
You could also add a handler for AppDomain.CurrentDomain.UnhandledException in your add-in and just write the Exception.ToString() to a file or something.
The crash code you see in the event log indicates that it is an unhandled exception from the .NET runtime, so maybe we get lucky.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/e7d3bbbc-1258-4f8f-8acc-42049e2a976en%40googlegroups.com.
Hi Brian,
Thank you very much – that’s already very helpful!
I realize that happens without changes to your code between the Excel-DNA versions, but it would still help to understand what interactions are involved.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/d89d21fb-a509-47a7-8ffe-bcdfc4de1c70n%40googlegroups.com.
Hi Brian,
Thank you for the follow-up and checking some more.
I think I’ll make the release candidate the official release, and we’ll see if anyone else runs into trouble.
Regarding the first-change exceptions:
Thanks again for the effort!
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/7bf42688-46fe-48b5-9875-aa3c6d47f27an%40googlegroups.com.