I have found a VERY annoying behaviour of Visual Studio where it corrupts VB6 source files by doing the following if performing a merge where conflicting changes exist to be able to check-in the updated file to TFS, the file must be manually altered to resolve the conflicts, and the alteration is done in the merge window.
- Changes all "Variants" to "Objects"
- Removes all instances of the keyword "Set"
- Forces brackets around all procedure/method calls
- etc.
I have found that this occurs with every version of Visual Studio from 2010 to 2013 and possibly others due to the fact that all VB6 files are associated with VB.Net.
I have tried to change Visual Studio so that all VB6 objects are treated as text files to prevent this, however, this change appears to revert to the VB.Net association at random times (possibly when an update is applied or an extension is added).
Is there any way to deal with this permanently???
Mark
Seradex Inc.
