Skip to content

Home

Jump to bottom Edit New page
Philip Wales edited this page Apr 10, 2015 · 28 revisions

###Why Rubberduck?

Because we want a pet project, and this one is fun, and challenging. The idea is to do everything we can to make programming in VBA and refactoring legacy VBA code, as enjoyable as in the modern-day versions of Visual Studio. The VBE has had its VB6 feel for as long as I can remember, Rubberduck takes it... elsewhere.

It all started on Code Review, with a post about unit testing in VBA. It grew into a 100% VBA working solution, and then we wanted to have this unit testing functionality built into the IDE - the COM add-in solution started with it.

Having access to the entire VBE object model in a COM add-in that can add custom menus, toolbars and dockable windows, we wanted to parse and inspect the code, and fix issues - or at least point them out.

Then we just thought let's pack everything we want to implement to extend the VBE. We added ways to navigate the code more easily, a list of todo items, and then we had ideas like integrating source control, implementing some refactorings, using the Stack Exchange API to create and post your VBA code as a Code Review question.

Where is this going to take us? No idea. But it's a fun ride. Fork us!

Table of Contents

Using Rubberduck

Collaborate!

  • Tag Wiki: Everything you ever wanted to know about the tags/labels we use in this repository.

What's cooking?

See our Milestones page for a quick progress report on the next release.

If you think of a feature you'd like Rubberduck to have, but don't feel like implementing yourself, suggest a feature request as an issue and we'll see what we can do; we want Rubberduck to be a great tool to use, so all feedback is welcome, too.

Version 1.3

Here's a few of the features we want to add in the next release:

See release notes for changes between versions.

Twitter @rubberduckvba

  • Meta meta meta
Clone this wiki locally