2.0 Beta Release

Since 2.0 alpha release, Rubberduck has had many features extensively revised, improved, and added.

• Settings: All settings fully work now, as does the indenter settings preview. The dialog can now be resized, too!
• Code Explorer: The Code Explorer really works, and is a full replacement for the Project Explorer. It even offers virtual folders to organize your members by—just add a '@Folder("folder1.folder2.folder3") comment to the top of each module, with the . signifying a folder nested in the previous folder. The . delimiter can be set to a slash (/) instead of a period (.) in Rubberduck’s settings.
• Source Control: The Source Control window received a bug fix or two and a slightly updated UI for messages.
• Inspections: The Inspections window now wraps the text at the bottom of the window correctly. Many inspections sport new bug fixes as well.
• Refactorings: Multiple bug fixes make the refactorings more reliable.
  • Extract Method refactoring has been completely rewritten and is now much more robust, thanks to the awesomeness of @grleachman (yes I mean it, Gareth!); user interface and function extraction should be back for next release.
• Resolver: A completely rewritten resolver will help prevent Rubberduck from not being able to resolve valid code. The parser also has many improvements, the least of which is not speed.
• Unloading: Unloading the addin correctly removes it from the VBE. There are still some issues when reloading it.
• Smart Indenter: Now allows you to indent an entire project, or all components in a folder, or to mark a component to not be indented. See the Code Explorer for this feature. Also sports several bug fixes.
• Translations: Thanks to the dedicated work of INOPIAE and Vogel 612, the German translations are still up-to-date. The French translation is also done. Other translations are coming soon.
• Unit Testing: The unit testing feature now works off the parser, updating its list of known tests with each reparse. It also allows ignoring tests with the “'@ignoretest” attribute and correctly displays them, unlike the last release. Best of all, Rubberduck now supports unit tests in Outlook, Project and Visio.

Known Issues

This beta release isn't perfect - it wouldn't be a "beta" if it were. All known issues are documented in our issues list. The most important ones are:

• Unit test discovery working off the parser makes it much, much slower than it should be.
• Occasional crash upon closing the host application.
• Some built-in classes' (documents) events aren't recognized as such... yet. This impacts a number of inspections, that fire up results, when they shouldn't.
• The type of document modules isn't known.... yet. This also impacts a number of inspections, that don't fire up results, when they should.