Visual Studio 2015 Broken Razor Intellisense

This has been recurring for me also and seems to be connected to extension updates but I have not yet been able to blame anything specific. What I have been able to discover is a less intrusive resolution. In my case deleting the contents of this directory allows the IDE to recover: %LocalAppData%\Microsoft\VisualStudio\14.0\ComponentModelCache Edit: I … Read more

Packages not loading after installing Visual Studio 2015 RTM

I have Visual Studio 2012, 2013 and 2015 all installed on my machine. After installing Visual Studio 2013 Update 5, I started getting the “package did not load correctly” error in VS 2013. All I did to get it working was to follow this step: Close all instances of Visual Studio Delete everything in this folder C:\Users\%username%\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache Restart Visual … Read more

Why is the Visual Studio 2015/2017/2019 Test Runner not discovering my xUnit v2 tests

Eliminate discovery exceptions from your inquiries; go to the output Window (Ctrl-Alt-O), then switch the show output from dropdown (Shift-Alt-S) to Tests and make sure there are no discovery exceptions Test|Test settings|Default processor architecture can help if your tests are x86/x64 specific and discovery is triggering bittedness-related exceptions, i.e. not AnyCpu As suggested in this … Read more

Visual Studio 2015 TFS .tfignore file

First, please make sure your .tfignore file created without any problem. This file does not have any suffix. One way to create it suggest you to rename a new.txt file with “tfignore.” It will auto change to right .tfignore file. You can also use the auto automatically generated .tfignore file, follow below steps: In the … Read more

Exception 0xC0000005 from JNI_CreateJavaVM (jvm.dll)

JVM actively uses OS signals (or exceptions in Windows terminology) for its own purposes: for implicit null pointer checks and stack overflow checks; for safepoint polling; for remote memory barriers; etc. SEGV (or exception 0xC0000005) is also generated intentionally on JVM startup to verify certain CPU/OS features. Some OSes or hypervisors had a bug that … Read more