Closed woxovvoxow closed 7 years ago
Please check out the beta. We fixed a bunch of bugs since the alpha release, and this may well be one of them.
Hi,
I tried the version 2.0.b, 2.0.1b and 2.0.2b now. The behaviour changed a bit in that way, that there's no Error-message any more, but It is still not working. Starting for the first time the addin is loading, but for exaple the test-explorer does'nt recognize its tests:
The menu Code-Inspection is not working as well - it is showing no results at all. At least every 2.nd time Access is not closed properly - I have to kill the MSACCESS-process in Task-Manager.
for me it looks like I still have an issue with no proper installation / registration or so.
any help appriciated - I was dreaming to have a VBE like this (at least what I can see from your Site) and now it is not installabe properly on my machine... :-(
...closed accidentially..
Looks like it is not parsing. The Code Inspections, Test Explorer, Code Explorer, and Todo Explorer all require there be a successful parse and resolve to work. If you have a very large project, it could take a while--what does the status bar say? The host app not closing properly is a known issue being addressed.
You are right, it is obviously not parsing. The project is just a Test for the Addin - only 2 Modules - so there should be no performance issue.
The status bar displays "Referenzen werden geladen" (resolving).
so it seems to be the same issue as #1843.
Actually that's not quite correct. The status bar says "loading references..." which is different from resolving. #1843 is not related
Meanwhile I installed 2.0.3b.
I found out that code-Inspection seems to be ok (loading references - parsing - ready) as long as I dont add a reference on Rubbeduck.tlb (for Unit-Testing). Once I add the reference, close Access and reopen it, Rubberduck gets stuck in "loadin references". Sometimes a click on the refresch button next to the status starts a proper parsing (stops with ready) sometimes not...
OK, thanks for the updates.
unfortunately no change with 2.0_RC1 here... :-(
Trying to add a test-Procedure Rubberduck crashes with the hint to send the logfile. Where can I find the log? The only file i found "Rubberduck.App.log" has a change-Date in Mai...
Is it just Access, or Excel doesn't work either? You can get to the logs via the settings dialog; from there you can also set minimum log level to 'Trace' to log everything. Hopefully something gets logged.. what version of Access are you using?
Nevermind, saw Access 2010 in the original post
OK, thanks - I switched Logging to "Debugging". Attached you can find what happens, when I try to add a Test-Method:
(renamed rubberduck.log to rubberduck.txt for Upload)
Looks like a failing First call. I wonder what's up there.
I just changed this to do nothing in this case. I'm not even sure why this even happens (the commands should be disabled...)
Hi,
I'm very interested in your Project providing an up-to-date VBE! Everything I've seen so far looks very promising.
My environment is the following:
(obviously both 32bit and 64bit .NET Framework)
Rubberduck was installed with lokal Admin-Rights
when I open Access-VBE the following Error occurs:
The Details show following information:
I already tried your hin "Troubleshooting: Rubberduck Add-In could not be loaded" and succeeded in registering Rubberduck.dll - but nothing changed.
after clicking un "Continue" i can start for example the Test-Explorer, but nothing is working properly.
Closing Access it crashes.
any Ideas?