Microsoft .NET Framework error message when close Excel #6150
Comments
|
I get this annoying issue as well in MS-Excel which have to sign out as locks my COM type library referencing from rebuiding. Thought maybe it was already reported. Version 2.5.2.5906 @Brian45Fr The Host product details can be copied from menu Rubberduck->About (Copy version information to clipboard) link |
|
Could you try whether the exception still occurs with the latest prerelease? I tried to prevent the access after release. However, I cannot check it myself, because the race condition does not occur on my machine. |
Currently using Version 2.5.9.6296 which assume is the latest release. And for MS-Excel still get the excpeption triggered when closing MS-Excel. Excpetion is triggered even for a blank MS-Excel if visit the IDE. MS-Access appears fine which mainly use. Version 2.5.9.6296
|
|
This is the same issue my PR above tried to fix. That PR should have come in with the latest prerelease 2.5.9.6304 two days ago. Could you please check whether the issue persists in the latest prerelease? |
Where do you find the latest prelease 2.5.9.6304 installer? Prerelease-v2.5.9.6296 is the latest can find via the rubberduckvba site. Or any other methods how to install the latest prelease? Think I've found it. https://github.com/rubberduck-vba/Rubberduck/releases/tag/Prerelease-v2.5.9.6304 will check out later. |
Using prerelease 2.5.9.6304 it appears the exception when closing MS-Excel has been addressed. Version 2.5.9.6304 |
Normally that is automatically handled by a webhook endpoint on the API side, but the API has been down for a while and I really need to start looking into it... it's probably something as stupid as a GitHub token that expired and I somehow missed the email about it... although it doesn't explain why the rest of the public API is down, anyway... |
Thanks found it and just installed version 2.5.9.6304 and appears the exception when closing MS-Excel was fixed. |
|
Happy to hear that my fix worked for you. Would it be possible to provide a warning level log from Rubberduck? I would like to verify that we log it when the unexpected access happens and gets swallowed. Actually, I am only really interested in the last warning message(s) about access after release. |
|
@MarkJohnstoneGitHub, Great, but why doesn't it work for me :-( |
Hopefully this is what you require. Attached the Rubberduck log just now after opening and closing an Excel project. It might have the log from ealier tonight. Yeah it's just past midnight did the opening and closing. |
Did you install version 2.5.9.6304? https://github.com/rubberduck-vba/Rubberduck/releases/tag/Prerelease-v2.5.9.6304 . I just run the Rubberduck.Setup.2.5.9.6304-pre.exe to install it. |
Note: I haven't tested yet if still locks up the type library working on when exiting MS-Excel which was real annoying "feature". I'm assuming as now handing the exception "should" be ok. Will try and remember to test that the next time rebuilding the type library. Usually I'm developing in MS-Access and periodically update an MS-Excel verision to avoid the initially issue. |
|
@MarkJohnstoneGitHub Thanks for the log. The shutdown is still rather messy and warrants another look. However, we now seem to catch the exceptions at least. Seems the culprit for the crash was the access inside the exception handler,. |
Nice could help identify the issue and awesome that the RD flock is still fixing critical RD2 issues. I know they are busy tinkering away with RD3 and noticed some up "late" burning the midnight oil. Wish could more directly help IMO my C# is average. Only started programming in C# since about June. Going need some good karma to help with some COM questions down the track.😉 Like How to implement a predicate? and How to implementing the Char data type? . Ideas for those on the backburner thou love to open up the full functionality of the C# Array in VBA. Achieved in VBA for C# Arrays dynamically creating for a type provided and functionality not requiring generics. |
Rubberduck version information
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:
Description
When I want to exit Excel directly, I get this error message
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error message, exit Excel normally
Screenshots
Logfile
Rubberduck generates extensive logging in TRACE-Level. If no log was created at
%APPDATA%\Rubberduck\Logs, check your settings. Include this log for bug reports about the behavior of Rubberduck.RubberduckLog.txt
Additional context
Add any other context about the problem here.
DetailErrorMessage.txt
The text was updated successfully, but these errors were encountered: