G
Guest
I applied a System.Data.dll hotfix today and it did not solve the problem so
I went to a restore point from yesterday. It restored and rebooted. I then
went back to work on a C# Windows application in Visual Studio. Out of habit,
I verified that all of my source files were in sync with SourceSafe.
Lo and behold, the files on my disk were older than those I had checked in
late yesterday. What does this mean? It means that System Restore includes
..cs and who knows what else in the list of files that it feels free to
clobber.
How many bugs have been reintroduced and how much work has been lost to this
problem?!?!?!
To round out this report, I undid the last restore, and suddenly my files
were back in sync with SourceSafe. I still have a useless hotfix (hopefully
it is *only* useless - KB 887549 ) but at least I have all of my source and
who knows what files back.
Finally, I followed the Microsoft web site to try to report this BUG and got
some blithering idiot who insisted that I needed to pay $35 to report it -
and that besides, the lines were down and I would have to call back. What
crap!
Now, I can go back to trying to develop a workaround for
"System.Data.VersionNotFoundException" - yet another Microsoft bug that I
can't get any support for.
David Rogers
Fred Hutchinson Cancer Research Center
I went to a restore point from yesterday. It restored and rebooted. I then
went back to work on a C# Windows application in Visual Studio. Out of habit,
I verified that all of my source files were in sync with SourceSafe.
Lo and behold, the files on my disk were older than those I had checked in
late yesterday. What does this mean? It means that System Restore includes
..cs and who knows what else in the list of files that it feels free to
clobber.
How many bugs have been reintroduced and how much work has been lost to this
problem?!?!?!
To round out this report, I undid the last restore, and suddenly my files
were back in sync with SourceSafe. I still have a useless hotfix (hopefully
it is *only* useless - KB 887549 ) but at least I have all of my source and
who knows what files back.
Finally, I followed the Microsoft web site to try to report this BUG and got
some blithering idiot who insisted that I needed to pay $35 to report it -
and that besides, the lines were down and I would have to call back. What
crap!
Now, I can go back to trying to develop a workaround for
"System.Data.VersionNotFoundException" - yet another Microsoft bug that I
can't get any support for.
David Rogers
Fred Hutchinson Cancer Research Center