How to avoid automatic renaming of sub signature parameters in visual basic 6.

Question

In Visual basic 6, i declare a sub like this:

Private Sub test1(ByRef XmlFooOutput As String)
  ...
End Sub

Aafter that, I declare another sub like the following one:

Private Sub test2(ByRef xmlFooOutput As String)
  ...
End Sub

Automagically, the first method is transformed in:

Private Sub test1(ByVal xmlFooOutput As String)
   ...
End Sub

So the XmlFooOutput parameter is transformed in xmlFooOutput.

This is a pretty dangerous feature because methods like those could be mapped to different XSL presentation files that read XML values through Xpath. So when test1 parameter is renamed, XSL bound to test1 method goes broken because Xpath points to XmlFooOuput but the correct value is now in xmlFooOutput.

Is it possible to remove this weird feature? I'm using Microsoft Visual Basic 6.0 (SP6).

This question has some duplicates:

• http://stackoverflow.com/questions/1064858/stop-visual-basic-6-from-changing-my-casing
• http://stackoverflow.com/questions/248760/vb6-editor-changing-case-of-variable-names

From what I see, there's no practical solution to disable this Intellisense evil feature.

Answer 1

This is a feature of Visual Basic that probably originates back in QuickBasic, as has been pointed out stems from case insensitivity in names.

I tried the example of the OP and VB6 changes the declaration of test1() as described.

Its not possible to remove this feature - you will have to find another way round this.

Answer 2

The case of variable names and other identifiers makes absolutely no difference to the language - VB6 is case-insensitive.

I agree it can be annoying when the IDE changes the case of identifiers automatically. There is already a detailed discussion of possible workarounds in this question.