Mathieu Guindon

1. Let's try to include all checks, and if there's a problem, then we can consider moving the less-common checks to the `Execute` implementation, and display a message box that...

Oh - in my mind the selection columns are simply ignored; we work with the `StartLine` and `EndLine` of the user's selection, simple as that :wink:

@Vogel612 :+1: good point - we can keep that in mind for a future iteration!

The parser runs in the code pane for _one_ of the passes; then it exports each module to `%temp%\Rubberduck` and makes _another_ pass to capture the hidden `VB_Attribute` values. If...

Perhaps the best way to do this would be to add a new `TempExportPath` setting that defaults to `%temp%\Rubberduck` but can be configured to something else.

@bclothier that sounds more likely than somehow-volatile write permissions under `%temp%\Rubberduck`...

RD suspends parsing when the IDE isn't in design mode - an interim work-around can be to add/remove modules programmatically, at run-time.

@neilt1700 AFAICT it's been fixed a little while ago, but since we know for a fact that some of the objects are still leaking (mostly parser state stuff IIRC), we...

Controls on a UserForm shouldn't be triggering this inspection, and public parameterless procedures in a standard module shouldn't either. Can you confirm which version you're using? Thanks!

Side note, should there be a `ObjectOrientedOpportunities` inspection type?