Editor plugin support for ReSharper?

[citizenmatt]

Currently, the editor plugin has many assumptions about being used in Rider, and isn't applicable to being used for the ReSharper plugin. But this means that a number of features (e.g. installing a compatible version of nunit for local unit testing - #335) are unavailable to ReSharper. On the flip side, it also performs a number of tasks that are inappropriate for ReSharper (e.g. setting Rider as the default external editor, simplifying debugging setup, etc.)

This task is initially to investigate if it's worth migrating the editor plugin to also support ReSharper.

• Evaluate what the Rider plugin currently does to see what features are appropriate for ReSharper
• Should we expose the protocol to ReSharper? List the protocol features, see what would be useful, what wouldn't, and what's already handled by VSTU
• If refactoring/migrating the plugin is not an appropriate use of resources, would a stripped down, simpler version be useful?

[van800]

List of features:

1. Refresh Assets
2. Play/Pause/Step. But VSTU has Play.
3. Logs. But VSTU also has it. We can present logs better.
4. UnitTesting.
5. Open File by double click in Unity. Makes sense only if someone wants to drop VSTU.
6. New features like #32, when ready.

[wingyplus]

Is UnitTesting feature including Play mode tests?

[van800]

@wingyplus Not yet.

[MaxPalmer-UH]

Has there been any update on plans to do this?

[citizenmatt]

Not as it stands. What integration feature would you most be interested in?

[MaxPalmer-UH]

To be able to run all unit tests, including those that rely on Unity(3D) components from within Visual Studio 19 (with ReSharper installed). You have this functionality in Rider.