Please make the auto-update feature optional. I work disconnected a lot and it's really inconvenient when Reflector won't launch because there's no internet connection.
Comments
3 comments
-
I've had a similar issue... I worked offline and Reflector told me that I needed to update (some sporadic wifi-connection made it look for an update I guess). I tried to update, but it failed... and Reflector was gone... It actually deleted the current version I had! Quite annoying, since I had no backup.
Oh well, nevertheless I second that suggestion... -
I've also run into this quirk as I often work offline. It's a rather unfortunate feature of an otherwise awesome tool. I'd like to see it more willing to run the current version when it knows there is an update available.
-
Yes! I've wished for years that NET Reflector's auto-update feature could be turned off. I've even considered ways of faking it out, either by redirecting its network traffic or intercepting its date/time calls.
Several times I've found myself away from the internet with my favorite NET tool broken because it wanted to update itself. It's very annoying to have to adjust your system date & time just to get things started, and even worse if it has deleted itself.
Once or twice I have needed to use reflector without sending any traffic onto the network. I have had to disable the network interface, make extra copies in case Reflector deleted itself, and play with the system date/time until I got Reflector started, then plug everything back in to work. This should not be necessary!
Another time a bug was introduced on an update and I had to go back to the old version, again by adjusting the system date & time. Fortunately I still had a copy of the old version.
A simple "DisableUpdate" option in the config file would solve all of these problems. Also, Reflector should be willing to start if the update fails.
Add comment
Please sign in to leave a comment.