I wonder how Option Compare is implemented. It's a language construct, but only valid in Access. Presumably that needed some special-casing in the VBA compiler?
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5387?src=pr&el=h1) Report > Merging [#5387](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5387?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/dc732efef8fb3a7ced16e4af16e3257ed10fea11?src=pr&el=desc) will **increase** coverage by `0.17%`. > The diff coverage is `86.6%`.
@IvenBach Since my PR conflicts really bad with your extract interface refactoring, shall I add the part inside the extract interface refactoring action in my PR?
@mansellan Option is the language-level statement; the token that follows it is probably language-level too, but the host might be allowed to provide some... I suppose. Indeed, a good question.
@MathieuGuindon Unless I'm missing something, that's still library-specific? It'd be an inspection for Sheets("Sheet1")? and Sheets is from the Excel library?
related: there are 2.5 VBE's - VBA, VB6 and VBA-in-ODE-mode
I have a bunch of issues I could raise for [ode-specific], but I suspect they'd have exactly zero users. Unless, of course, it turns out that switching on ODE mode in Office 2019 yields some magical outcome I haven't located yet...
I was hoping that rainbow would be "make 64-bit DLLs with VBA", but it's eluded me.
@MathieuGuindon Not sure that's true... Suspect I may have been the first to stumble on the realisation that ODE is just a reg key away, even today.
Stumble being the operative word
Tbh I probably have more to look into. In ODE mode, there's temporary files emitted and an external linker, both of which could yield clues. If I knew how to examine for pointer sizes it would answer it definitively one way or another.
Apparantly one can attach the MSVC 6 debugger to VB native-mode modules, perhaps that is worth exploring
VB and MSVC were very close in their toolchains at v6 it seems
> @retailcoder - glad it was helpful. :) Is there an alert list i can subscribe to for this fix so that my colleagues and myself can return to download Rubberduck when it is useable with Inventor?
> @danny-boy-online you can watch this repository for new releases (or just watch it in general). Note that every pull request we merge gets a prerelease, so it might be a few notifications, before it works.
As it is, you should be automatically notified when this issue gets closed, because you commented here :)
> Not sure if it should be a separate issue or not. The indenter puts additional indent after a comment which contains a colon followed by "do", like this: `Private Sub SomeSub() AnotherSub AndOneMoreSub 'important comment: do not get surprised when line below gets an extra indent WronglyIndentedSub End Sub`
@mansellan What is VBA-in-ODE-mode? The interwebz return info about VBA 'code' and VBA mode and VBA Mod, but nothing about ODE mode. Unless, of course, my DDG-fu is weakened...
> Update: I just loaded up a new Excel workbook, added some fluff code, added the reference to `bin\rxinventor.tlb` and it was able to parse & resolve the project.
I tried adding: ``` Public Sub doit() Dim x As Inventor.AddInAutomation Dim y As Inventor.Document
Debug.Print "hi" End Sub ```
and it still resolves. :\
I tried the `bin32\rxinventor.tlb` just to make sure it wasn't being weird but was unable to load (which I expect since Excel is 64-bit).
> I also noticed that there's a definition for an add-in object. Is it the case that when you load Excel, you also have a Inventor add-in available to you in either Excel or VBA addins (note those are 2 separate kinds of add-ins, with separate managers; so we need to check both places). It might actually be the add-in that is causing problem. We can verify this by unloading the add-in from the add-in manager then reference the library only. If it resolves, then the problem is definitely with the
@FreeMan what @this said, but also it's possible to turn modern versions of Office into developer edition by adding one value to the registry. Unfortunately I can't share that value, as it's the license key. But I do plan to document what happens when the mode is activated.
> As it stands, this change is breaking some unit tests that were expecting a trailing newline to be present. I would also argue in favor of a module ending with a single newline to simplify editing it.
The unit tests need to be fixed before this can be merged, I don't particularly care about the newline at the end, but there is merit to having an EOL-EOF combination at the end of a module, if only because it's somewhat conventional to have that.
> > Update: I just loaded up a new Excel workbook, added some fluff code, added the reference to `bin\rxinventor.tlb` and it was able to parse & resolve the project. ... > Can you please confirm that this issue exists even with the latest version of Rubberduck?
@bclothier - the OP and I are using the latest official release 2.5.0.5244. Which version are you using so that i can download and try the one you are using and report back pls?
> > there's a definition for an add-in object. Is it the case that when you load Excel, you also have a Inventor add-in available to you in either Excel or VBA addins (note those are 2 separate kinds of add-ins, with separate managers; so we need to check both places). It might actually be the add-in that is causing problem. We can verify this by unloading the add-in from the add-in manager then reference the library only. If it resolves, then the problem is definit
> @Vogel612 , @bclothier I've updated RD to the latest you recommended (v2.5.0.5338) . I still get the same error as you can see in screenshot. 
I had noticed in his screenshot, his excel workbook was saved as a xlsm. Tried using a saved xlsm. No luck.
Even unblocked the file (since it was downloaded from internet) in case it matters (I kind of doubt it because if it did, VBIDE wouldn't have been able to load it in first place but have to be sure)
pasted the code, reparsed, and got the resolution error
hold on, pulling the log
2020-02-20 10:47:39.5127;WARN-2.5.0.5244;Rubberduck.Parsing.VBA.ReferenceManagement.CompilationPasses.TypeAnnotationPass;Failed to resolve type VBE;
2020-02-20 10:47:39.5197;ERROR-2.5.0.5244;Rubberduck.Parsing.VBA.ReferenceManagement.ReferenceResolveRunnerBase;Exception thrown on resolving those modules: 'VBAProject.Module1' (thread 64).;System.NotSupportedException: Unexpected context type Rubberduck.Parsing.Grammar.VBAParser+ExpressionContext
à Rubberduck.Parsing.Binding.TypeBindingContext.BuildTree(Declaration module, Declaration parent, IParseTree expression, IBoundExpression withBlo…
``` Version 2.5.0.5244 OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64 Host Product: Microsoft Office x64 Host Version: 16.0.12430.20264 Host Executable: EXCEL.EXE ```
Now the bad news is, I don't have a RD debug build on this machine, so I'm not sure exactly what's going on with the resolver, but I can confirm that removing the .tlb reference makes the parse run to completion.
From the logs and stack trace it looks like the .tlb was succ
> Repro also confirmed with the latest pre-release built (x64):
``` Version 2.5.0.5338 OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64 Host Product: Microsoft Office x64 Host Version: 16.0.12430.20264 Host Executable: EXCEL.EXE ```
Steps taken:
- Fire up Excel (with a new, empty, unsaved workbook), bring up the VBE - Rubberduck parses the project; go Tools > References, locate the .tlb, add it - Adding the library did not trigger an automatic reparse (?); hit "Ready" to pa
@this I actually saw that the other day. He was walking down the street pushing his shopping cart. Instantly thought of you with your hat and belts-n-suspenders, but in the good way.
turns out that "fixing" csproj was the cause for the borken
It was modified and had lines like <Page Remove="UI\Styles\LightBlueTheme.xaml" />
I did not add them myself and thought it was unnecessary and removed it. That caused VS to try and compile those XAML files as a Page rather than Resource
(despite the explicit lines further down where we have <Resource Add="..." />)
INTUITIVE!
it didn't help that the error it threw did not even come anywhere to suggesting that the XAML files were pages, not resource. It just hollered about not finding the Infalution XAML.
I'm doing some code revision and I'm looking at this portion of my Worksheet_Change() event:
If Target.Address = "$A$4" Or _
Target.Address = "$A$7" Or _
Target.Address = "$A$10" Or _
Target.Address = "$B$21" Or _
Target.Address = "$B$22" Or _
Target.Address = ...
@MathieuGuindon codereview.stackexchange.com/a/237197/131748 links to your RD post 'The Macro Recorder Curse'. Little traction every day Mug. Keep that #IndustryDisruptor ball rollin'.
FML, someone used "l" as a variable (i, j, k, l, m, & n) in this module... time to refactor everything and hope that it doesn't break the module
one thing i've noticed when refactoring, if the line of code is already about at the end of the module, it will push characters to the next line causing a parse error, which causes all sorts of fun
as in a completely blank module is present; scary unti lyou realize somethign RD is doing can just be ctrl+Z'd back to where you were
at least i found a consistent way to break VBIDE with RD
holy F it saved... oh no
So, i guess RD copies all of the content from a module, deletes the module, creates a new one, and pastes into it with the refactored name? because my module is gone.
I was in break mode while running a test. I got called away for a while. When I came back I went to resume debugging and hit F8. The application "working circle" started spinning. Then the entire Excel session closed. I then got a warning that Malwarebytes had blocked the RD logging.
Now in the RD "About" the link to the Logs folder goes to the Computer in Windows Explorer; nowhere near the Logs folder, which apparently Malwarebytes removed!
But to get RD running again I installed the latest version and thought it would "repair" the path. I went into my Malwarebytes settings and whitelisted the path after recreating the path. The button in the settings pane found the folder.
Any suggestions on how to "fix" my laptop? I updated RD, opened XL and the VBIDE, did a Refresh. Shouldn't that activity have created a logfile (it didn't)?
and figure out how to get RD back to normal. I've closed XL and reopened it to the VBIDE a couple of times and still don't have config or anything except an MT Logs folder...
@MathieuGuindon in checking %temp% i didn't see any .bas file enclosed (assumes a .bas was exported). there is a rubberduck folder in there thta had no content. is it possible that RD uses a kill/quit/delete for the exported file?
i ended up pulling my archive and using a backup from 0800, so that module in particular had few if any significant changes (was just starting to refactor it when i noticed all of the fun and had the IDE crash)
I'm doing some code revision and I'm looking at this portion of my Worksheet_Change() event:
If Target.Address = "$A$4" Or _
Target.Address = "$A$7" Or _
Target.Address = "$A$10" Or _
Target.Address = "$B$21" Or _
Target.Address = "$B$22" Or _
Target.Address = ...
VBA Rubberducking
VBA Rubberducking