For this build, I should have the AWE (or LLA?) activated by default? I didn't find it in the settings.
Yeah. It's more and more sluggish. :-/
I even saved it in .xlsb.
3rd crash. Again after automatic fix (for option explicit missing)
Well,a fter I opened --only-- the "show memory xlsb", it shows
So the project I work on has only 0.39 GB? But what the hell is the default 1GB of virtual Memory..
So it looks like the memory is the issue? Now, on the first try, it won't even parse (it parsed on the second try)
2019-04-02 02:17:02.7594;INFO-2.4.1.27739;Rubberduck.Parsing.VBA.RubberduckParserState;RubberduckParserState (5) is invoking StateChanged (Error);
2019-04-02 02:17:03.4342;ERROR-2.4.1.27739;Rubberduck.Parsing.VBA.ParseCoordinator;Unexpected exception thrown in parsing run. (thread 7).;System.AggregateException: One or more errors occurred. ---> System.OutOfMemoryException: Exception from HRESULT: 0x800A0007 (CTL_E_OUTOFMEMORY)
at Microsoft.Vbe.Interop._VBComponent.get_Designer()
And it took 54 seconds
2019-04-02 02:18:38.8214;DEBUG-2.4.1.27739;Rubberduck.Parsing.VBA.RubberduckParserState;Module 'frmLoadRegime' state is changing to 'Ready' (thread 12);
2019-04-02 02:18:38.8214;DEBUG-2.4.1.27739;Rubberduck.Parsing.Common.ParsingStageTimer;Resolved references in 597ms.;
2019-04-02 02:18:38.8504;DEBUG-2.4.1.27739;Rubberduck.Parsing.Common.ParsingStageTimer;Determined module to module references in 25ms.;
2019-04-02 02:18:38.9913;INFO-2.4.1.27739;Rubberduck.Parsing.VBA.RubberduckParserState;RubberduckParserState (14) is invoking StateChanged (Ready);
Aaaand after trying to fix a warning (vbnullstring instead of ""), crashed again :-(
That's weird. It's truth I wasn't working on my project for 2 months but before there were no problems of this type :-/
This is the last debug log just before crashing
2019-04-02 02:22:32.5553;WARN-2.4.1.27739;Rubberduck.Parsing.Symbols.IdentifierReferenceResolver;Default Context: Failed to resolve 10 + (.Width * dist) * (i - 1) - _
(.Width * dist) * Int((i - 1) / btnsInR) * btnsInR. Binding as much as we can.;
2019-04-02 02:22:32.5553;WARN-2.4.1.27739;Rubberduck.Parsing.Symbols.IdentifierReferenceResolver;Default Context: Failed to resolve ThisWorkbook.Path & "\resource\pictures\lomo_" & Format$(i, "00") & ".gif". Binding as much as we can.;
This is the "Increasing Number problem". Where we are looking for all numbers with N digits where each digit is bigger than the digit before it. Or in Mathematical therms where:
And
Examples: 123456789 or 123 or 569 or 139 or 45 or 12379. Goal: Give out all numbers that fullfill these pro...
After thinking about it, I ended up simply overriding the OnExecute and EvaluateCanExecute in the ComCommandBase, sealing them both, then require the child classes to implement SafeOnExecute and SafeEvaluateCanExecute. That does not require me to modify CommandBase, which I didn't want to do. Not as pretty since child classes must use different methods but that'll address the issues, I think.
Const FOLDERPATH As String = "\ITSEASY"
Const DATAFOLDER As String = "\AS"
Const OLDDATAFOLDER As String = "\ABC"
Public Sub ExportData()
Application.ScreenUpdating = False
'GET DROPBOX PATH
Dim TheDropBoxPath As String
TheDropBoxPath = DropBoxPath.GetDBPath
Dim files() As Variant 'STARTS AT 1
f...
I think I remember why I did not want to do the Safe*** approach - that would have left the derived classes with two methods, increasing the mental load to use. I wanted to use the EvalulateCanExexcute and OnExecute so the child classes can still behave as if it was just ComCommand but with additional constraint enforced by ComCommandBase. I'm changing the code in the Code Explorer commands and it's not pretty since it has lot of references to the base.EvaluateCanExecute...
hmm, if I'm reading this right, the RefactorCommandBase still exposes EvaluateCanExecute; child classes can override that.
even though they should actually use AddToCanExecuteEvaluation to customize the behavior
The issue I have with CE items is that they have calls to base.EvaluateCanExecute, which must be changed to base.SafeEvaluateCanExecute to avoid infinite recursion and therefore a stack overflow.
As a matter of fact, the tests are now aborting with a StackOverflowException because I missed a base.EvaluateCaneExecute somewhere. Even more fun, NUnit does not deign to tell me which test.
I think it would be best to change the CommandBase to the setup of the RefactoringCommandBase. Otherwise, it cannot be enforced that the derived classes honor the execution conditions of the base class.
That would be a separate PR, though.
I also do not like that we have to pass a logger to the CommandBase.
The point of my setup is that you do not have to invent a new CanExecute method for each level of the hierarchy.
> **Rubberduck version information** The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:
Rubberduck version 2.4.1.4627 Operating System: Win 10 Host Product: Microsoft Visual Basic 6.0 Host Version: [...] Host Executable: [...]
**Description** It seems vb6 allows a semi colon on the Print line to suppress CRLF. It seems to be an exception but it is making parsing fail on my [very old and large] code base.
> Thanks for the feedback! This parser bug has been reported as part of another issue last week - let's keep both open, and make the older one specific to the issue with `Line` statements.
@this I seem to recall find all refs being kind of broken for interface members, but are you saying direct references to ISomething_DoSomething should count as references to ISomething.DoSomething? IMO they shouldn't
hey @Vogel612, I saw you had linked commits to #4875 (for the Line syntax), so I assigned it to you - the semicolon bug should be addressed separately :)
> Since #4888 is now about the second part of the issue this references, this PR is now considered a fix for #4875 instead of only partially fixing it.
the good news is that Print seems to be a reserved identifier, so we have a way of forbidding it as a member call while crafting a similar rule that allows trailing semicolon and comma tokens when something looks like a member call but the member is Print
> Expr Required String The string expressions to print. If this argument is omitted, the Print method prints a blank line. Multiple expressions can be separated with a space, a semicolon (;), or a comma. A space has the same effect as a semicolon.
this is a compile error, though; whereas this compiles:
Dim r As Access.Report
r.Print "ab"; "cd"
if it's not at COM level, the only way I could see this working is that it's VBA hijacking the Print and consuming the expressions before ultimately calling the Print with all the combined expressions.
> So I made a quick little DLL to try and see how the VBE actually works, made it COM-visible, exposing a `Print` method:
The `Print` member gets keyword syntax highlighting, which is a tell-tale sign *something* is going on at the language level. The code compiles, but running it throws run-time error 438 "member not found"; invo
i tried to check whether the print had effect between loop but I cannot see the actual output - it doesn't happen until the procedure has exited so I have no way of knowing if it was in fact rendering something between the call or not
the question is more about the maintenance - there are different solutions out there that supposed to keep the doc automatically in sync with the code changes
hey @user10792291 - I'm just looking at your recent question on SO -- you'll want to edit it to include the actual error, and whether the myFile variable contains a legal existing file name. Side note, I'd recommend capturing the returned Workbook object into a local variable: Set wb = Workbooks.Open(myFile), that way you can work with wb instead of working out which object in the Workbooks collection is the workbook that was just opened.
"The new loading system introduces a potentially massive range of edge cases, as the extension can now be loaded at any time by the IDE, potentially very late in the session"
Hey, who knew - the VBE had an async loader years ahead of VS, apparantly ;-)
> Another change introduced in VS2019 of a more controversial nature is the new Extensions menu. From VS2019, extensions are no longer allowed to create their own top-level menu inside VS. Instead, all extension menus are grouped together in a separate menu where they can no longer be accessed through a single mouse-click or shortcut key. This affects us significantly, as it does other productivity centric extensions (i.e. ReSharper, CodeRush, JustCode, etc).
Looks like RD made the right call (not that it matters since it's VBE, not VS but still)
@Vogel612 thinking it stuck around because we said maybe it would be useful for the eventual custom code panes... but then, it's probably better to just make a setting for it (we'll want that setting anyway)
@this heh sorry was an attempt at humour. The new VS2019 loader is causing headaches to extension writers due to its nondeterministic timing. Just sounded familiar :-)
But, pretty sure you can tell the start dialog to never show.
> Of course, we understand that some users may prefer going straight into the IDE and doing what they’re used to doing to load code. We provide a way to turn off the new window in Tools > Options > Startup > On startup, open, and choosing something other than the start window. To get the old Start Page back, simply select the “Start Page” option.
You can. You can also kinda get the start screen back, manually on the File menu (have to delete and readd the command). But the dev news feed doesn't work - says to change an Options setting that's no longer there
Well either way, I'm gonna give try it as my daily driver at work. I'm sure there are some actual improvements in there somewhere...
I think I can get the top-level menu back by manually recreating the entire structure manually, and adding every single R# command individually. Thanks MS :-)
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
namespace XAMLBuildErrorExample
{
class MyDataClass
{
}
}
1>------ Build started: Project: XAMLBuildErrorExample, Configuration: Debug Any CPU ------
1>Build started 4/2/2019 12:56:04 PM.
1>GenerateBindingRedirects:
1> No suggested binding redirects from ResolveAssemblyReferences.
1>C:\Users\cpaustell\source\repos\XAMLBuildErrorExample\XAMLBuildErrorExample\MainWindow.xaml(10,10): error MC3074: The tag 'MyDataClass' does not exist in XML namespace 'clr-namespace:XAMLBuildErrorExample'. Line 10 Position 10.
1>
1>Build FAILED.
1>
1>"C:\Users\cpaustell\source\repos\XAMLBuildErrorExample\XAMLBuildErrorExample\XAMLBuildErrorExample.csproj" (Build;Buil…
This is the "Increasing Number problem". Where we are looking for all numbers with N digits where each digit is bigger than the digit before it. Or in Mathematical therms where:
And
Examples: 123456789 or 123 or 569 or 139 or 45 or 12379. Goal: Give out all numbers that fullfill these pro...
VBA Rubberducking
VBA Rubberducking