-
Notifications
You must be signed in to change notification settings - Fork 226
Known Issues: Razor Tooling in VS 15.3 #1628
Comments
Repairing Visual Studio or even making a full reinstall does not make tag helpers colorization/completion work in 15.3.2. Razor Language Services is installed and enabled by default. Tried to disable it or uninstall it but I can't then open any cshtml file (see stackoverflow). |
@czmotig if you type |
Yes,
|
@czmotig If you create a brand new web application does TagHelper IntelliSense light up for you? Also, to note, |
I'm sorry it works now, I did not know Edit: although Razor Language Services is still installed and enabled. Not sure if this is what you intended, since you advise to remove the extension before upgrading to 15.3 |
Thanks for pointing this out. This is intended. I will update the main post to explain this. |
I do not know if this is related to Razor Tooling or something else. I noticed that Wrap in Div (Alt-Shift-W) appears to have a bug. The opening div tag has 2 additional spaces
This does not happen always. It happens when the wrapping is attempted in a code block following @using e.g.
Could somebody try to reproduce it? Just put an input tag in a using block select it and press Alt-Shift-W |
Hi @tomeks666 - moved your issue to https://github.com/aspnet/Razor/issues/1723 |
I'm closing and locking this issue because this provides a good summary of the issues with upgrading from the gallery extension -> VS 15.3 If you have other problems please open separate issues or post them to VS feedback |
What's Broken?
Anyone that used our preview of the Razor Language Services and upgraded to Visual Studio 15.3 this week, you may find that the ASP.NET Core Razor editing experience has regressed.
This may include:
@namespace
and@page
This is due to a conflict with the older Razor Language Services extension and the version that now ships as part of the Web Tools in the box.
You no longer need the marketplace-based extension to get the full Razor editing experience. it is included with Visual Studio 15.3.
If You Haven't Upgraded
If you haven't upgraded to 15.3 yet, you should remove the Razor Language Services extension before doing so. This will ensure that all of the old files are removed prior to getting the new version.
If You Are Already Broken
First of all, our apologies. We made a mistake in how we published the original extension to the marketplace. It was our goal from the beginning for this to upgrade smoothly and we didn't catch that this wasn't working.
If you are here, the best fix is to repair VS.
More
Repair
After Repair
If this it not working after a repair, please tell us about it here or via VS Feedback.
You should still see the see the 'Razor Language Services' extension as installed after doing a repair
The text was updated successfully, but these errors were encountered: