How to resolve “Could not load file or assembly Microsoft.CodeAnalysis, version=…” in Visual Studio 2015

Do you find yourself unable to do a “ctrl + .” for code suggestions in VS 2015? An error message comes up saying the following:

Could not load file or assembly ‘Microsoft.CodeAnalysis, version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

For some developers, you can still build and develop but you can’t get “ctrl + .” to work for you. Below are suggestions for fixing this bug.

Option 1:

If you’re working on a web project, ASP.NET uses the nuget package Microsoft.CodeDom.Providers.DotNetCompilerPlatform to update the Microsoft.CodeAnalysis assemblies. So updated the DotNetCompilerPlatform package.

In Visual Studio:

Tools-> Nuget Package Manager -> Package Manager Console

and then type:

Install-Package Microsoft.CodeDom.Providers.DotNetCompilerPlatform

Option 2:

  1. Go to you project folder in Windows Explorer
  2. Delete the packages folder in your Project Folder
  3. Go back to Visual Studio, Right-Click on your solution and select “Restore Nuget Packages”

Option 3:

Update to Visual Studio 2015 Update 3.  Here is a link: Download from here


Kindly indicate the option that works for you in the comment section below.

Here is a collection of places you can buy bitcoin online right now.


Oludayo Alli

Oludayo Alli is the Chief Solutions Architect at DevCrux Solutions, a programmer with more than seven years experience, a tutor and a mentor. He works with Microsoft Technologies and he's a lover of Windows Phone. He loves to collaborate, so do not hesitate to contact him at oludayo[at]devcrux[dot]com

2 thoughts on “How to resolve “Could not load file or assembly Microsoft.CodeAnalysis, version=…” in Visual Studio 2015

  • avatar
    July 6, 2017 at 4:56 am

    I did NOT have KB3072630 installed, so the error was coming from elsewhere, but the re-register of the application solved my problem immediately.

  • avatar
    May 17, 2017 at 6:50 pm

    Thank you for posting, Option 1 worked for me.
    Required a restart of VS to take effect.

Leave a Reply