I think I'm going to get all the windows hook stuff out of Rubberduck.dll and use the EventHook library instead - it seems more stable than what I came up with, and it makes that much COM/Win32 out of Rubberduck
Your code looks pretty solid from a COM level actually - you just have to remember that the message pump isn't executing in your thread. That means that you need to ensure thread safety for the callback arguments.
Yeah, what I can't sort out is how to get around having to duplicate a concrete implementation of some piece of IConfigurationService and XmlConfigurationServiceBase on SmartIndenter.
On the one hand, if I split part of the IConfigurationService interface off into SmartIndenter and have IConfigurationService implement it, it creates an ambiguous reference because XmlConfigurationServiceBase inherits from it.
On the other hand, if I only inject an IIndenterSettings it runs into the same timing issues I was having the other day.
Or maybe just a simple Rubberduck.SettingsProvider. That would also give some more flexibility in addressing the issue that was raised in #1290 about how local settings have the potential to interfere with source control.
It would make it easier to implement some sort of enterprise-wide provider.
I.e., if a team relies on a common configuration for reasons of source control, style guidelines, whatever, then can just pop in a different SettingsProvider.
@Mat'sMug does the resolver know what a document-type module's implicit WithEvents variable is? For example, does the resolver know that a ThisWorkbook module with a workbook_open signature relates to a Workbook object?
Sure, it's a dumb example, but given enough hosts and document-types, plus ActiveX controls, there's scope for collisions. I don't think VBA gets confused, as iirc, it keeps the details in the module, but doesn't export them.
But the reason I ask is because I'd like a way to view all document event handlers. For example, I just opened a workbook with 50+ sheets. I wanted to find the workbook and all of the sheets that had event handlers. The only way I can think of in VBE, is to search Worksheet_ in ObjectExplorer.
Exploring a bit VBA Application.InputBox method I've realized that catching user cancellation is tricky when type is reference, so return value is a range object.
As cancellation's return value is False I can't assign it to an object with Set, so I've created a UDF to return Nothing when user p...
> This issue is also causing the Ready state to "stick", due to stale/duplicate VBComponent objects floating around in the _moduleStates dictionary with a Ready parser state.
that's pretty cool - you can see inspection results update as the parser completes. the fix for #1307 shows that the "ghost declarations" occur when setting error state... which is a problem, because now there's no error state anymore
Sub CrackPassword()
Dim v1 As Integer, u1 As Integer, w1 As Integer
Dim v2 As Integer, u2 As Integer, w2 As Integer
Dim v3 As Integer, u3 As Integer, w3 As Integer
Dim v4 As Integer, u4 As Integer, w4 As Integer
On Error Resume Next
For v1 = 65 To 66: For u1 = 65 To 66: For w1 = 65 To 66
For v2 = 65 To 66: For u2 = 65 To 66: For w2 = 65 To 66
For v3 = 65 To 66: For u3 = 65 To 66: For w3 = 65 To 66
For v4 = 65 To 66: For u4 = 65 To 66: For w4 = 32 To 126
ActiveSheet.Unprotect Chr(v1) & Chr(u1) & Chr(w1) & _
I found this VBA code to unlock sheets without knowing the password:
Sub PasswordBreaker()
Dim i As Integer, j As Integer, k As Integer
Dim l As Integer, m As Integer, n As Integer
Dim i1 As Integer, i2 As Integer, i3 As Integer
Dim i4 As Integer, i5 As Integer, i6 As Integer
On Error...
Encryption was a banned US export until 2000, so MS had to limit the encryption.
IIRC, there used to be a "Not for export" warning on the Office retail box. Just like there used to be a US version of Netscape and an International version
And I know that there is no real code signing available in MS Access. Which is mandatory in some business cases in Germany VBA codes in financal products.
Yes, I know -but Access doesn't offer the "Disable access to VBIDE" option, so if the project can be unprotected (which it can, if it isn't an ACCDE/MDE) then a malicious user can add their own code.
And even if it is an ACCDE/MDE then the pcode can be decompiled into VBA.
Once you give your users physical access to a PC, you can't guarantee that your security won't be defeated. The whole industry even says as much:
If a bad guy has unrestricted physical access to your computer, it's not your computer anymore
Password protection is at best a deterrent. If you...
And this for Access (from the same guys that make vbWatchdog)
Yes, so unless the regulator forces the user to only be able to run signed code, then the requirement that code be signed on publish is not much of a protection.
But that's a bit like saying that users should only use approved calculations in a calculator. The whole point of a calculator is that it can do any calculation that it's capable of.
So like you say, you don't have liability for the code anymore, and like I say in the SO answer.. You need to make best efforts and educate users about policy, and know that determined users will find a way, and make sure the regulator can see your best efforts and policies.
Exploring a bit VBA Application.InputBox method I've realized that catching user cancellation is tricky when type is reference, so return value is a range object.
As cancellation's return value is False I can't assign it to an object with Set, so I've created a UDF to return Nothing when user p...
Once you give your users physical access to a PC, you can't guarantee that your security won't be defeated. The whole industry even says as much:
If a bad guy has unrestricted physical access to your computer, it's not your computer anymore
Password protection is at best a deterrent. If you...
VBA Rubberducking
VBA Rubberducking