"Move closer to usage" refactor leaves a bit undone

[daFreeMan]

It does not trigger a reparse and it does not execute the indenter on the changed method.

Private Sub DeleteExtraLogFiles(ByVal filePath As String, ByVal fileNamePattern As String, ByVal maxLogsToKeep As Long)

'move this vvv
  Dim oldestFile As String
  
  On Error GoTo ErrorHandler
  
  Dim fileCount As Long
  
  Dim currentFile As String
  currentFile = Dir(filePath & fileNamePattern)
  
  Dim oldestFileDate As Date
  oldestFileDate = #12/31/3999#
  
  Dim currentFileDate As Date
  
  Do While Len(currentFile) > 0
    fileCount = fileCount + 1
    currentFileDate = FileDateTime(filePath & currentFile)
    If fileCount < maxLogsToKeep Then
      If currentFileDate < oldestFileDate Then
        oldestFile = currentFile
        oldestFileDate = currentFileDate
      End If
    Else
...

Yields this when moving Dim oldestFile As String

Private Sub DeleteExtraLogFiles(ByVal filePath As String, ByVal fileNamePattern As String, ByVal maxLogsToKeep As Long)

  On Error GoTo ErrorHandler
  
  Dim fileCount As Long
  
  Dim currentFile As String
  currentFile = Dir(filePath & fileNamePattern)
  
  Dim oldestFileDate As Date
  oldestFileDate = #12/31/3999#
  
  Dim currentFileDate As Date
  
  Do While Len(currentFile) > 0
    fileCount = fileCount + 1
    currentFileDate = FileDateTime(filePath & currentFile)
    If fileCount < maxLogsToKeep Then
      If currentFileDate < oldestFileDate Then
'get this vvv
        Dim oldestFile As String
oldestFile = currentFile
'and that ^^^
        oldestFileDate = currentFileDate
      End If
    Else
...

The lack of reparse:

It also somewhat inconveniently leaves the cursor at the top of the module instead of somewhere in the method that's being edited.

[daFreeMan]

Upon further usage, it appears that manually triggering the indenter causes a reparse, so as I see it, a simple call to the indenter for the affected method should take care of both stones with one bird.