RELOAD!

[Cardshifter/Cardshifter] 1 opened issue. 3 closed issues. 24 issue comments.

[Cardshifter/HTML-Client] 1 commit. 2 issue comments. 29 additions. 2 deletions.

[ckuhn203/VBEX] 1 closed issue.

[Hosch250/Rubberduck] 1 commit. 23 additions.

[Hosch250/VSDiagnostics] 21 commits. 1814 additions. 146 deletions.

[retailcoder/Rubberduck] 1 commit. 389 additions. 167 deletions.

[Vannevelj/VSDiagnostics] 19 commits. 15 opened issues. 5 closed issues. 5 issue comments. 355 additions. 103 deletions.

[Vannevelj/VSDiagnostics] 1 commit. 1 opened issue. 1 closed issue. 1 issue comment. 2 additions. 2 deletions.

[Zomis/SE-Scripts] 3 issue comments.

[rubberduck-vba/Rubberduck] vdubya starred us

@Duga 85. One day soon, you'll have 100 stars.

How do I properly install RubberDuck?

Are there instructions anywhere?

@EthanBierlein exit all Office apps, run the installer from an administrator account

@RubberDuck look at this!

    /// <summary>
    /// A TestExplorer model that discovers unit tests in a 'ThisOutlookSession' document/class module.
    /// </summary>
    public class ThisOutlookSessionTestExplorerModel : TestExplorerModelBase
    {
        private readonly VBE _vbe;

        public ThisOutlookSessionTestExplorerModel(VBE vbe)
        {
            _vbe = vbe;
        }

        public override void Refresh()
        {
            Tests.Clear();
            var tests = _vbe.ActiveVBProject.VBComponents.Cast<VBComponent>()

@EthanBierlein there's a known issue about the add-in not registering properly for non-admin users; MZ-Tools has the same issue, and the same fix. let me know if you need more info - if you're local admin then there's no issue.

[retailcoder/Rubberduck] retailcoder pushed commit 9fe7d7f0 to ICommand_Shelved: commented-out broken tests; changed ITestEngine interface, added ITestExplorerModel and implemented a new test engine. Need to reimplement the TestExplorer now,

> commented-out broken tests; changed ITestEngine interface, added ITestExplorerModel and implemented a new test engine. Need to reimplement the TestExplorer now, because RD unit testing is officially broken with this commit. Good news is that the new structure will enable unit testing in Outlook :)

actually I didn't bother setting up ITestExplorerModel with Ninject, so RD is broken, period - it blows up with an ActivationException on startup. no panic, everything is under control.

@Mat'sMug that's fantastic, but shouldn't we leave the red tests red until it does work? Lol

[rubberduck-vba/Rubberduck] syonoki starred us

I hereby apologize for not following @RubberDuck (the person duck, not the project) before on Twitter.

Awesome blog post about "real experience". I haven't faced that as much as you have probably, but I have a big fear about facing it, which might be why I don't apply for as many jobs as I should.

Hey guys, long time no chat. Actually been swamped at job...

I do have a quick VBA style question for ya. Given this code:

Dim MyRS As ADODB.Recordset
MyRS.Open Source:="SELECT a, b, c FROM Table"
Debug.Print MyRS.Fields(1)
Debug.Print MyRS!a

Which reference style makes more sense/is more std/whatever... to me, MyRS!a is more clear, since I know exactly what field I'm using, and it won't break if someone rearranges the query, but, MyRS.Fields(1) seems more right since the dot-notation is supported by the IDE and autocompletes Fields as I type.

@SimonAndréForsberg That's kind of the wrong attitude to have. You should apply a lot.

but not too much. Only apply to the jobs you really want.

@RubberDuck I know. Only applied to 3 jobs this year. One I got interviewed at and didn't get, one that I didn't get interviewed for (dunno why really...) and one that I will have the first of possibly two interviews for next week (should have been today, but I called to postpone it this morning because crappy sickness. really wanted it done today)

@SimonAndréForsberg Hope you get better soon.

@Mat'sMug The Project/Visio 14.0.0.0 PIA's don't work with the VBE PIA.

You'll have to get @RubberDuck to post them.

Ok. I think I can do that tonight. I think

no rush

BTW, @Mat'sMug, Project supports Run().

Nice!

[Hosch250/ResxEditor] Hosch250 pushed commit 877c35a3 to master: Load list of comments.

[Hosch250/ResxEditor] Hosch250 pushed commit 54c5a272 to master: Whoops, I broke my build.

[rubberduck-vba/Rubberduck] ckuhn203 commented on RetailCoder.VBE/UI/DockablePresenterBase.cs of pull request #746: Logging support

[rubberduck-vba/Rubberduck] ckuhn203 commented on pull request #746: Logging support

> For posterity, only the NLog and Moq packages were updated.

[rubberduck-vba/Rubberduck] ckuhn203 commented on pull request #746: Logging support

[rubberduck-vba/Rubberduck] ckuhn203 opened issue #747: Not recieving AppVeyor build notifications

> I'm still getting build notifications emailed to me, but they're not showing up on GitHub or chat.

[rubberduck-vba/Rubberduck] ckuhn203 added label meta to issue #747: Not recieving AppVeyor build notifications

[rubberduck-vba/Rubberduck] ckuhn203 added label critical to issue #747: Not recieving AppVeyor build notifications

[rubberduck-vba/Rubberduck] zippy1981 commented on pull request #746: Logging support

> Ok so if I put the retry back and add the event ID to the installer is this mergable?