Home/ Questions/Q 8828649
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T07:39:19+00:00

I’ve upgraded EntityFramework from 4.1 to 5 and Upgraded .NET Framework to 4.5 on

  • 0

I’ve upgraded EntityFramework from 4.1 to 5 and Upgraded .NET Framework to 4.5 on local machine everything works perfectly, but when I published my changes on Azure I receive this error:

Server Error in '/' Application.

Could not load file or assembly 'Microsoft.Build.Utilities.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Build.Utilities.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Build.Utilities.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Check your project references for that assembly. Ensure that you have copy local set to true on the properties of that reference. Also, upgrading your Azure SDK and EF may have impacted the versions of the assemblies referenced by the project. Ensure that you have the correct versions referenced in your project as well.

    Found what would potentially be the source of your issue -> especially if you are upgrading your project: http://ivarunsingh.blogspot.com/2011/12/microsoftbuildutilitiesv35-report.html

    • 0