Exception thrown: 'System.ArgumentException' in Rubberduck.VBEditor.dll
2018-09-20 19:15:25.0397;ERROR;Rubberduck.UI.Command.ReparseCommand;System.ArgumentException: Expected COM object, but validation failed.
at Rubberduck.VBEditor.ComManagement.TypeLibs.TypeLibWrapper..ctor(IntPtr rawObjectPtr, Boolean isRefCountedInput) in C:\Rubberduck\Rubberduck.VBEEditor\ComManagement\TypeLibs\TypeLibs.cs:line 196
at Rubberduck.VBEditor.ComManagement.TypeLibs.TypeLibWrapper.FromVBProject(IVBProject vbProject) in C:\Rubberduck\Rubberduck.VBEEditor\ComManagement\TypeLibs\TypeLibs.cs:line 176
Got that when I was triggering a reparse from the code inspections - clicked on "Disable this inspection".
Got some of these above it:
Exception thrown: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' in Rubberduck.Inspections.dll
Exception thrown: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' in Rubberduck.Inspections.dll
Exception thrown: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' in Rubberduck.Inspections.dll
Exception thrown: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' in Rubberduck.Inspections.dll
Exception thrown: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' in Rubberduck.Inspections.dll
``` Exception thrown: 'System.NullReferenceException' in Rubberduck.Core.dll **_wrapped** was null.
The thread 0x2d5c has exited with code 0 (0x0). System.Windows.Data Error: 17 : Cannot get 'FullMemberSignature' value (type 'String') from '' (type 'InterfaceMemberViewModel'). BindingExpression:Path=FullMemberSignature; DataItem='InterfaceMemberViewModel' (HashCode=42701800); target element is 'TextBlock' (Name=''); target property is 'Text' (typ
@IvenBach Not Run after running all tests usually means Inconclusive. (They should really introduce a separate bucked for it.) Most of the time it is the parser failing to parse the input code.
1) Was it intentional to delete [this inspection](https://github.com/rubberduck-vba/Rubberduck/pull/4383/files#diff-813398b2cd7dbff2cb0d3307ae86463e) 2) EasyHook files were apparently deleted. Is that intentional as well? I did not see a corresponding addition; only a `PackageReference`, and I am assuming we are now referencing the files in the `packages` folder which isn't a part of the git solution; but a bit unsure why files existed inside the projects originally.
Hi, sorry pointer question again........this link states: If you follow a string variable’s pointer you won’t actually get the start of a string. Instead, you’ll get another pointer. If you follow that pointer you’ll get the 5th byte of a BSTR structure, a COM Unicode string buffer.
So, what is that first pointer to? The offset storing the length info?
Earlier I told you(?) that the length is at negative offset. We prefer to pass around the pointer to the address of the 1st character so that it is compatible when we pass the same pointer to a API that expects a null-terminated string.
You did tell me. I am just going over everything that you guys shared with me trying to get it all to sink in along with doing extra reading.
Why is it called the COM Unicode string buffer? Said 5th byte. I know it is the start of the unicode data string. Is it simply buffer because it is the start?
IIRC, this is a convention by Automation specifications that VB6/VBA/other programs follow; all string must be Unicode.
Buffer is usually referring to the array of characters --- that is, a contiguous range of memory where we contain the string itself. Remember that the buffer is variable size so you have to know when to stop reading.
When you think about it, it's fairly important that the buffer be contiguous. you can come up with a different data structure where you have a piece of string here and another piece of string over there and that's totally legit. But that would be disastrous if you passed that data structure to the API which will want to do a sequential read from start to end
if we used only one 0x00 to terminate the string, we would terminate before we got to read the letter "A"
that's just one of many way to encode unicode. UCS-2 means that it's fixed width in 16 bits for all characters. This is different from say, UTF-8 for example where we may either use one or two characters depending on the character we actually use.
I have to profess I don't yet understand "so with letter "A" we have value of 0x0041 if we used only one 0x00 to terminate the string, we would terminate before we got to read the letter "A""
Dim s As String
Dim b() As Byte
Dim i As Long
Dim u As Long
Dim l As Long
s = "ABC"
b = s
l = LBound(b)
u = UBound(b)
For i = l To u
Debug.Print Right$("0" & Hex(b(i)), 2);
Next
you are correct about using it as a compact way to write a large number and it is often used with memory address, yes but there's a underlying reason to both of those
The same article states for String on allocation: The VB runtime truly creates a new copy of a string upon assignment. Both a new pointer (for the string variable) and a new BSTR structure (for the string’s value) are allocated. Then the contents of the source BSTR are copied to the destination BSTR, and the address of the new BSTR is written to the string variable’s content address.
And for deallocation: Deallocate the memory occupied by the target BSTR structure, and deallocate the pointer that constitutes the string variable itself.
So, an entire copy is made, fine. On deallocation the target (copy) is basically erased. What about the original?
@QHarr I'd have to see it in context, but I'd assume that it's describing marshaling behavior. The original string would be deallocated when it went out of scope.
> Re 1: That inspection had been removed from the csproj files, but not from the git working tree. It uses old API for inspections and refers to resources that have been removed. The move to the new csproj format (which uses globbing to include files) just surfaced that mishap.
Re 2: EasyHook (as well as NLog.Schema and possibly other NuGet Packages) pushed parts of the content they should add to the `/packages` directory to the solution content. That behaviour is apparently not supported for
> Error making request with Error Code ServiceUnavailable and Http Status Code ServiceUnavailable. No further error information was returned by the service.
Not sure you can do something about it? Retry or something?
@Duga "eliminates" feels a bit strong, given the only easy part is updating the git repo - updating the VBA project from the git repo is still bloody tedious
Duck check: Is it a best/preferred practice to have all images reference in a UserControl.Resources for xaml? Then just use Source={StaticResource Foo} when an image is needed?
turns out VB wasn't installed :P
make sure it is
in VS, go to tools -> options -> text editor -> file extension
add asp as the extension and pick Visual Basic as the editor
@IvenBach What I meant is that they should stop putting inconclusive tests into the same bucket as other tests. Previously, I think in VS2015, the test explorer showed them as ignored; now, it is not run.
literally the only difference between vbs and vba boils down to the data types (or rather the lack thereof) and the presence of WScript and a "global" procedure.
Sure. I was thinking for bigger recordsets where you could be a way away from the original SQL statement or in case where it's executing a stored procedure.
think of how that procedure is going to be growing: if there's rs1 then rs2 and a nested loop or something, extending it means adding rs3 and another level of nesting
if each procedure is responsible for its own recordset, there's no need to number them
if one procedure is going to need multiple recordsets, then they deserve descriptive names
we don't do Dim str1 As String, str2 As String, so why would we go Dim rs1 As Recordset, rs2 As Recordset?
don't get me wrong: rs is a perfectly fine name IMO - but only when it's clear that the procedure needs a recordset to do its job, and that it only needs one.
(although, there's almost always a more descriptive name for it)
and for record, I tend to agree. That said, I do use rs but as soon as I need rs2 in the same scope, I will go back and rename rs to rsFoo and the new one to rsBar
Reminds me of a strip I saw once --- The guy's taking a philosophy exam. The question on the sheet asks Can you go back in time and kill your grandmother?. He writes, No.. He touches his scar on the right temple gingerly. Then he continues, Her kung fu is too powerful.
> `Assert` calls document a reason for a test to *fail* - if a test doens't invoke any `Assert`, then that test will pass; that's by design, and consistent with the expectations of a unit test.
By default, the `IAssert` contract will be fulfilled by `Rubberduck.AssertClass`, which has rather stiff equality rules where mismatching types are considered to not be equal. Depending on the `Variant` subtypes involved, this may be what's happening here.
> That test is essentially a "poor man's data-driven test" working around lack of data-driven support for Rubberduck unit tests (#3699).
An alternative work-around could be to split it into multiple tests that explicitly cover a single case, for example:
```vb '@TestMethod Public Sub GivenSameDividendAndDivisor_RemainderIsZero() Const value As Double = 10 Const expected As Double = 0 Dim actual As Double If value = 0 Then Assert.Inconclusive "Test is misconfi
> That test is essentially a "poor man's data-driven test" working around lack of data-driven support for Rubberduck unit tests (#3699).
An alternative work-around could be to split it into multiple tests that explicitly cover a single case, for example:
```vb '@TestMethod Public Sub GivenSameDividendAndDivisor_RemainderIsZero() Const value As Double = 10 Const expected As Double = 0 Dim actual As Double If value = 0 Then Assert.Inconclusive "Test is misconfi
> That test is essentially a "poor man's data-driven test" working around lack of data-driven support for Rubberduck unit tests (#3699).
An alternative work-around could be to split it into multiple tests that explicitly cover a single case, for example:
```vb '@TestMethod Public Sub GivenSameDividendAndDivisor_RemainderIsZero() Const value As Double = 10 Const expected As Double = 0 Dim actual As Double If value = 0 Then Assert.Inconclusive "Test is misconfi
> That test is essentially a "poor man's data-driven test" working around lack of data-driven support for Rubberduck unit tests (#3699).
An alternative work-around could be to split it into multiple tests that explicitly cover a single case, for example:
```vb '@TestMethod Public Sub GivenSameDividendAndDivisor_RemainderIsZero() Const value As Double = 10 Const expected As Double = 0 If value = 0 Then Assert.Inconclusive "Test is misconfigured" Exit Sub
"--soft" -> make HEAD point to given commit. Nothing else "--mixed" -> make HEAD point to given commit and clear staging area "--hard" -> make HEAD point to given commit and reset everything in the working tree to that state "--merge" / "--keep" never used those, I don't quite understand the docs either
turns out VB wasn't installed :P
make sure it is
in VS, go to tools -> options -> text editor -> file extension
add asp as the extension and pick Visual Basic as the editor
VBA Rubberducking
VBA Rubberducking