« first day (3053 days earlier)      last day (127 days later) » 

Duga
Duga
00:05
REFRESH!
[Minesweeper] 124 Games Played. 95 Bombs Used. 15534 Moves Performed. 17 New Users
[rubberduck-vba/Rubberduck] 1 issues closed. 2 issue comments
 
6 hours later…
Duga
Duga
06:09
[rubberduck-vba/Rubberduck] phobo3s created comment on issue #5964: Resolver Error
> Dim isZwCad As Boolean
Dim zcadApp As Object
Dim zcadDoc As Object
On Error Resume Next
Set zcadApp = GetObject(, "ZWCAD.Application")
'if no zwcad then try autocad
If zcadApp Is Nothing Then
Set zcadApp = GetObject(, "AutoCAD.Application.23")
isZwCad = False
If zcadApp Is Nothing Then Exit Sub
Else
isZwCad = True
End If

I think this is the type of declaration that causes the error.
 
8 hours later…
Greedo
Greedo
13:55
C# Question: If I compile rubberduck.dll in visual studio, then I call a function from it in VBA or any dll consumer Declare Sub Quack Lib "rubberduck.dll" (ByVal volume As Double) can I set a breakpoint in my C# code in visual studio in the quack routine and step through it? Is this sort of thing possible in compiled languages?
I really want to step through by twinBASIC vbide addin since VBA/tB is one of my favourite languages because debugging is so easy. (except when you declare a property get incorrectly and crash the immediate window). Anyway what is this feature of a language/IDE called, does it exist for any languages that are compiled?
I know at a very high level for C/C++ there is a common practice to "attach" a debugger to a running process and step through the machine code. You can include "symbols" in a compiled dll and then when you attach the debugger it can convert the machine code to what it assumes the C/C++ source code looked like. IIRC in VB6 there are settings to compile to p-code not all the way to machine code
All that goes way above my head, I just want to put a red dot in my tB source code and then step through line by line to debug my compiled dll. Also break on errors, debug.print all that stuff, use the immediate window all that stuff. Do you think this is a reasonable request to make of Wayne & twinBASIC, is there any prior art of getting debugging integrated as well as I describe in a compiled dll/exe?
BZngr
BZngr
Debug=> Attach to Process... in visual studio. That's how I/we test RD code from within the VBIDE. I think it is the process you are describing.
Greedo
Greedo
Ok cool thanks, does that just hop into the code at whatever line it's currently on, or can you set a breakpoint in the Visual Studio IDE, then compile, then load VBIDE which in turn calls your addin, then that hits the breakpoint. What's the workflow like basically? I pretty much want tB IDE to pop up when my dll function is first called.
just like if I set a breakpoint in an Excel UDF called from the worksheet
BZngr
BZngr
14:14
In VS, attach to the Excel process after RD has loaded. Set breakpoint(s) in the C# code and invoke logic in the VBIDE that would call C# code of interest.
You will need to have Excel load a debug version of the RD dll.
 
10 hours later…
Duga
Duga
23:50
[rubberduck-vba/Rubberduck] 1657 stars vs. [decalage2/oletools] 2232 stars

« first day (3053 days earlier)      last day (127 days later) »