Visual Studio .NET 2003 editor bug?  
Author Message
xceluser





PostPosted: Tue Jun 21 23:01:09 CDT 2005 Top

Visual Studio C++ >> Visual Studio .NET 2003 editor bug?

Hi,

I'm not sure if it's only me or it happens to a lot of people. Every
once-in-a-while, the Visual Studio .NET 2003 will try to ruin my source
files by appending something like up to 70KB of garbage characters in the
end of the source file. As a result, the compiler won't be able to detect
the changes made in the source file, and it reports that the project is
update to date. Ocassionally, I receives the following messages when
openning the corrupted source file:
---------------------------
Microsoft Development Environment
---------------------------
Document contains one or more extremely long lines of text. These lines will
cause the editor to respond slowly when you open the file. Do you still want
to open the file?
---------------------------
Yes No
---------------------------
It's certainly because the ending line is too long, and I can always solve
this problem by erasing it.

I'm wondering if it's a problem of the visual studio editor, because it
happens to me a lot, but only once in a while. How can I avoid it?

Thanks,
--
He Shiming

Visual Studio322  
 
 
Alexander





PostPosted: Tue Jun 21 23:01:09 CDT 2005 Top

Visual Studio C++ >> Visual Studio .NET 2003 editor bug? Any antivirus running with "scan on access"?



> Hi,
>
> I'm not sure if it's only me or it happens to a lot of people. Every
> once-in-a-while, the Visual Studio .NET 2003 will try to ruin my source
> files by appending something like up to 70KB of garbage characters in the
> end of the source file. As a result, the compiler won't be able to detect
> the changes made in the source file, and it reports that the project is
> update to date. Ocassionally, I receives the following messages when
> openning the corrupted source file:
> ---------------------------
> Microsoft Development Environment
> ---------------------------
> Document contains one or more extremely long lines of text. These lines
> will cause the editor to respond slowly when you open the file. Do you
> still want to open the file?
> ---------------------------
> Yes No
> ---------------------------
> It's certainly because the ending line is too long, and I can always solve
> this problem by erasing it.
>
> I'm wondering if it's a problem of the visual studio editor, because it
> happens to me a lot, but only once in a while. How can I avoid it?
>
> Thanks,
> --
> He Shiming
>


 
 
He





PostPosted: Tue Jun 21 23:44:24 CDT 2005 Top

Visual Studio C++ >> Visual Studio .NET 2003 editor bug? Nope, what do antivirus programs scanning .cpp files for? And chkdsk reports
no problem with the file system. It happens to me once every like two
months.

--
He Shiming



> Any antivirus running with "scan on access"?
>


 
 
Mark





PostPosted: Wed Jun 22 03:30:28 CDT 2005 Top

Visual Studio C++ >> Visual Studio .NET 2003 editor bug? Because they scan everything, exe with a .jpg extension still = exe if a
config is made.

--
- Mark Randall
http://zetech.swehli.com



> Nope, what do antivirus programs scanning .cpp files for? And chkdsk
> reports no problem with the file system. It happens to me once every like
> two months.
>
> --
> He Shiming
>


>> Any antivirus running with "scan on access"?
>>
>
>


 
 
pavel_a





PostPosted: Wed Jun 22 07:27:01 CDT 2005 Top

Visual Studio C++ >> Visual Studio .NET 2003 editor bug? Well it's not likely that a C source file begins with letters MZ :)

--


> Because they scan everything, exe with a .jpg extension still = exe if a
> config is made.
>
> --
> - Mark Randall
> http://zetech.swehli.com
>


> > Nope, what do antivirus programs scanning .cpp files for? And chkdsk
> > reports no problem with the file system. It happens to me once every like
> > two months.
> >
> > --
> > He Shiming
> >


> >> Any antivirus running with "scan on access"?