Feature Request: VS 2017 (et al) Add-in needs ability to turn of its "Handle Code Browsing" logic
Here's the issue: I have other add-ins that I'm VERY happy with that already handle "Go to Definition" and other functionality in VS. The Reflector Add-in is "fighting" for supremacy with my other add-ins though, and now basic functions like "Go to Definition" are pretty broken.
I understand that Reflector probably needs to override those to allow "Go to Definition" to work for pulling up the code for 3rd party assemblies it has decompiled, etc. So, I understand that there are times when I would want to opt-in to let Reflector have the wheel.
I would really like to see a "Handle Code Browsing" checkable menu option added to the Reflector Add-in's drop down menu. When checked, Reflector would do the current behavior. When unchecked, it would not intercept any of the code browsing requests. (Behind the scenes, Reflector would likely continue intercepting all requests and just check this flag as to whether to handle them or not.)
The goal is to allow me, the developer, the driver, to decide where the car goes. It is extremely frustrating when my Add-ins are fighting me.