You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: test-plan.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
# Validating C# Extension for VS Code
2
2
3
3
#### Opening projects
4
-
When you open a directory in VS Code, the C# extension should look for a .csprojor .sln file in that directory and use "OmniSharp" to load it. If a .cs file is present and no .csprojor .sln file are present, Omnisharp should start but the intellisense should only appear when a change is made to the file.
4
+
When you open a directory in VS Code, the C# extension should look for a .csproj, .sln, or .slnf file in that directory and use "OmniSharp" to load it. If a .cs file is present and no .csproj, .sln, or .slnf file are present, Omnisharp should start but the intellisense should only appear when a change is made to the file.
5
5
If you look in "Output > Omnisharp Log" a bunch of information should be printed about what copy of MSBuild was used and what projects were load
6
6
7
7
Project types to test:
8
8
* Standalone csproj
9
-
* Directory containing .sln file that references csprojs--projects should be loaded
9
+
* Directory containing .sln or .slnf file that references csprojs--projects should be loaded
0 commit comments