I cloned it. Tried looking at the UI XAML and got The member 'Foo' is not recognized or is not accessible. and The name "Bar" does not exist in the namespace "clr-namespace:Rubberduck.UI.FindSymbol".
> Hi, I've just uninstalled and reinstalled Rubberduck, and still get the same error, seems I'm missing git2-15e1193.DLL. Is there anything I can do about this to fix it?
> Please give more information. That OS and host app are you using. Which version have you installed. When exactly did it throw that error (which steps did you follow to reproduce it).
> Please give more information. What OS and host app are you using. Which version of RD have you installed. When exactly did it throw that error (which steps did you follow to reproduce it).
> I'm on Windows 7 Enterprise SP1 64 bit, I've just reinstalled Rubberduck 2.1.1.2532. If I open the source control window, it doesn't spot changes in the modules, so I have tried to open an existing repository and create a new repository. The error occurs on invoking either of those.
> I'm on Windows 7 Enterprise SP1 64 bit, Excel in Office Professional Plus 2013, and I've just reinstalled Rubberduck 2.1.1.2532. If I open the source control window, it doesn't spot changes in the modules, so I have tried to open an existing repository and create a new repository. The error occurs on invoking either of those.
@NelsonVides you might want to check the installer script to see if it needs updated. I didn’t see any mods in your PR. It might also be worthwhile to see what SHA v1.85 of libgit2 relates to.
This here is strange - stackoverflow.com/questions/47775959/… - it seems that if you can compare two instances of a class then .Sort() should be working as well or?
so yes, this is happening here: github.com/rubberduck-vba/Rubberduck/blob/… it's indeed copying that dll alone. Strange thing is that updating libgit2shapr didn't change the dependency on its nativebinaries, it was still the 1.0.085 version, so this shouldn't have change. But I'm very lost here, is there anybody to help me? :/
@IvenBach IDK if you knew already but it has been reported here and there that Rebuild, which is supposed to be basically Clean and Build doesn't always blow away all the crud correctly. For that reason, you may get better results with a separate Clean and Build (or Rebuild) actions.
SQL Clause is Coming to Town!
You better apply updates
You better not cry
You better backup
I'm telling you why
SQL Clause is coming to town
He's created a database
He’s checking it twice
SELECT * from contacts WHERE behavior = 'nice'
SQL Clause is coming to town
His exec requests are sleeping
His cardinality estimates are wrong
Seven billion rows to see if = bad or good
So update stats for goodness sake!
O! You better apply updates
You better not cry
You better backup
I'm telling you why
From what I recall it's best not to have RD installed while using VS to test bug fixes. I uninstalled RD and only have the local repo. I can't recall how to get RD to work when debugging.
for VBE add-ins to be registered, VBE has to be explicitly told that this COM class here in this yonder DLL can be invoked as a VBE add-in. Thus you need more registry keys just to tell VBE about that addin
and because VBE "speaks" COM, it has to be a COM-compatible library
but not all COM objects are VBE add-ins
RE: the question of blueprint --- more or less yes.
Which is why you can directly reference some DLLs (e.g. you could reference EXCEL.EXE or MSACC.OLB or scrrun.dll)
no no that's the thing, it simply doesn't do embedded, period.
to embed the TLB in your custom DLL, you gonna add a post build step
which is too complicated to do
But that's why when you add references via the VBE's Tools - References, it would sometime tell you it can't reference a given DLL but would accept another DLL, even though it's the same file extension. Because it's missing the type library. Most of native win32 DLL don't have a type library (nor will they ever) and not all .NET assemblies will have a type library, so you would be unable to reference those directly.
IDK what ivenBach did to push but if he was using client tools, rather than Github, a push to forked repo would be OK, as PR can be then made. OTOH, a push to the rubberduck-vba => merge this thing right now, screw PRs!
the concept of PR just doesn't exist in the git world.
1) pull from rubberduck-vba/rubberduck:next
2) switch to a new branch "foo"
3) commit to bclothier/rubberduck (to update the branches)
4) work on the branch, commit as necessary. (smaller commits are generally better)
5) push to bclothier/rubberduck:foo
6) use github to create a pull request
a) the base should be rubberduck-vba/rubberduck:foo
b) the head should be bclothier/rubberduck:foo
While the PR is open....
Any subsequent pushes to bclothier/rubberduck:foo will synchronize the PR
**A** push to rubberduck-vba/rubberduck:foo will close the PR
@IvenBach simply replace bclothier with Ivenbach, foo with whatever branch you're using and you have it basically.
@Vogel612 probably won't need it if you don't screw it up in the first place. :)
@Vogel612 Perhaps but in my case I'm working on several different repositories for project, I like being able to review branches and history before I commit; no way to remember them all by memory.
and also lazy
I'll grant this much, though - it pays to know the underlying commands. Otherwise it's just a glorified button to do wrong thing.
@Vogel612 tried the git diff HEAD and to be honest, it feels more work to read through the changes than seeing it via Tortoise's diff tool which presents the changes in a similar format to what Github does.
> Sometimes when I select a block of code and then try to "Refactor Extract Method" it does nothing. I assume this is because it can't refactor my selected block for some reason. It would be helpful if Rubberduck told me why it couldn't refactor that block of code.
> What version are you using? Extract Method was originally shipped in v1.2, removed in v2.x, and is currently being re-rewritten (it's... a complicated one :wink:) - long story short, I don't expect the current WIP implementation to have released.. or did you build your own ducky from the source code?
Rubberduck version: Version 2.1.1.2532 Operating System: Microsoft Windows NT 6.1.7601 Service Pack 1, x64 Host Product: Microsoft Office 2010 x86 Host Version: 14.0.7191.5000 Host Executable: EXCEL.EXE
VBA Rubberducking
VBA Rubberducking