Resolving circular references in VBA via ObjectStore class and CleanUp cascade
I have been working on a VBA database library and realized I had a few circular reference loops in my class hierarchy, as illustrated in the figure (left panel). I recalled reading an RDVBA blog post about the circular...
I haven't pushed anything yet, but I'll have an update for the website soon; I'm moving all the database and GitHub interactions to a web api, so the website project itself will not need any api keys or connection strings. So far got endpoints for the indenter, fetching tags and xml assets, getting the inspection defaults config, and CRUD operations on everything in the database. The logic that parses xmldocs is also moving to a service library that's part of the public solution.
@Vogel612 In my book, if they took the "senior" in the title to mean "I'm done studying", they should find a new park bench to sleep on because they aren't going to be senior anything.
Ok, I take it back. They can be a senior idiot if they want to be. :-p
@Vogel612 the API works off the latest .net framework, referencing antlr and RD libs just fine (on Windows anyway) - I don't see any reason at all the website itself couldn't be entirely platform-independent =)
Version 2.5.2.5906 OS: Microsoft Windows NT 10.0.19042.0, x64 Host Product: Microsoft Office x86 Host Version: 16.0.14527.20234 Host Executable: EXCEL.EXE
I let it run overnight (knowing that it would not stop spinning). Don't know what I am doing wrong. The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:
Rubberduck version [...] Operating System: [...] Host Product: [...] Host
Can you please elaborate a bit on the steps to reproduce the problem, and confirm that your test module has at least one unit test?
Obviously something is wrong if the toolwindow's "busy" state is erroneously set (or erroneously not reset), but the spinning duckies would only be shown while parsing / discovering tests. How was the parse triggered exactly?
This adds decorators for several com wrapper types that suppress disposal attempts on them. This is relevant in two places. First, the wrappers handed out by the ProjectsRepository are references to cashed wrappers; only the repository itself should be allowed to dispose the instances when it clears its cache. Second, disposal of the com wrappers bound in CW is non-deterministic. In order to avoid running into concurrency issues on shutdown, CW sho
VBA Rubberducking
VBA Rubberducking