Visual Basic and case-sensivity

[Øyvind Idland]

We use CVS in our organisation, and its an incdredible tool.

However, we have a couple of Visual Basic programmers here.
If one, for example changes a function-name from FOOBar to Foobar,
the VB IDE parses _every_ single for FOOBar and changes the case to Foobar.
(unbelivable, but its true.. )

When the user updates/commits the source, the conflicts arrive:
Every line containing FOOBar now is changed to FooBar, and it
generates a lot of conflicts.

Does anyone have a workaround to this problem ? We cant be the
first ones having this issue :)

Oyvind Idland,  Powel Gemini ASA
mailto:address@hidden