VBA Rubberducking

Duga

00:01

RELOAD!

[Phrancis/ChucK-Scripts] 2 commits. 64 additions. 67 deletions.

[retailcoder/Rubberduck] 1 commit. 54 additions. 16 deletions.

[rubberduck-vba/Rubberduck] 2 commits. 4 issue comments. 108 additions. 32 deletions.

[Zomis/Brainduck] 4 commits. 1 opened issue. 1 issue comment. 97 additions. 27 deletions.

[rubberduck-vba/Rubberduck] AndrewM- opened issue #818: Add support for 'XML' comments to code explorer

> In applications with hundreds of procedures, it gets hard to remember exactly what they do and how they relate to each other. To make my life easier, I have been putting C# style 'XML' comments in my procedures. I wonder if these could be shown as tool tips in code explorer as in the attached mock-up. This would make it far easier to find existing functions suitable for purpose.

![xml_comments](https://cloud.githubusercontent.com/assets/5060805/10354432/0f2e3e00-6da3-11e5-9d75-ea989f1fee

[rubberduck-vba/Rubberduck] retailcoder commented on issue #818: Add support for 'XML' comments to code explorer

> Consider this on the roadmap, I love the idea!

Duga

00:37

[rubberduck-vba/Rubberduck] retailcoder commented on issue #818: Add support for 'XML' comments to code explorer

> How about supporting actual XML comments? I mean, the .net XML comments are well documented, we could very well have an implementation for the VBE, and we could very well export an actual .xml file that could be processed by the exact same tools that generate .net documentation (e.g. SandCastle)... and the <summary> tag could be used in the code explorer as tooltips, but also as a pop-up window in the code pane - you could right-click a method (declaration and usage), select "about this

[rubberduck-vba/Rubberduck] retailcoder commented on issue #818: Add support for 'XML' comments to code explorer

> Now I'm really starting to wish we could hijack IntelliSense...

Duga

00:56

[rubberduck-vba/Rubberduck] retailcoder added label feature-request to issue #818: Add support for 'XML' comments to code explorer

[rubberduck-vba/Rubberduck] retailcoder added label magic-comments to issue #818: Add support for 'XML' comments to code explorer

[rubberduck-vba/Rubberduck] retailcoder added label magic-comments to issue #810: Support @ignore markers for code inspections

[rubberduck-vba/Rubberduck] ShearOfDoom commented on issue #818: Add support for 'XML' comments to code explorer

> Nice idea! I feel like using '/// for XML comments is a little tacky though. Maybe ''' would work? Just an idea..

Duga

01:49

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #818: Add support for 'XML' comments to code explorer

> ''' is what VB.NET uses.

Duga

02:12

[rubberduck-vba/Rubberduck] retailcoder commented on issue #818: Add support for 'XML' comments to code explorer

> So, it could look like this then:

'''<summary>Calls functions that create photo hashes for each photo that does not yet have one.</summary>
'''<param name="s">A description for parameter <c>s</c>.</param>
'''<param name="VSN">A description for parameter <c>VSN</c>.</param>
'''<returns>Returns a <see cref="FunctReturn"/> object encapsulating the result.</returns>
Public Function ReadDrivePhotoHashes(s As TypeSQL, VSN As String) As FunctReturn
'...
End Fu

Duga

02:39

[retailcoder/Rubberduck] retailcoder pushed commit c5b625b4 to next: fixed the 225 failing tests by setting up the mock for CodeModule.CountOfDeclarationLines()

…ntOfDeclarationLines()

[rubberduck-vba/Rubberduck] retailcoder merged pull request #819: fixed the 225 failing tests by setting up the mock for CodeModule.Cou… from retailcoder/Rubberduck/next into rubberduck-vba/Rubberduck/next

[rubberduck-vba/Rubberduck] retailcoder pushed commit c5b625b4 to next: fixed the 225 failing tests by setting up the mock for CodeModule.CountOfDeclarationLines()

[rubberduck-vba/Rubberduck] retailcoder pushed commit 1eba5fbf to next

Merge pull request #819 from retailcoder/next

fixed the 225 failing tests by setting up the mock for CodeModule.Cou…

Duga

02:51

[rubberduck-vba/Rubberduck] scottadoyle commented on issue #305: No additional AddIn was found after installing Rubberduck 1.2.

> I had recently installed rubberduck. I have not used it much. Programming
is not my primary job responsibilities. I thought I had downloaded and
installed the newest version.

I am looking forward to learning how to use the github integration.
On Sep 30, 2015 9:00 PM, "Hosch250" <[email protected]> wrote:

> @scottadoyle <https://github.com/scottadoyle> Any particular reason you
> aren't using 1.4.3? This release brings a bunch of new improvements and bug
> fixes (and a few new bugs

Duga

03:05

[retailcoder/Rubberduck] retailcoder pushed commit a6b227f4 to next: added Annotations static class; changed const to static readonly. fixes #815

Duga

05:06

[retailcoder/Rubberduck] retailcoder pushed commit 3b86a8df to next: can now disable inspections and fix-all-in-project without drilling down to individual inspection results

[retailcoder/Rubberduck] retailcoder pushed commit 7c4e6020 to next: fixed InvalidOperationException in module grouping view - that grouping doesn't seem to refresh as expected

[rubberduck-vba/Rubberduck] retailcoder created pull request #820: Code Inspection toolwindow enhancements to merge retailcoder/Rubberduck/next into rubberduck-vba/Rubberduck/next

[rubberduck-vba/Rubberduck] retailcoder closed issue #815: Make an "Annotations" static class

[rubberduck-vba/Rubberduck] retailcoder merged pull request #820: Code Inspection toolwindow enhancements from retailcoder/Rubberduck/next into rubberduck-vba/Rubberduck/next

[rubberduck-vba/Rubberduck] retailcoder pushed commit a6b227f4 to next: added Annotations static class; changed const to static readonly. fixes #815

[rubberduck-vba/Rubberduck] retailcoder pushed commit 3b86a8df to next: can now disable inspections and fix-all-in-project without drilling down to individual inspection results

[rubberduck-vba/Rubberduck] retailcoder pushed commit 7c4e6020 to next: fixed InvalidOperationException in module grouping view - that grouping doesn't seem to refresh as expected

[rubberduck-vba/Rubberduck] retailcoder pushed commit fedb6a23 to next

Merge pull request #820 from retailcoder/next

Code Inspection toolwindow enhancements

Duga

05:38

[rubberduck-vba/Rubberduck] AndrewM- commented on issue #818: Add support for 'XML' comments to code explorer

> I would not use ''' as they do in VB.net because ms-access has a comment block tool on the Edit Toolbar in the VBE. If you have commented out a line, then commented out the rest of the block with the comment block tool, you are already have ''. Sometimes I globally replace On Error with 'On Error and over time build up to '''On Error. This is probably bad practice on my part but VBA is cowboy land. VB.net also seems to be not that popular (dumped from #Develop) and would prefer to use the

Duga

09:38

[rubberduck-vba/Rubberduck] AndrewM- commented on issue #818: Add support for 'XML' comments to code explorer

> I am happy to use XML as per visual studio but there should be a way of handling comments that are just plain text as well.

[rubberduck-vba/Rubberduck] AndrewM- reopened issue #818: Add support for 'XML' comments to code explorer

Zak

10:28

So, I have a bug report

The RD source-control pane no longer displays

And, possibly, is no longer updating the GH repository

Everything else about RD displays and runs as usual

Also uninstalled and re-installed

no difference

Duga

11:52

[rubberduck-vba/Rubberduck] retailcoder commented on issue #818: Add support for 'XML' comments to code explorer

> I agree that C#'s syntax looks better than VB.NET's, but C# doesn't use a single-quote to denote a comment, `'///` feels somewhat like a bastardization; I don't like the idea of mixing up syntaxes, especially since we're already using Java-like "@" annotations.

The argument about the `'On Error` building into `'''On Error` doesn't hold, and wouldn't affect XML comments unless the instruction was sitting between an opening and a closing XML tag... *if we exclude picking up standalone/stray c

[rubberduck-vba/Rubberduck] AndrewM- commented on issue #818: Add support for 'XML' comments to code explorer

> If XML comments must contain XML, then there is no need for having a different notation for these comments, I am happy with that.

Mat's Mug

13:15

@Duga they're... called "xml comments" for a reason...

Duga

13:32

[rubberduck-vba/Rubberduck] ckuhn203 commented on issue #818: Add support for 'XML' comments to code explorer

> You're not the only one wishing we could hijack intellisense @Retailcoder! This is a great feature request @AndrewM!

Support for XML doc comments is on the roadmap already (somewhere, I'll need to find the issue later and link back to it), but I never considered a tool tip. Most excellent suggestion!

I am going to second that we use the triple apostrophe notation of VB.Net though. It's going to make life much simpler in the long run as far as an implementation goes. I really do bet that

[rubberduck-vba/Rubberduck] ckuhn203 commented on issue #305: No additional AddIn was found after installing Rubberduck 1.2.

> @scottadoyle please be aware that the Git integration isn't fantastic or stable yet (10/8/15). I hope to get it working correctly over the winter.

Mat's Mug

14:37

I touched GPL code once, but I'm not licensed under the GPL. — Martijn yesterday

lol

Duga

[rubberduck-vba/Rubberduck] retailcoder commented on issue #818: Add support for 'XML' comments to code explorer

> @ckuhn203 ooh it didn't even occur to me that we could use Roslyn for that! Wouldn't that be yet another license nightmare though?

Mat's Mug

Licensing is a frakking PITA.

Duga

15:48

[rubberduck-vba/Rubberduck] ckuhn203 commented on issue #818: Add support for 'XML' comments to code explorer

> <strike>Possibly</strike> Probably @retailcoder. Probably...

Duga

17:11

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #818: Add support for 'XML' comments to code explorer

> @ckuhn203 @retailcoder You bet you can use Roslyn for this (I think you might need C# 6, though?). SyntaxFactory (VisualBasic version), then just create an XML doc comment.

Duga

17:55

[rubberduck-vba/Rubberduck] retailcoder commented on issue #818: Add support for 'XML' comments to code explorer

> @Hosch250 except Roslyn is under an APL license and we can't just grab a random part of its source code and embed it into ours..

FreeMan

Howdy, guys. Are you aware that the Go to implementation option doesn't work? It pops open a parsing dialog box, but doesn't change location in the VBAIDE. It doesn't move the cursor there either, as using cursor control keys doesn't jump the editor window to the current location of the cursor.

Oh, and, hey! It's been a while...

Hosch250

@Mat'sMug Of course you can't. What you need to do is generate the code with the Roslyn API, extract the text from the node, and insert it.

Also, the amount of code you would have to insert is incredibly high.

The only issue is the C# 6 thing.

Mat's Mug

19:44

@FreeMan works here

"Goto implementation" != "Goto definition"

Got any interfaces?

FreeMan

OK, my mistake. guess I was expecting it to take me to he [Function|Sub] definition.

That would be an awesomely handy thing to have! nudge, nudge, wink, wink

Mat's Mug

It's... already built into the IDE...

Shift+F2 ;-)

FreeMan

well, who knew???

seriously, I had no idea...

I'll just go back into hiding now

thanks

Mat's Mug

I have an IRepository interface with 12 implementations; goto implementation is useful because if I'm at a call site that's written against IRepository, "goto definition" takes me to the interface class; "goto implementation" lists all the concrete implementations of the method I'm calling, and lets me navigate there ;-)

Chrismas007

20:20

72

Q: The Power of Teams: A Proposed Expansion of Stack Overflow

TL;DR: We're proposing a new area called Teams. The goal is to allow groups (of varying sizes) to publicly share about themselves (who they are and what they build) on Stack Overflow. Content can include information about The Team (Overview, Meta Information), a member roster, projects, communit...

@Mat'sMug @RubberDuck Sounds like a cool concept to have a "team" for RubberDuck

Mat's Mug

already done :)

Chrismas007

See what happens when I'm not on here frequently... i miss all the good stuff

Mat's Mug

@FreeMan damn, you're right - something's not working the way it should with goto implementation

Chrismas007

@Mat'sMug There is quite a bit of negative reaction surrounding it tho...

Mat's Mug

yeah, saw that

I thought "pfft, might as well"

Duga

20:35

[rubberduck-vba/Rubberduck] retailcoder opened issue #821: GoTo Implementation could be smarter

> I have code like this, where `UnitOfWork` is of type `IUnitOfWork`, and `Add` is a method of `IRepository`:

UnitOfWork.Repository("CustomerGroups").Add NewCustomerGroup(description:=description)
UnitOfWork.Commit

The VBE's "goto definition" (Shift+F2) resolves to `IUnitOfWork.Commit` and `IRepository.Add`, respectively; Rubberduck's "find all references" works as expected:

![image](https://cloud.githubusercontent.com/assets/5751684/10378862/6c62c150-6dd9-11e5-9e3f-403bc629d1a

[rubberduck-vba/Rubberduck] retailcoder added label bug to issue #821: GoTo Implementation could be smarter

[rubberduck-vba/Rubberduck] retailcoder added label navigation to issue #821: GoTo Implementation could be smarter

Mat's Mug

thanks @FreeMan :)

FreeMan

Happy to help, @Mat'sMug, even though.. well... yeah.

3

Duga

23:11

[rubberduck-vba/Rubberduck] retailcoder added label up-for-grabs to issue #821: GoTo Implementation could be smarter

[rubberduck-vba/Rubberduck] retailcoder removed label up-for-grabs from issue #821: GoTo Implementation could be smarter

[rubberduck-vba/Rubberduck] retailcoder commented on issue #821: GoTo Implementation could be smarter

> I'd leave it up for grabs, but the code in the dockable presenter needs to be refactored into a ViewModel and the actual UI needs a XAML-ification first, so this issue is a bit premature...

[rubberduck-vba/Rubberduck] ryanjhodge starred us

AndrewM

23:34

Just a note to all. I am still a dedicated procedural programmer and have tried Rubberduck on an application with about 15 KLoc and it all works. It is great that Rubberduck works so well across development paradigms.

Transcript for