> Rubberduck.1.22.Setup.x64.exe(2.86MB) - Downloaded 77 times. Last updated on 2015-04-01 Rubberduck.1.22.Setup.x86.exe(3.21MB) - Downloaded 150 times. Last updated on 2015-03-31
1.22 has 227 downloads!
> Rubberduck.Setup.1.3.0.1.exe(4.05MB) - Downloaded 23 times. Last updated on 2015-05-05
> The VBIDE dependency wasn't embedding its interop types in all projects (only the SourceControl project was actually) - I'm going to close this issue as fixed, keeping in mind that it might come back and bite us later.
it shouldn't be needed.. I reinstated it when I realized switching between debug and release builds, and then debug again, broke the debugger for some reason.
just don't forget to run regasm.exe /u in pre-build after that, otherwise you'll end up cluttering your registry with dozens of registered builds like I did last month
> error MSB3073: The command "c:\Windows\Microsoft.NET\Framework64\v4.0.30319\regasm.exe C:\Users\Hosch250\Documents\Visual Studio 2013\Projects\Rubberduck\RetailCoder.VBE\bin\Debug\Rubberduck.dll /codebase /tlb" exited with code 100.
Warning 3 A reference was created to embedded interop assembly 'c:\Windows\assembly\GAC_MSIL\office\14.0.0.0__71e9bce111e9429c\OFFICE.DLL' because of an indirect reference to that assembly created by assembly 'c:\Windows\assembly\GAC_MSIL\Microsoft.Vbe.Interop\14.0.0.0__71e9bce111e9429c\Microsoft.Vbe.Interop.dll'. Consider changing the 'Embed Interop Types' property on either assembly. C:\Users\Mathieu\Source\Repos\Rubberduck\Rubberduck.Parsing\CSC Rubberduck.Parsing
// identifiers used inside selection and before selection are candidates for parameters:
var input = inScopeDeclarations.Where(item =>
item.References.Any(reference => inSelection.Contains(reference)
&& reference.Selection.StartLine < selection.Selection.StartLine))
.ToList();
also borked:
// identifiers used inside selection and after selection are candidates for return values:
var output = inScopeDeclarations.Where(item =>
item.References.Any(reference => inSelection.Contains(reference)
&& reference.Selection.StartLine > selection.Selection.StartLine + selection.Selection.LineCount))
.ToList();
and borked:
// identifiers used only inside and/or after selection are candidates for locals:
_locals = inScopeDeclarations.Where(item =>
item.References.All(reference => inSelection.Contains(reference)
|| reference.Selection.StartLine > selection.Selection.StartLine))
.ToList();
Public Sub LoopOverDateRange()
Const startDate As Date = #5/13/2015#
Const endDate As Date = #5/20/2015#
Dim d As Date
Dim i As Integer
i = 1
For d = startDate To endDate
Debug.Print "Iteration " & i & ":"; d
i = i + 1
Next
End Sub
> Per this conversation, the idea was to make it so that the references required for unit testing would stop breaking on each update, so folding it back into the Rubberduck.dll might not be a great idea. Idk.
A string is an array of bytes, and you can iterate through it if you know your way around two-byte unicode representation of a string.
When I say is, I mean it: there is no need for a type conversion, and this will work just fine:
Public Sub TestByteString()
Dim strChars As String
Dim ...
@Phrancis did Windows find a solution to the problem? ;)
Web Page Blocked Access to the web page you were trying to visit has been blocked in accordance with company policy. Please contact your system administrator if you believe this is in error. User: xxxxx\yyyy URL: github.com/ Category: shareware-and-freeware
Once you've figured out what the error is, take that commented-out On Error Resume Next line, and remove it. Then make a quick search on this site about error handling in VBA. The best way to never know what's going on is to use On Error Resume Next. — Mat's Mug8 secs ago
You can check the system tables, MSysObjects and MSysQueries for references to tables and queries (you can also check the sql string of querydefs). You can loop through the properties of forms and reports, and their controls, for references to tables, queries and macros. You can search code.
Th...
@RubberDuck refactor/rename in Access looks like is going to be problematic
> We've inherited an MS Access db/application (Office 2002) with great names such as NewTable, Subform or Macro1. Unfortunately, when we change these to more meaningful names, the references (in other Queries, Forms or Actions) are not updated.
Why does this have to be VBA? As much as I love VBA, it seems kind of like using a hammer when what you really need is a screwdriver. — RubberDuck8 secs ago
> When running _Refactor/Extract Method_, declarations of variables that are only used in the new method should be removed instead of leaving them for a later clean up in _Code Inspections_.
When this code is refactored:
Public Sub test1() Dim i As Integer Dim j As Integer
i = 10 For j = 1 To i MsgBox j Next
End Sub
it becomes this:
Public Sub test1() Dim i As Integer Dim j As Integer
@Duga though I've got to admit, the never assigned is still a little shaky. I just discovered a couple of variables that Code Inspections claims aren't used, but clearly are.
I'd have just gone with Enhancement, myself, but whatever makes you happy.
Also, still not getting proper highlighting on all variables when they're flagged as Never Assigned/Used. i.e. too many characters are highlighted or not enough.
it's all because of that 1 - the assumption was that an identifier could only ever span a single line, so the only line to replace would be the line the identifier is on
Is it better to create a class module to hold Global variables, use Global variables, or create them in the Main module, and pass them everywhere they need to go?
A string is an array of bytes, and you can iterate through it if you know your way around two-byte unicode representation of a string.
When I say is, I mean it: there is no need for a type conversion, and this will work just fine:
Public Sub TestByteString()
Dim strChars As String
Dim ...
You can check the system tables, MSysObjects and MSysQueries for references to tables and queries (you can also check the sql string of querydefs). You can loop through the properties of forms and reports, and their controls, for references to tables, queries and macros. You can search code.
Th...
VBA Rubberducking
VBA Rubberducking