J
jy836
I was using VB .NET, working on my database application. After running it
successfully, I decided to take a little break. So I closed Visual Studio (I
saved all files, of course), and when I opened my solution later, the
application had several bugs which hadn't been there earlier.
I had to manually look through the code to figure out what had been changed
and fix the problems. It wasn't a lot of work, but I'm concerned that if VS
..NET does this in the future (when my application is farther along and has
much more code), it could have serious consequences. (I haven't tested the
application as thoroughly as I would have liked to after fixing the code, so
there may still be existing bugs that I don't yet know about.)
Has anyone else had this problem? Is there some kind of patch from MS that I
can download for this?
successfully, I decided to take a little break. So I closed Visual Studio (I
saved all files, of course), and when I opened my solution later, the
application had several bugs which hadn't been there earlier.
I had to manually look through the code to figure out what had been changed
and fix the problems. It wasn't a lot of work, but I'm concerned that if VS
..NET does this in the future (when my application is farther along and has
much more code), it could have serious consequences. (I haven't tested the
application as thoroughly as I would have liked to after fixing the code, so
there may still be existing bugs that I don't yet know about.)
Has anyone else had this problem? Is there some kind of patch from MS that I
can download for this?