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
*[Video Tutorial compiling with .NET Core](https://channel9.msdn.com/Blogs/dotnet/Get-started-VSCode-Csharp-NET-Core-Windows)
22
22
23
+
### What's new in 1.17.0
24
+
* Added preview Razor (cshtml) language service with support for C# completions and diagnostics.
25
+
* Added omnisharp.minFindSymbolsFilterLength setting to configure the number of characters a user must type in for "Go to Symbol in Workspace" command to return any results
26
+
* Added a command - "CSharp: Start authoring a new issue on GitHub" to enable the users to file issues on github from within the extension with helpful config information from their system
27
+
23
28
### What's New in 1.16.2
24
29
* Update extension to handle upcoming breaking change to launch.json configurations in VS Code 1.28.
25
30
* Fixed launch.json `envFile` option on Windows
@@ -37,7 +42,7 @@ The C# extension is powered by [OmniSharp](https://github.com/OmniSharp/omnishar
37
42
* Added `monoPath` option to use the mono installation at the specified path when the `useGlobalMono` is set to "always" or "auto".
38
43
* Many other bug fixes!
39
44
40
-
See our [change log](https://github.com/OmniSharp/omnisharp-vscode/blob/v1.16.0/CHANGELOG.md) for more detail.
45
+
See our [change log](https://github.com/OmniSharp/omnisharp-vscode/blob/v1.17.0/CHANGELOG.md) for more detail.
Copy file name to clipboardExpand all lines: test-plan.md
+123-5Lines changed: 123 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ The easist way to verify that a project was successfully loaded is to open a .cs
93
93
* In a project that uses globbing (.NET Core), use the VS Code file explorer to add a new file next to the csproj. Intellisense/sighelp/etc should be available in the new file
94
94
* Add a new file and reference a type in it from a different file. Deleting from disk the file containing the referenced type should produce error messages
95
95
96
-
#### Razor
96
+
#### ASP.NET Core Razor
97
97
The Razor experience is available when you open a .cshtml file in a valid OmniSharp project. To setup a test project to verify on you can do:
98
98
1.`dotnet new razor`
99
99
2. Open `Pages/Index.cshtml`
@@ -103,18 +103,136 @@ The Razor experience is available when you open a .cshtml file in a valid OmniSh
103
103
* Completion is available for types that exist in the project (i.e. `Program`)
104
104
* Typing `@model DateTime` prompts for completion for the `model` symbol and the `DateTime` symbol.
105
105
106
-
#### C# Signature Help
106
+
#####C# Signature Help
107
107
* Typing `@Html.Raw()` prompts for signature help inside of the `()`.
108
108
109
-
#### C# Diagnostics
109
+
#####C# Diagnostics
110
110
* Typing `@ThisDoesNotExist` results in an error being created and squiggled in the .cshtml file. NOTE: This error squiggly will be misaligned due to known issues.
111
111
112
+
##### Known issues:
113
+
- Error squiggles may be misaligned due to known issues.
114
+
115
+
#### Blazor
116
+
The Blazor experience is available when you open a .cshtml file in a valid OmniSharp/Blazor project. To setup a test project to verify on you can do:
117
+
1.`dotnet new -i Microsoft.AspNetCore.Blazor.Templates`
118
+
2.`dotnet new blazor`
119
+
3. Open `Pages/Index.cshtml`
120
+
121
+
##### C# Completion
122
+
* Typing `@DateTime.Now` and `@(DateTime.Now)` provides completions throughout typing.
123
+
* Completion is available for types that exist in the project (i.e. `Program`)
124
+
* Typing `@layout MainLayout` prompts for completion for the `layout` symbol and the `MainLayout` symbol.
125
+
126
+
##### C# Signature Help
127
+
* Typing `@SetParameters()` prompts for signature help inside of the `()`.
128
+
129
+
##### C# Diagnostics
130
+
* When no changes have been performed on `Pages/Index.cshtml`, there are 0 errors.
131
+
* Typing `@ThisDoesNotExist` results in an error being created and squiggled in the .cshtml file.
132
+
133
+
##### Known issues:
134
+
- Error squiggles may be misaligned due to known issues.
135
+
- There are some errors in the default Blazor project that are known. All errors that read like `Cannot convert method group 'SomeMethodName' to non-delegate type 'object'. Did you intend to invoke the method? [ProjectName]` are expected.
136
+
137
+
#### Legacy Razor
138
+
The Razor experience is degraded (but no errors) when you open a .cshtml file in a valid OmniSharp/Legacy Razor project. To setup a test project to verify on you can do:
139
+
1. Open Visual Studio
140
+
2. New Project
141
+
3. ASP.NET Web Application (.NET Framework)
142
+
4. Select MVC
143
+
5. OK
144
+
6. Open `Views/Home/Index.cshtml`
145
+
146
+
##### C# Completion / IntelliSense
147
+
* Typing `@DateTime.Now` does not result in any C# completion.
148
+
* Typing `@{ var x = DateTime.Now; }` does not result in any C# completion.
149
+
* Typing `@model` does not result in any Razor directive completion.
150
+
151
+
##### C# Diagnostics
152
+
* There are 0 .cshtml related errors on open.
153
+
* Typing `@ThisDoesNotExist` does not result in an error being created.
154
+
155
+
##### Html Completion
156
+
Verifying Html is needed to ensure the Razor experience is still partially enabled.
157
+
* Typing `<stron` results in Html completion with an entry for `strong`.
158
+
* Typing `<strong>` results in a corresponding `</strong>` being appended
159
+
* Hitting enter Typing `@{}` and then hitting enter inbetween the curly braces results in:
160
+
```
161
+
@{
162
+
163
+
}
164
+
```
165
+
166
+
#### Razor Project level Information
167
+
To verify the project level information for Razor do the following:
168
+
1. Verify the `obj/Debug/TheTFMOfTheProject` folder contains a `project.razor.json` file (once the project is restored)
169
+
2. Verify the `project.razor.json`'s `Configuration` section is not set to `null`.
170
+
171
+
Verify each of the test projects above's `project.razor.json` file (ASP.NET Core Razor, Blazor and Legacy Razor) looks something like the following:
This option can be set to `true` to disable the above described C# experience.
233
+
This option can be set to `true` to disable the above described C# experiences.
116
234
117
-
##### razor.languageServer.trace
235
+
##### razor.trace
118
236
This option should always be displayed in the View --> Output --> Razor Log window
119
237
This option can be set to any of the following values:
120
238
* "Off" - Will launch Razor Language server with its log output set to 'Off'. The header in the Razor Log output window will be shown but no other content will be shown.
0 commit comments