A little while ago, we issued an alpha release of Rubberduck 2.0, just because, well, v1.4.3 had been around since July 2015, and we wanted to say “look, this is what we’ve been working on; it’s not nearly stable yet, but we still want to show you what’s coming”.
Time flies. 6 whole weeks, 353 commits (plus a few last-minute ones), 142* pull requests from 8 contributors, 143* closed issues, 60* new ones, 129,835 additions and 113,388 deletions in 788* files later, Rubberduck still has a number of known issues, some involving COM interop, most involving COM reflection and difficulties in coming up with a host-agnostic way of identifying the exact types we’re dealing with.
It might seem obvious, but knowing that ThisWorkbook is a Workbook object is anything but trivial – at this point we know that Workbook implements a WorkbookEvents interface; we also know what events are exposed: we’re this close to connect all the dots and have a resolver that works the way we need it to.
So what does this mean?
It means a number of false positives for a number of inspections. It means false negatives for a number of others.
Other than that, if the last version you used was 1.4.3, you’re going to be blown away. If the last version you used was 2.0.1a, you’ll appreciate all the work that just went into this beta build.
There are a number of little minor issues here and there, but the major issues we’re having pretty much all revolve around resolving identifier references, but I have to admit I don’t like unit test discovery working off the parser – it just doesn’t feel right and we’re going to fix that soon.
Speaking of unit testing… thanks to @ThunderFrame’s hard work, Rubberduck 2.0 unit tests now work in Outlook, Project, Publisher and Visio.
@Hosch250 If you get unit testing to work in outlook I’ll eat my hat.
– @RubberDuck 2016-05-13
So Chris, how’s the hat?
Stay tuned, things are going to snowball from this point on – we’ll be releasing much more often than we have been.
*From the GitHub “Pulse” page between May 7 and June 7, 2016.
Rubberduck News 
I saw somewhere else in this site that Bovey/Bullen Smart Indenter will be part of 2.something. Is it in there now? I guess I’ll download and find out.
LikeLike
I just discovered Rubberduck on reddit yesterday and I am amazed how helpful this tool can be. So first thing in the morning I downloaded the 1.4.3 and tried to use it. I am developing in Access and unfortunately I already have some issues. Is there any place (forum?) where I can ask “noob” questions?
LikeLike
Hi Andrew, we are currently working on ironing the wrinkles of 2.0 – you probably encountered some of the several parser issues in 1.4.3, all of which have been fixed or worked around in 2.0. I suggest you give the latest version a try (there *are* some stability issues though), and you can always make a new issue in our github repository: https://github.com/rubberduck-vba/Rubberduck – cheers!
LikeLike
Thanks, I already set up the 2.0. But still am facing a number of issues. I will open an issue in github repository. Since I did not see any installation package, I installed it using the the Contributing.Initial Setup part of the github wiki. Thanks again.
LikeLike