I’ve just fixed a bug in Hovervue that was really getting to me and several other folks have reported it over time.

Since the first version, my save code only ran when Hovervue was closing down. This was bad as a crash would not save your data as it never got to shut down. Truth is I haven’t seen too many crashes while it’s running (and the ones I have been told of I’ve addressed) but there has always been a crash whenever the user has Hovervue running and shuts down their Windows machine. I haven’t figured out how to get around this but basically what happens is you get some sort of error with csc.exe (the C# compiler) as it gets spawned by the XML Serialization code that runs in my save code. This works perfectly in every case but when the machine is attempting to shut down.

What made this worse was that it would leave me with incomplete XML data files which would cause Hovervue to realize it had corrupt data the next time it started and as a result start from scratch settings wise.

I did a couple of quick searches and didn’t seen anything along the lines of what I’m seeing so I wimped out and just removed the save code from the shutdown code and moved it to happen automatically whenever a user changes something that can be saved (adds or removes a tile and when a tile’s options are modified). In a way, this is nicer for the user as it all happens automatically and is always up to date now.

I’m hoping to get around to creating a tile soon for Visual Studio Team System. At work we’re now dogfooding VSTS drops and I have much less use for the old Product Studio tile I had (previous internal bug management software) which was honestly by far the most useful tile and therefore my main reason for running Hovervue. When I get around to writing one to go against WIT, I’ll be sure to post it as well.

Anyway, you can get the latest version of Hovervue from here.