System.FormatException if date/time registry entries are corrupted


If either or both of the registry entries that NetSparkle uses (LastCheckTime or LastProfileUpdate) contains a value that the system cannot correctly interpret as a date/time value, an unhandled System.FormatException is thrown. I think this could probably happen as a result of changing the current "culture" settings in between runs. Another possibility is that these registry entries could become corrupted, perhaps as a result of malware or a hardware glitch, or of course by intentionally corrupting them. NetSparkle should write the values using a culture-independent format and should protect against an unhandled FormatException when attempting to convert the values from from the registry.


TomBogle wrote Jan 23 at 7:49 PM

I see this has been fixed in the current version.