Comments
3 comments
-
Thank you for your post.
As you noted the original upgrade mechanism is still in place and hasn't changed from its original incarnation.
There's one simple reason it's still in place - we haven't changed the Release code except to extend the expiration date so you can keep using Reflector freely while work continues internally on the tool to improve it for our users.
It also follows that we have not gone even near the search behaviour or resulting code.
I'm not saying you are not experiencing problems - simply that the code hasn't been touched so there will be another explanation for your current issues that we will try and test for.
Kind regards,
Stephen -
Sorry, but this problem did not exist prior to the 'compulsory' update to the latest release, and no other variables on the system have changed.
If you didn't touch the code, why did the problem appear with the latest upgrade? Also, this is a good example of why compulsory upgrades to each new release will only foster bad will. I can't revert to the previous working release, and have no choice but to deal with the defect. :?StephenC wrote:Thank you for your post.
As you noted the original upgrade mechanism is still in place and hasn't changed from its original incarnation.
There's one simple reason it's still in place - we haven't changed the Release code except to extend the expiration date so you can keep using Reflector freely while work continues internally on the tool to improve it for our users.
It also follows that we have not gone even near the search behaviour or resulting code.
I'm not saying you are not experiencing problems - simply that the code hasn't been touched so there will be another explanation for your current issues that we will try and test for.
Kind regards,
Stephen -
The only changes were to digitally sign the assembly, to stop Vista (and later), complaining about the assembly being unsigned every time you run .NET Reflector, and the version number. It's *possible* that the digital signing may have interfered with the search functionality, although that seems unlikely.
It's also possible that something else installed on your system could be interfering with .NET Reflector's operation. Again, this is unlikely, but without more information I can't say either way for sure.
The bottom line is that because this problem appears to occur so rarely and, as a result, we've been unable to reproduce it here, unfortunately I don't have anything more sensible to suggest at this point.
Sorry I can't be more help.
Thanks,
Add comment
Please sign in to leave a comment.
Lutz seemed to have the sense to use a timer to not trigger a search until a certain period of time elapsed after the last keystroke in the search box.
Now, on a Core i7 box with 12 gigs of RAM and Vista 64 bit, every keystroke results in triggering an immediate search, and typing in the search box is almost as painful as root canal.
This is new as of the most recent upgrade.
Thank you very much Red Gate.