Since installing VAX 1216 I've had several file corruption problems. Basically, VAX inserts stray CR characters in my code. The compiler will give you a variety of compile errors that are totaly unrelated and you can only fix the file with a hex editor.
I'm pretty sure this is a VAX bug and not Visual Studio's since it has only occured when VAX is installed and enabled.
I'm using Visual Studio .NET 2003 on Windows XP Pro. I have no other AddIns installed. I'm not using any unusual language or keyboard settings (just the default US/English). This is on my home machine.
Its interesting to note that I also installed VAX on my work machine which is running Visual Studio .NET 2002 on Windows XP Pro but I have not seen the bug on my work machine.
Anyway, the last time this bug occured it was right after I had commented out part of a line like below and recompiled. Extra CR's were inserted only from that point to the end of the file. Maybe VAX was trying to reparse that section of the file to highlight it correctly?
Line Before: si.nMax = m_sizeWorkspace.Width - <expression>; Line After: si.nMax = m_sizeWorkspace.Width; // - <expression>;
I don't have that machine in front of me at the moment, but I did look in one of the VAX install sub-directories and noticed multiple "cached" copies of the two affected files. I inspected some of the cached copies and saw that they also had stray CR characters.
Topic Locked
Posted - Feb 29 2004 : 10:06:23 PM
Ensink
