Merge pull request #4509 from Vogel612/appveyor-shallow-clone

Fix Release Upload

0 + 4 + 12 = 16 Dec
16 Dec = 0x10 Hex
On a 32 bit address, that is in fact 0x0010

In a more generic manner, here is how you count with a Dec/Hex conversion

0 -> 0
...
9 -> 9
10 -> A
...
15 -> F
16 -> 10

> Win10, Excel2016 (desktop), RD build .4129 freshly installed this am

Installed .4129 this morning. The `Rubberduck | Settings` command has no effect. The settings dialog does _not_ open.

From the `Rubberduck` menu, I _can_ bring up:

- Test Explorer
- Indent Current Procedure (Not sure what that did - no code panes were open at all)
- Code Explorer
- Code Metrics
- ToDo list
- RegEx Assistant
- Export Active Project dialog
- Code Inspections
- About

So, this seems pretty i

> I renamed the `rubberduck.config` file and still no love.

Here's a log file for your perusal.
[RubberduckLog.txt](https://github.com/rubberduck-vba/Rubberduck/files/2572122/RubberduckLog.txt)

Also, of note, the `.config` file did _not_ get recreated when RD was opened, but I presume that may only get recreated when the settings dialog is launched, leaving something of a catch-22.

> I renamed the `rubberduck.config` file and still no love.

Here's a log file for your perusal.
[RubberduckLog.txt](https://github.com/rubberduck-vba/Rubberduck/files/2572122/RubberduckLog.txt)

Also, of note, the `.config` file did _not_ get recreated when RD was opened, but I presume that may only get recreated when the settings dialog is launched, leaving something of a catch-22.

This looks to be relevant:

2018-11-12 08:48:59.2051;ERROR-2.2.0.4129;Rubberduck.UI.Command.Settin

> Additional info:

The settings menu _does_ work in build 4124. It does _not_ work in build 4128.

> This issue is not fixed. If running inspections after parseing is disabled, the inspection results in the code inspection window do not get invalidated.

This is a possible cause for issue #4503.

> This issue is not fixed. If running inspections after parsing is disabled, the inspection results in the code inspection window do not get invalidated.

This is a possible cause for issue #4503.

> The instructions for compiling this addin do not work as of Nov 12 2018. Using Office 365 (2016) 64 bit.

I changed the powershell execution policy to allow unrestricted running however for each source file I received a dialog box asking me to unblock the file.

```
PS C:\WINDOWS\system32> get-executionpolicy
Unrestricted

PS C:\WINDOWS\system32> G:\Download\Microsoft\Visual Basic stuff\VBEX-master\VBEX-master\Make.ps1
Will Build G:\Download\Microsoft\Visual Basic stuff\VBEX-master\

> I cannot recreate this error applying the quickfix immediately after the inspection result got created.

Did you do anything between generating the inspection result and applying the quickfix? Here a setting might play a role: do you have running the inspections after parsing disabled in the settings?

With this disabled I can recreate the issue by running the inspections, then adding a new line with some whitespace, parsing and then choosing to apply the fix to the inspection.

> I cannot reproduce this error applying the quickfix immediately after the inspection result got created.

Did you do anything between generating the inspection result and applying the quickfix? Here a setting might play a role: do you have running the inspections after parsing disabled in the settings?

With this disabled I can reproduce the issue by running the inspections, then adding a new line with some whitespace, parsing and then choosing to apply the fix to the inspection.

> Found a few more examples:

Application.StatusBar = "Printing for: " & customerName

With "Object variable 'StatusBar'" being flagged. According to [MS Docs](https://docs.microsoft.com/en-us/office/vba/api/excel.application.statusbar), `Application` is an object, while the property `StatusBar` is a string.

Is the issue that the inspection is seeing the Application object and throwing, instead of digging deeper to note that the property in question is _not_ an object?

> Found a few more examples, one of note:

Application.StatusBar = "Printing for: " & customerName

With "Object variable 'StatusBar'" being flagged. According to [MS Docs](https://docs.microsoft.com/en-us/office/vba/api/excel.application.statusbar), `Application` is an object, while the property `StatusBar` is a string.

Is the issue that the inspection is seeing the Application object and throwing, instead of digging deeper to note that the property in question is _not_ an object?

> Hi. Sorry about that.
I don’t actively support this project anymore, but would be happy to evaluate pull requests.

> As a followup to one of my earlier examples, I started with:

```VBA
Dim RS As ADODB.Recordset
Set RS = New ADODB.Recordset

RS.ActiveConnection = dbConfig.SetupConnection(dbConfig.SQLConString)
```

This time I used the `Use 'Set' Keyword` quick fix, and this is what I got:

```VBA
Dim RS As ADODB.Recordset
Set RS = New ADODB.Recordset

RS.Set ActiveConnection = dbConfig.SetupConnection(dbConfig.SQLConString)
```

After applying the fix, the code was parsed,