« first day (277 days earlier)      last day (2903 days later) » 
00:00 - 19:0019:00 - 00:00

19:02
> Thanks @danwagnerco. Don't use the reg files in the root directory. The build instructions need to be updated. Here is the one key that should be needed. Visual Studio should handle the rest.

```
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\VBA\VBE\6.0\Addins\Rubberduck.Extension]
"LoadBehavior"=dword:00000003
"FriendlyName"="Rubberduck"
"Description"="Rubberduck add-in for VBA IDE."
"CommandLineSafe"=dword:00000000
```
> Found the article I was reading. Might have borked something when I built the installer.

(or simply didn't target 64 bit.)

http://blogs.msdn.com/b/vsto/archive/2010/04/09/deploying-com-add-ins-for-64-bit-office-using-visual-studio-saaid-khan-for-nathan-halstead.aspx
What did this poor soul see?
1
Q: Office 2013 Com Shim Add-in

Pawan KumarI have a Com Add-in for Office 07,2010 created in VS 2008 , .net 2.0. implementing IDExensibility2 and IRibbonExtensibility. Com Shim dll - C++ Rest all code -C# I need to upgrade this project to Office 2013, i have read online that it doesn't require any change, the same com add-in should work...

> It's possible the extension needs to be registered in the wow6432 node of the registry. If someone could try adding this key I'd be eternally grateful. ``` Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\VBA\VBE\6.0\Addins\Rubberduck.‌​Extension] "LoadBehavior"=dword:00000003 "FriendlyName"="Rubberduck" "Description"="Rubberduck add-in for VBA IDE." "CommandLineSafe"=dword:00000000 ``` It this solves the issue, I'll need to create a 64 bit version of...
the installer.
> :+1:
19:18
@RubberDuck can you do that tonight? I'll be at the office all evening tonight :(
@Mat'sMug Yeah. I think so... I'll have to reset a local branch back to that version.
(or just unleash 1.21 as is into the wild?)
note to self: uninstall Office 2010, and reinstall the 64-bit version. ASAP.
19:34
@Mat'sMug I was considering that too.
heck, why not?
> release early, release often
@Mat'sMug I hate it when my own words come back to bite me.
I don't like that I don't have a way to test a 64 bit installer though.... ugh.
Okay. So be it.
5 mins ago, by Mat's Mug
> release early, release often
@RubberDuck I have installed 32-bit on my x64 machine by accident, and thought "oh so be it" - I'll reinstall Office when I get a chance.
/ x64
That makes me feel a bit better.
so we'll have both versions
sorry I can't release that one tonight :(
and BTW, no pressure buddy - if you can't, you can't!
19:47
I might hold off until Dan Wagner checks things out.
Anything I do right now would be a guess.
19:58
The worst part is that I left my charger at home this morning, so I'll have to shut down my phone and go dark for a few painful hours!
@Mat'sMug @SimonKarfunkel says: Office 2010, 64 bit.
and it works?
> Simon says: Office 2010, 64-bit
It's the 64 bit version. Year doesn't seem to matter then.
huh? I'm lost here
The other Simon was having the same trouble the guys with 2013 x64 were.
20:17
ah
So, it's one of two things. I can fix both if I can get an hour or two this this evening.
awesome!
has to be x64
20:39
@Mat'sMug nope, it doesn't work. I guess it's a 64 bit thing.
definitely
chat is UTC time right?
looks like it's localized
maybe in the transcripts it's UTC though
Okay. News Post scheduled so I don't get myself in any trouble.
cool
(you're reading my mind here, it's scary)
20:46
@Mat'sMug Someday we will start a real Rubberduck Software Inc. and get people to pay us for our work.
I'm still floating on the "hats off" from the other side of the planet
First thing I did was call my wife.
lol
what'd she say?
She laughed and screamed.
screamed?
20:48
Like, in a good way.
> Hey @ckuhn203 / @retailcoder -- bad news. Either it's heavy user error or the registry key addition above is not the fix. Here are the steps I followed in my attempt: 1. Uninstall Rubberduck. 2. Create a test_registry_key.reg file on my desktop with the info above to make sure no dumb copy/paste errors happen. 3. Run > regedit from the command line. 4. File > Import then select the test_registry_key.reg file....
!image I then ran the Rubberduck installer and restarted, but unfortunately Rubberduck still does not appear as an Add-in option.
uh-oh
clue?
my guess is that the 32-bit installer is creating the required keys in the wrong place
> Dang. Thanks for trying @danwagnerco. I'm going to try building an installer targeted at 64x as soon as I have a moment. It could possibly be the Lib2git native binaries causing the issue on the 64 bit target. Or the current installer might be creating the required registry keys in the wrong place.
@Mat'sMug Out of my head man.
21:15
let's make that Japanese blog tell the world Rubberduck works with 64-bit Office then!
> Wait... Maybe not. @danwagnerco can you try creating the extension reg key under Addins64 instead of AddIns please?
^^ that should work
> [HKEY_CURRENT_USER\Software\Microsoft\VBA\VBE\6.0\Addins64\Rubberduck.Extension]
"CommandLineSafe"=dword:00000000
"Description"="Rubberduck add-in for VBA IDE."
"LoadBehavior"=DWORD:00000003
"FriendlyName"="Rubberduck"
> Hey @retailcoder -- I added that registry key but unfortunately now I can't open the VBE:

![image](https://cloud.githubusercontent.com/assets/6598675/6585880/38c0ecf6-c743-11e4-9518-2115c01505f7.png)

[cue the sad trombone from The Price Is Right...]

I'm going to delete that key for now.
> Oh wow, that's a new one! I'll set up a 64-bit Office instance as soon as I can, we'll get a 64-bit Office build to work, one way or another. Thanks for your help!
21:46
@SimonAndréForsberg what's the hashtag for fucking up like this?
#FML
21:59
> Yikes! Sorry @danwagnerco. Thanks for helping out. @retailcoder let me know when you're set up.
22:30
@Mat'sMug fucked up what?
we released 1.2 for 32-bit Office only; nobody running a 64-bit Office can use it!
@Mat'sMug that explains it :)
both @RubberDuck & I are working off a 32-bit Office... I need to reinstall Office when I get home, and I'm stuck at work for I don't know how long because we're having a late meeting at 7PM
ugh
@Mat'sMug you need to have a 64-bit Office in order to make a Rubberduck for it?
no, but to confirm that it's working before we release it, yes ;)
besides I always wanted to be able to declare a LongLong
(only in VBA x64)
22:40
that's true :)
well that was a bittersweet day
@RubberDuck ^^ I've updated the release page to say "32-bit Office" on the 1.2 release, and that we're working on getting a 64-bit Office build up.
perhaps we should tweet it
oh, I'm late to the game I see
RT'd
@rubberduckvba looks like there's an issue with x64 bit Office. https://github.com/retailcoder/Rubberduck/issues/305
lol forgot the feed
nevermind
22:59
Bitter sweet day indeed.
Users in Japan. Free ReSharper license.
Damn thing doesn't work in 64x Office...
how the heck did it take a whole week to figure that out...
Neither of us had a copy to test on. That's all.
^^ that
Not all days can be great days.
You are still doing really awesome things here.
I bet that users will also judge RubberDuck by your ability to handle situations like this.
Let's just hope some hiring managers think so.
Ducky still needs to find a new job.
If you handle it well, which I think that you do, you will be even more loved by users.
23:05
Waits for the localization requests
@RubberDuck Simon needs that as well.
And Simon too, in fact.
(I love it when there are two Simon's)
@RubberDuck in a couple of months (weeks?) when you tell a hiring manager that you're behind Rubberduck, they'll all fight to get you in!
@SimonAndréForsberg thanks :)
meeting aborted, we'll do it tomorrow instead. ugh, I'd be home by now!!!
TTQW
23:26
Lame dude...
23:59
RELOAD!
[retailcoder/Rubberduck] 3 commits. 1 opened issue. 1 closed issue. 22 issue comments.
[Zomis/GithubHookSEChatService] 1 issue comment.
00:00 - 19:0019:00 - 00:00

« first day (277 days earlier)      last day (2903 days later) »