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

It doesn't work on Rider 2018.3.1 #8

Open
huoguangjin opened this issue Jan 13, 2019 · 3 comments
Open

It doesn't work on Rider 2018.3.1 #8

huoguangjin opened this issue Jan 13, 2019 · 3 comments

Comments

@huoguangjin
Copy link
Owner

Rider 2018.3.1 (Build #RD-183.5253.26, built on December 27, 2018)

@huoguangjin
Copy link
Owner Author

Log when trying to toggle highlight:

20:51:54.093 | INFO  | FrontendEditorActionHandler    | Executing backend editor handler 'EditorSelectWord'
20:51:54.093 | INFO  | FrontendActionHandlers         | >> Begin backend 'ExtendSelection' action session
20:51:54.097 | INFO  | FrontendActionHandlers         | << End backend 'ExtendSelection' action session

@huoguangjin
Copy link
Owner Author

check the last section about Rider in this sdk doc What is the IntelliJ Platform

Highlights may be implemented by ReSharper

JetBrains Rider uses the IntelliJ Platform differently than other IntelliJ based IDEs. It uses the IntelliJ Platform to provide the user interface for a C# and .NET IDE, with the standard IntelliJ editors, tool windows, debugging experience, and so on. It also integrates into the standard Find Usages and Search Everywhere UI, and makes use of code completion, syntax highlighting, and so on.
However, Rider doesn’t create a full PSI (syntactic and semantic) model for C# files. Instead, it reuses ReSharper to provide language functionality. All of the C# PSI model, all inspections and code rewriting, such as quick fixes and refactorings are run out of the process, in a command- line version of ReSharper. This means that creating a plugin for Rider involves two parts - a plugin that lives in the IntelliJ “front end” to show user interface, and a plugin that lives in the ReSharper “back end” to analyze and work with the C# PSI.
Fortunately, many plugins can simply work with the ReSharper backend. The Rider takes care of displaying the results of inspections and code completion, and many plugins can be written that don’t require an IntelliJ UI component. More details can be found in the Part VIII - Product Specific section.

@huoguangjin
Copy link
Owner Author

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

No branches or pull requests

1 participant