Visual Studio 2015 crashes when opening angle bracket - editor

as soon as I open an angle bracket in a cshtml file, Visual Studio crashes.
I deleted the .suo file but no change. I also deactivated every editor related add-in.

turned out that the asp.net and web tools beta 7 caused the problem. I also had problems loading projects what took me to this answer.
Installing english langugage pack and switching VS to english helped me.

Related

Syntax highlighting stopped working in Blazor Server project

I am using Visual Studio 2019 16.8.1 and the project targets NET 5.0.
The whole code section is highlighted. Is this normal?
I just re-opened the file/re-opened Visual Studio. #Brian Yes there was ambiguity but i think a broken build somewhere

Microsoft Visual Studio Community 2019 CodeLens reference counter incorrect

I have a Windows Forms App with .Net Framework 4.8 and suddenly I realized that only a vertical line appears instead of the reference counter. Any idea how to fix it?
This applies to most of my solutions,but not all. I also noticed that if I reinstall Visual Studio it works after the first start, but once I close it and open it again the error comes back.
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE>devenv /resetuserdata" solved my problem.

Visual Studio 2015 Crashing when opening old razor views

I've been trying to install VS 2015 Enterprise edition on my computer but keep running into an issue. Hunting through SO for the last 24 hours, I've already tried the devenv.exe /ResetUserData & clearing the VS cache fixes, uninstalling enterprise edition and installing professional edition (which still failed for the same reason) and then reinstalling enterprise edition. I've tried deleting the .vs folder before opening the solution, ensuring that the MVC versions in the /Views/ web.config matches the version of the sites web.config (MVC 5.2.3.0).
As of this morning, I've noticed that it only crashes when I try to open a razor view that wasn't created through Visual Studio 2015 (I was using VS 2012 previously, and I'm trying to work on this project in 2015 now that I have a license). I can right-click in the solution explorer to create a brand new view and write anything I want in it with intellisense and save it, and open it back up without any issues.
I get the whole "An exception has occurred, this may be caused by an extension" message and then visual studio restarts if I try to open up a view that was already created through VS 2012.
I've tried looking inside of the log that it provides but I'm a newer developer so I can't really deduce anything from it..I'll attach it if anyone else can make anything of it.
MS VS Enterprise 2015 - Version 14.0.25029.00 Update 2 RC - .NET Framework Version 4.6.01055
I just cleared out the ActivityLog.XML and forced the error to get a fresh set of details - http://pastebin.com/j7RbGJFP
I found the answer in this blog post - https://blogs.msdn.microsoft.com/webdev/2016/01/12/visual-studio-keeps-showing-suggested-extensions/. It has to do with the extensions suggestion - it turns out if you have files not included in your project, you can't view them because of a bug introduced through the extensions suggestion. If you turn that off and include the views in the project, VS won't crash and you'll have intellisense.

Why is editing Umbraco templates in Visual Studio slow?

I've created an Umbraco 7.1.8 in Visual Studio 2013 using MVC templates. When I edit the templates in Visual Studio the editor slows right down and VS shows a permanent 13% usage in Task Manager. If it helps, I'm using Windows 8.1 64-bit on a machine with a 2.3GHz quad-core cpu. Other projects work fine.
Any help/suggestions would be appreciated.
Jason
Okay, found out what the problem was. It turns out if you don't include the .cshtml file in your Visual Studio project (just edit it with Show All Files enabled), you don't get Intellisense and it results in the CPU usage and performance issue I described.
So basically, if you're editing files in Visual Studio, make sure they're included in the project (not greyed out in the Solution Explorer). I'll accept this as the answer as soon as it lets me.

Copy and paste Razor markup in Visual Studio 2010 SP1 is extremely slow

Any time I try to paste anything in a CSHTML file that contains Razor markup or targets a line inside a code block - the entire Visual Studio freezes for almost a minute.
I've applied SP1 for Visual Studio. I'm using ASP.NET MVC 3.
I also only have this problem on a single computer so I'm guessing there's some sort of application or version mismatch I'm simply not seeing. I'm running ReSharper and upgraded it to 6.0 to no avail (though the Razor code inspection works and is really nice).
It's only if I paste a line containing Razor markup that the issue occur. I get no errors on the copy operation, and if I'm pasting regular HTML without Razor markup or outside code blocks in the very same file there're no issues whatsoever. No problems pasting in any other kinds of files like .cs or .aspx. Freshly created MVC 3 projects suffer as well as existing old projects.
I resolved this a while ago but I don't recall exactly which component was the issue - but it was either SP1 for Visual Studio that was in fact not RTM (though it wasn't obvious when looking at the about dialog hence the difficulty in figuring out) or, more likely according to my memory, a pre-RTM version of MVC 3 installed, also not obvious at all when looking through the installed components list.
It took some manual work to get all the related components uninstalled, including some registry hacks, before reinstalling the RTM version and then the problem disappeared. I did not have to reinstall Visual Studio or any of my addons.
Hope this helps someone with similar problems, carefully investigate the exact build numbers of the suspected components. They may in fact be pre-RTM :9
Have you tried to reset the Visual Studio settings? I can't promise this will help but I think it would be worth a try (devenv.exe /ResetSettings). If that doesn't help, I think you will have to re-install Visual Studio.

Resources