3 votesNathan Sokalski commented
I also want to mention that I do know that keyboard shortcuts can be customized, but I believe that there is such a thing as overcustomization. I think what I really should have said I wanted is to have the same keyboard shortcut for all places and contexts the command is available, and to remove the ability to change the defaults (only allow editing of keyboard shortcuts that the user added themselves). I think this would take away confusion and allow us to tell each other what keyboard shortcuts to use without worrying about whether they have their machine configured the same way we do.Nathan Sokalski shared this idea ·
406 votesNathan Sokalski commented
I often receive errors in my XAML for resources coming from other files. Even though Intellisense lists the resources (IValueConverters, Styles, etc.) as existing, it then shows them as errors. This is often related to the source not being compiled or something related to referencing not being updated, but even after the source is recompiled or the reference is fixed (although it often was correct already), Visual Studio 2015 often takes a lot of tries before realizing that the code is correct.
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to include this into the product.