Feature Overview¶
What works, per IDE — and where something needs a second look, exactly what to expect and what to do about it.
Symbol |
Meaning |
|---|---|
✅ |
Works |
⚠️ |
Works, with a caveat — see the note |
❌ |
Not available in this IDE — see the note for the alternative |
Editing Features¶
Feature |
VS Code |
Visual Studio |
Rider |
|---|---|---|---|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
❌¹ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
|
✅ |
✅ |
✅ |
Running Scenarios¶
Feature |
VS Code |
Visual Studio |
Rider |
|---|---|---|---|
❌⁴ |
✅ |
⚠️⁵ |
Project Setup¶
Feature |
VS Code |
Visual Studio |
Rider |
|---|---|---|---|
❌³ |
✅ |
❌³ |
¹ Visual Studio’s native Document Outline window doesn’t support
.feature files at all — a VS platform limitation, not something we can
configure around. See Document Outline.
² Visual Studio’s native Find All References (Shift+F12) does not route to Reqnroll bindings — use the N step usages CodeLens above the binding, or assign a keyboard shortcut to the Find Step Usages command (it has no menu entry). See Find Step Definition Usages.
³ VS Code and Rider don’t have an equivalent project wizard or file templates; create files with the IDE’s normal New File command and use the Define missing step quick fix to scaffold bindings — see New Project / Item Templates.
⁴ VS Code has no Reqnroll-owned Run feature; install the C# Dev Kit extension and use its own Test Explorer/CodeLens instead — see Running Scenarios.
⁵ Rider’s lens can only run a scenario, not debug it, and doesn’t appear in Rider’s native Unit Tests tool window. See Running Scenarios for the details and the workaround for debugging.
Preview status
Some features above shipped after this page was last reviewed for accuracy against the running extensions — if something here looks wrong or out of date, please file an issue.