Odd unwanted behavior during a windows update session
Forgot to turn off automatic updates in Windows 7 last night. Had been working on a legacy project in VB6. It was running on the desktop when Windows 7 got a bit too smart. BecauseVB was open and in debug mode, it appears that Windows 7 decided to shut it down and then looked for the last savedbackup of that object (I believe I saw a file that does a daily backup) and rather than giving me the last saved version from yesterday evening, Windows 7 brought out that backup and replaced my work in progress with the older version saved from the previous evening. This leaves about a day of coding that needs to be re-done. While it is nice to have a backup, shouldn't the user be allowed to decide what backup to use and what not to use - not Windows Update? There is no way I wanted the code from the previous day - I could have gotten that from Source Safe. Normally it wouldn't be an issue because it would be checked into Source Safe when the task is complete. In this case, it hadn't been checked in because it wasn't ready to check in. Instead it was just open (in debug mode) on my desktop.The simple solution for me is to change the Windows Update setting from automatic to manual. That is far from an optimal solution. Not much I can do about the lost code. It would be nice to be able to use both features - that is, daily backup and Windows Update. Guess this should go up on the Connect site - I don'thave access to the Windows 7 Connect - my primary is SQL Server and we don't want this thread there. urrgh!Nasty one! Ouch!Works okay with .NET and SQL which automatically backs itself up on a reboot. Not the case with Visual Studio 6.
November 5th, 2009 3:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics