This repository has been archived by the owner on Sep 24, 2019. It is now read-only.
Releases: aspnet/Razor.VSCode
Releases · aspnet/Razor.VSCode
1.0.0-alpha3
Features
- Handle old Razor project configuration files without exploding (#333)
- Consume root namespace changes. (#308)
- Remove initial experimental Blazor 0.7.0 support and add support for the next Blazor update (#302)
- Make logging errors more descriptive (#299)
- Update Report Razor Issue privacy notices (#283)
- Even when no Razor files allow telemetry (#281)
- Use built-in clipboard API. (#279)
- Add support for .razor files (#278)
- Provide a fallback URL for Razor Language Server (#257)
- Support Razor 3.0 (#250)
- Consume Razor ProjectSystem with import understanding (#209)
- Add issue reporter command (#182)
- Simple TagHelper completion (#93)
- Show Razor Diagnostics (#30)
- TagHelper refresh (#17)
- Initial TagHelper discovery. (#16)
Bugs Fixed
- On Document renamed that was open the old C# buffer sticks around. (#344)
- Fix local dev launch. (#327)
- If OmniSharpPlugin is building and user is building (dotnet watch run) things can break (#316)
- Batch component refresh TagHelper regens. (#315)
- Track Components and non-components in the LanguageServer (#312)
- Arch Linux Visual Studio Code Razor Language Server connection fails no messages (#303)
- Razor diagnostics at end of file result in exceptions. (#287)
- Renaming cshtml files no longer works. (#286)
- With dev16 installed we can't identify pre-2.0 Razor projects. (#246)
- Typing @{ results in @datetime{} (#240)
- Razor error: libunwind.so.8: cannot open shared object file (#223)
- Consider: Don't start razor language service when there are no razor files (#222)
1.0.0-alpha2
Bugs Fixed
- Razor.VSCode occassionally crashes VSCode (#221)
- HTML intellisense initially off by one character (#218)
- CSharp intellisense isn't always correct (#215)
- CSharp intellisense occasionally fails with an exception (#214)
- Incorrect completion in a simple view page (#210)
- Typing quickly can occasionally give inaccurate C# IntelliSense (#187)
- After a Razor file has been opened a prolonged amount of time on OSX C# experience stops. (#166)
Known Issues
- Only ASP.NET Core projects are supported (no support for ASP.NET projects)
- Support for tag helpers and formatting not yet implemented
- Limited support for colorization
- Loss of HTML completions following C# less than (
<
) operator - Error squiggles misaligned for expressions near the start of a new line
- Incorrect errors in Blazor projects for event bindings
- Emmet based abbreviation expansion is not yet supported
NOTE: To disable the preview Razor tooling set the "razor.disabled" setting to true
.
1.0.0-alpha1
Initial preview Razor (.cshtml) language service with support for C# completions and diagnostics in ASP.NET Core projects now available with the C# extension for Visual Studio Code (1.17.0)
NOTE: To disable the preview Razor tooling set the "razor.disabled" setting to true
.
Known Issues
- Only ASP.NET Core projects are supported (no support for ASP.NET projects)
- Support for tag helpers and formatting not yet implemented
- Limited support for colorization
- Loss of HTML completions following C# less than (
<
) operator - Error squiggles misaligned for expressions near the start of a new line
- Leaving Razor files open for a significant period of time results in loss of Razor C# tooling on macOS
- Incorrect errors in Blazor projects for event bindings