VBA Rubberducking

Duga

00:01

RELOAD!

[banane-io/PDB] 2 commits. 31 additions. 3 deletions.

[Cardshifter/Cardshifter] 1 commit. 1 opened issue. 21 additions. 3 deletions.

[Cardshifter/HTML-Client] 9 commits. 4 opened issues. 7 closed issues. 17 issue comments. 1053 additions. 848 deletions.

[FreezePhoenix/XtraUtils] 30 commits. 572 additions. 3243 deletions.

[rubberduck-vba/Rubberduck] 10 commits. 3 opened issues. 4 issue comments. 2895 additions. 2439 deletions.

[Zomis/Server2] 1 opened issue. 3 issue comments.

Peter M Taylor

08:02

hmm...okay have grabbed the latest build from next. Failed with 428 errors. Interesting a warning message says Severity Code Description Project File Line Suppression State
Warning AD0001 Analyzer 'Microsoft.CodeAnalysis.CSharp.Analyzers.FixAnalyzers.CSharpFixerWithFixAllAnalyzer' threw an exception of type 'System.TypeInitializationException' with message 'The type initializer for 'Microsoft.CodeAnalysis.Analyzers.FixAnalyzers.FixerWithFixAllAnalyzer`1' threw an exception.'. RubberduckTestsCodeAnalysis C:\Users\Peter\Source\Repos\Rubberduck\RubberduckTestsCodeAnalysis\CSC 1 Active

checking the chat notes if anyone had discussed how they go about resolving this.

I had ensure I have some C++ code. I think I may need more C++ libraries.

Vogel612

09:17

@PeterMTaylor the build should work without C++ tools

what version of Visual Studio are you running?

Peter M Taylor

good evening @Vogel612 I assumed from the wiki that I had to include some C++ tools

Vogel612

no, those tools are optional

they help register the build, but they're not strictly speaking necessary

Peter M Taylor

VS Community 2017 Version 15.7.2

Vogel612

because if they're not present we're falling back to tlbexp

@PeterMTaylor hmm ... that should work. I assume you did Set-ExecutionPolicy RemoteSigned?

Peter M Taylor

yep I had initally. I'll redo that step again\

Vogel612

09:21

428 errors seems rather harsh. It should build just fine with a bit less than 100 warnings..

The changes I made recently kinda added to the warning count, because I marked some stuff as obsolete

Peter M Taylor

yeah its a small pile. 0.0

rebuilding now

same 428. Um, its the bolding on Rubberduck.Parsing any importance?

Severity Code Description Project File Line Suppression State
Warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "olewoo_interop", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.…

I know that this had implemented a script to include libraries from olewoo for deployment

Vogel612

I have the same warning. Twice IIRC

Peter M Taylor

I was able to be flexible about sorting the errors out of the 428 got 5 RoslynHost errors.

Severity Code Description Project File Line Suppression State
Warning IDE1001 The analyzer assembly 'C:\Users\Peter\Source\Repos\Rubberduck\RubberduckCodeAnalysis\bin\Release\RubberduckCodeAnalysis.dll' has changed. Diagnostics may be incorrect until Visual Studio is restarted. Rubberduck.VBEditor 1 Active

Vogel612

sounds like a restart of VS is in order...

Peter M Taylor

okay. onto it captain!

Peter M Taylor

09:44

okay. no change for rebooting PC to be sure.

still 428 errors.

interesting XML errors. Severity Code Description Project File Line Suppression State
Error The type reference cannot find a public type named 'EndOfLineCommentStyle'. Line 20 Position 34. Rubberduck.Core C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.Core\UI\Settings\IndenterSettings.xaml 20

Vogel612

~confused

Peter M Taylor

agreed.

Severity Code Description Project File Line Suppression State
Warning CS1762 A reference was created to embedded interop assembly 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' because of an indirect reference to that assembly created by assembly 'office, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'. Consider changing the 'Embed Interop Types' property on either assembly. Rubberduck.VBEditor.VBA C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.VBEditor.VBA\CSC 1 Active

I recall a conversation with Ivenback about Interop

couldnt find it that this may have clarified and suggested...

Vogel612

try to find the first project in the build order that errors out. These may result in cascading error messages across the solution

Peter M Taylor

okay

Vogel612

Rubberduck.VBEditor.VBA seems like one possibly culprit

Peter M Taylor

09:49

turned off my grouping of error and approaching a waterfall fashion.

my first error is this one.,,

Severity Code Description Project File Line Suppression State
Error CS0246 The type or namespace name 'VBAParserBaseListener' could not be found (are you missing a using directive or an assembly reference?) Rubberduck.Parsing C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.Parsing\Annotations\AnnotationListener.cs 8 Active

M.Doerner

You did clean, then rebuild, right?

Peter M Taylor

yes definitely each time so far. always clean first then rebuild.

Peter M Taylor

10:06

no idea what to look for now...

Severity Code Description Project File Line Suppression State
Error CS0115 'AnnotationListener.ExitAnnotation(VBAParser.AnnotationContext)': no suitable method found to override Rubberduck.Parsing C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.Parsing\Annotations\AnnotationListener.cs 23 Active

Vogel612

that seems rather weird ...

Peter M Taylor

I found the solution file .sln had the parser file in bold.

lots of bits missing that appears to be dependent on.

i see that VBAParser is expecting certain attributes...including statements. Doing a search of that name against next history. its been in place from Dec 2017...so changes I think refactoring took place. I haven't followed the git trail well

MemberAccessExprContext is another VBAParser

anyhow. got three of these warnings...

Severity Code Description Project File Line Suppression State
Warning Unknown build error: The system cannot find the file specified Rubberduck.Parsing

its funny its not telling me which file is missing....

M.Doerner

10:27

The parser file should get generated via a build action, IIRC.

Has there been a change to the lexer or the parser?

It will not be there if antlr is unable to build the parser from the grammar.

Peter M Taylor

the last change made to ANTLR was 15 days ago

was not sure if the .g4 files were meant to be generated so the build in VS takes them in...

Severity Code Description Project File Line Suppression State
Error CS0006 Metadata file 'C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.Parsing\bin\Debug\Rubberduck.Parsing.dll' could not be found Rubberduck.SmartIndenter C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.SmartIndenter\CSC 1 Active
Error CS0006 Metadata file 'C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.Parsing\bin\Debug\Rubberduck.Parsing.dll' could not be found Rubberduck.Refactorings C:\Users\Peter\Source\Repos\Rubberduck\Rubberduck.Refactorings\CSC 1 Active

pardon my frustration just a sample out of 420 errors from last build

Vogel612

these missing dll errors are a cascading effect from the actual problem

Peter M Taylor

okay so VBAParser or lexer changes?

Vogel612

10:43

again: next does just build just fine for me

it shouldn't be the VBAParser or VBALexer

M.Doerner

It builds for me, as well.

Peter M Taylor

:(

then its a local PC configuration...unable to build correctly...I'll resync Next...

M.Doerner

I'll update my vs and see if it still builds.

I am on 15.6.6.

Peter M Taylor

I'm on 15.7.2

just a habit to also do VS installer when I did a Win10 feature update.

Git tells me no further changes so I am update with next.

okay I got to go get my kid ready for her school tomorrow. I'll reattempt build and am open to any suggests to reconfig.

tomorrow. good night/morning everyone. catch ya soon.

just another go tomorrow night to get my development of next work...

bye

Duga

13:45

[rubberduck-vba/Rubberduck] mansellan added label parse-tree-preprocessing to issue #4045: VB6 COM documentation issues

[rubberduck-vba/Rubberduck] mansellan opened issue #4045: VB6 COM documentation issues

> Several type libraries commonly used by VB6 fail to fully load COM documentation, leading to names not being set. Need to examine how OleWoo handles these so that references are loaded correctly.

[rubberduck-vba/Rubberduck] mansellan assigned mansellan to issue #4045: VB6 COM documentation issues

[rubberduck-vba/Rubberduck] mansellan added label vb6-specific to issue #4045: VB6 COM documentation issues

[rubberduck-vba/Rubberduck] mansellan assigned mansellan to issue #4046: VB6 project events not working

[rubberduck-vba/Rubberduck] mansellan added label vb6-specific to issue #4046: VB6 project events not working

[rubberduck-vba/Rubberduck] mansellan opened issue #4046: VB6 project events not working

> Several project-level events (Project load \ unload etc) not functional in VB6.

Son Goku ssj4

16:43

@this hi, will be at home in 3 hours. Would you want to continue with the team viewer meeting?

this

20:11

@SonGokussj4 i'm around now

@PeterMTaylor One way to help narrow down the cascading errors is to do a clean, then build project individually in the same build order. I usually start with Rubberduck.VBEEditor project then go from there. You can see the build order via the solution properties and build project in the same order.

It might be also related to the fact that .NET 4.6 is now needed, too.

Duga

20:40

[rubberduck-vba/Rubberduck] bclothier created comment on issue #4041: Discussion: COM Shims

> Just to keep things in perspective:

Having 2 shims is not a problem per se because we already use separate registry paths for each 32-bit and 64-bit. It would be a matter of handling it within the installer script since we now install both 32-bit and 64-bit unconditionally. As a matter of fact, we already are exporting both 32-bit and 64-bit TLB files for that reason.

The documentation on COM shims are somewhat dated and as such, need to be taken with a grain of salt. For example, it ta

Transcript for