Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confirmation of expected behavior @ 01-Navigation/6-Find_usages/6.2-Find_usages.cs #42

Open
sun-flat-yamada opened this issue May 21, 2021 · 3 comments

Comments

@sun-flat-yamada
Copy link
Contributor

Summary

I want to check the expected behavior.

I didn't know what to expect from what was written in this workshop.
01-Navigation/6-Find_usages/6.2-Find_usages.cs

    :
        // 1. Put the caret on ButtonText and Find Usages
        //    Note that ReSharper has found read and write usages
-->     //    It has also found usages of the type in a XAML control
-->     //    And has inferred a dynamic usage in the XAML control where no type is specified
    :

When I tried it with ReSharper, I got the following results, is this what you expect?
What part of this do you want me to look at?

jetbrains-resharper-find-usages

@maartenba
Copy link
Contributor

That tool window in your screenshot looks like the "regular Visual Studio" tool window. Can you try resetting the R# keymap (Extensions | ReSharper | Options, then Environment | Keyboard | Shortcut scheme, and Apply Scheme)

Ideally the screen should look like this:
image

I just pushed an update to fix the XAML user control (it was no longer working)

@sun-flat-yamada
Copy link
Contributor Author

Hi, @maartenba .

Apparently, my ReSharper is not working perfectly.

I had problems with shortcuts not being applied before, but I haven't been able to essentially solve the problem.
I'll try uninstalling and setting it up again.

@maartenba
Copy link
Contributor

Also check Extensions | ReSharper | Options, then Environment | Keyboard | Shortcut scheme, and Apply Scheme, this should put the keymap in place

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants