Could not load file or assembly Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0

Question

After update to the new package Microsoft.EntityFrameworkCore.SqlServer 1.1.2 I got error when try to create DBContext:

System.IO.FileLoadException occurred HResult=0x80131040
Message=Could not load file or assembly 'Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) Source=Microsoft.EntityFrameworkCore StackTrace: at Microsoft.EntityFrameworkCore.DbContext..ctor(DbContextOptions options) at Services.Infrastructure.Data.SqlServerDbContext..ctor(DatabaseOptions databaseOptions) in C:\src\backend\Packages\Services.Infrastructure\Data\SqlServerDbContext.cs:line 16 at Translations.Api.Data.TranslationsDbContext..ctor(DatabaseOptions databaseOptions) in C:\src\backend\Modules\Translations\Translations.Api\Data\TranslationsDbContext.cs:line 16

My base DbContext

public class SqlServerDbContext : DbContext
{
    private readonly DatabaseOptions _databaseOptions;

    protected SqlServerDbContext(DatabaseOptions databaseOptions)
    {
        if (string.IsNullOrEmpty(databaseOptions.ConnectionString))
            throw new Exception("Database connection string is missed.");

        _databaseOptions = databaseOptions;
    }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    {
        optionsBuilder.UseSqlServer(_databaseOptions.ConnectionString);
    }
}

Database options that I use

public class DatabaseOptions
{
    public string ConnectionString { get; set; }
}

Place where I create instance of context

 var dbOptions = new DatabaseOptions { ConnectionString = _connectionString };
 DbContext = (TContext) Activator.CreateInstance(typeof(TContext), dbOptions);
// where TContext is derived class from SqlServerDbContext

All my packages are updated. Visual Studio 2017 15.2 (26430.6). Before upgrade to 1.1.2 everything works fine. Please help to solve the problem.

Please give information about what the projects is you're consuming the package from? .net standard / .net framework library / console / web application? — Martin Ullrich, May 16 '17 at 08:14
FWIW - This can happen if you played with upgrading your NuGets, then decided to use your source control tools to revert back to your 'working' project (reverted packages.config and the .csproj file) but then forgot to revert the binding redirects out of the web.config — bkwdesign, May 07 '20 at 20:48
It would be great if this error contained helpful information, such as the incompatible packages, and at least a more clear error message. — Josh Noe, Dec 11 '20 at 16:53
I noticed in the error the Microsoft.Extensions.DependencyInjection.Abstractions 2.0.0 version was requested. Downgraded to that package in NuGet, cleared the NuGet cache. Also cleared all binding redirects in web.config to have VisualStudio update the config clicking each compiler warning. — flodis, Jul 18 '23 at 01:35

score 100 · Accepted Answer · answered May 16 '17 at 08:38

100

Since you're using the project in a .net framework library, there's an issue with auto-generated binding redirects (might be resolved in the upcoming 15.3 update / 2.0 .net core CLI). To work around it, add this in your cpsroj file (preferably before any <Import> element for a .targets file if present):

<PropertyGroup>
  <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
  <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
</PropertyGroup>

This should force MSBuild to create / update a YourProject.dll.config file containing the necessary binding redirects.

answered May 16 '17 at 08:38

Martin Ullrich

94,744
25
252
217

1

Thanks. Solved my problem around version 2.0.0. I had version 2.1.0 installed. – Azhar Khorasany Jul 04 '18 at 09:45
1

I installed a lib version through the CLI an ai got the lattest version of the library, however, I had to downgrade the version to match my development target wich was ASP.NET Core 2.0 (Not 2.1). – Aaron C Jul 11 '18 at 19:14
1

Is this only required for the database project or is it needed for all referenced projects? – Tigerware Nov 08 '18 at 14:54
1

For all "non-sdk" ("classic") csproj files that reference .net standard assemblies. So it may be required for all projects referencing the projects that need this. – Martin Ullrich Nov 08 '18 at 16:35
Does 15.3 refer to Visual Studio here? Any idea when it will be fixed? ~https://stackoverflow.com/questions/60217182/could-not-load-file-or-assembly-microsoft-extensions-dependencyinjection-abstra – Kirsten Mar 04 '20 at 04:15
After lots of research and finally I fixed this issue, see my answer below: https://stackoverflow.com/a/65434701/1815500 – Leon Dec 24 '20 at 06:22
Microsoft Visual Studio Professional 2019 - Version 16.8.3. The UI shows this property checked even if the tag it is not present in the csproj. Adding the AutoGenerateBindingRedirects tag in the csproj, the UI is then capable of setting it. It did not solve my binding issues though... – pasx May 26 '21 at 14:39

Luis Gouveia · Answer 2 · 2021-03-17T08:18:33.843

If you're working with Azure Functions in .NET Core this will work

If you're not using the .net framework library, but the .net core library, the accepted solution will not work because "you shouldn't be setting the property AutoGenerateBindingRedirects on a netcoreapp project as binding redirects aren't even a thing in netcoreapp, they are only a concept in .NET Framework" (source: https://github.com/microsoft/ApplicationInsights-dotnet/issues/1699#issuecomment-592693436).

Try this:

Uninstall Microsoft.Extensions.DependencyInjection.Abstractions
Uninstall Microsoft.Extensions.DependencyInjection

Although this seems like a radical solution, it works because the library is already indirectly installed through Microsoft.Azure.Functions.Extensions:

Important: Do not try to solve this issue by upgrading .NET Core from 3.1 to 5.0. Azure functions are still not supported in .NET 5.0. A patch is coming in early 2021: https://github.com/Azure/azure-functions-host/issues/6674#issuecomment-712596112

EDIT: Azure functions are now supported in .NET Core (unless you're using durable entities, in that case you'll have to wait for .NET 6.0):

Today (10/3/2021), we announced support for running production .NET 5 apps on Azure Functions. https://techcommunity.microsoft.com/t5/apps-on-azure/net-on-azure-functions-roadmap/ba-p/2197916

Downgrading other dependencies works for me ref: https://github.com/Azure/Azure-Functions/issues/1729 — Tomasz Kaniewski, Feb 01 '21 at 10:39
Thanks, fix worked for me after adding DI to an Azure Function — Michael, Feb 08 '21 at 15:35

score 15 · Answer 3 · answered Nov 30 '19 at 13:20

15

I Googled my exception below, and it brought me to this stakoverflow post.

System.IO.FileNotFoundException: 'Could not load file or assembly 'Microsoft.Extensions.OptionsModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file specified.'

I had the relevant Binding Redirects but if I Delete all bin/obj folders it worked fine afterwards.

answered Nov 30 '19 at 13:20

metoyou

639
1
7
22

4

I had +1 this answer 2 years ago and it's still relevant. And somehow, it happens every time Windows updates with a new .NET SDK. Today? .NET 6.0. `git clean -xfd` does the trick. – jsgoupil Apr 13 '22 at 02:00

albin · Answer 4 · 2020-10-15T05:39:45.527

9

This is an old thread but I had a similar same issue after I updated my Azure function from dotnet core version 3 to 3.1.

Error message: Could not load file or assembly 'Microsoft.Extensions.DependencyInjection.Abstractions, Version=3.1.9.0

In this case you need to update the Azure function version to 'v3' in .proj file.

edited Oct 15 '20 at 05:39

answered Oct 15 '20 at 05:22

albin

607
6
10

3

This helped me out, but I need to add something now that Version 5.x of Microsoft.Extensions.DependencyInjection is available now. I had to downgrade to 3.10.0, but I imagine any 3.x version will work just as well. 5.x does not work and results in the same issue. This will probably be resolved with Azure Functions for dotnet 5 is availalbe. – Oxymoron Nov 23 '20 at 15:31
What to do here ? `Microsoft.Extensions.DependencyInjection 7.0.0` – ispostback Dec 15 '22 at 10:57

score 5 · Answer 5 · answered Jan 11 '22 at 03:15

I've been getting a similar issue using Azure functions 3.0.13

I kept getting the error System.IO.FileNotFoundException: 'Could not load file or assembly 'Microsoft.Extensions.Options, Version=6.0.0.0

I added a direct reference to the package via NuGet and then had to add this to my project.csproj file to make everything work. I can't take credit for this fix. I found it somewhere else a while ago, but I can't recall from where.

<PropertyGroup>
    <_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>
</PropertyGroup>

This worked for me but later found better approach to just preserve what is need ` ` — Mayur Pawar, Oct 10 '22 at 12:16

score 4 · Answer 6 · answered Oct 10 '20 at 18:03

4

I was having this problem. But the packet was Microsoft.Extensions.Primitives. In my case I installed it in my Project and in my Project test from nuget. Maybe could help someone.

answered Oct 10 '20 at 18:03

Edvan Souza

1,058
9
11

In my case also this `Microsoft.Extensions.Primitives` assembly couldn't be loaded. Execute `Update-Package -reinstall -Project MyProject` from Package Manager Console resolved the issue... – Rohim Chou Aug 09 '21 at 05:04
1

I had problem with Microsoft.Extensions.Options while unit testing after upgrading a nuget package. Resolved when I added that same package into my Test project (part of the same solution), even though it wasn't directly used. I then removed the package from the Test project and it still worked. – GreenRock Nov 09 '22 at 04:20

score 2 · Answer 7 · answered Jun 22 '20 at 12:34

2

For me, what did it was to downgrade all the packages support .Net Standard to 2.2.0 from 3.x.x i guess the 3.x packages relevant to a different version of .Net standard which does not support ,net framework.

answered Jun 22 '20 at 12:34

Yosi Golan

129
8

score 2 · Answer 8 · answered Sep 28 '21 at 13:46

2

It is a cracy thing, but for me what really worked was upating all packages that begins with Microsoft, since I updated my project to run over .Net 4.7.2, Then I just right click on Solution and Clean and Build again.

answered Sep 28 '21 at 13:46

Ruben

139
1
3

score 1 · Answer 9 · answered Feb 01 '21 at 10:41

1

If Luis Gouveia solution doesn't work for you, try downgrading other dependencies included in the project. There are some compatibility issues with .NET standard.

Ref: https://github.com/Azure/Azure-Functions/issues/1729

answered Feb 01 '21 at 10:41

Tomasz Kaniewski

1,065
8
16

mandarin software · Answer 10 · 2021-08-07T19:50:10.067

0

Here some solves :

1-I updated my packages from NuGet to latest version and working 100%.

2- make these editing in config :

<PropertyGroup>
  <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
  </PropertyGroup>

3-Delete all bin and objct folders then clean solution and finally run , hope this will be work .

edited Aug 07 '21 at 19:50

answered Oct 10 '20 at 02:15

mandarin software

197
8

score 0 · Answer 11 · answered Dec 24 '20 at 06:19

I had same problem and finally fixed with below solution

Install "System.ComponentModel.Annotations" version 4.4.1 in a temporary project to get the file of "System.ComponentModel.Annotations.dll", then copy this file to your real project and then change your project reference to point this file instead of the original NuGet path
Then in your web.config add below code that redirec

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <publisherPolicy apply="no" />
      <dependentAssembly>
        <assemblyIdentity name="System.ComponentModel.Annotations" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.5.0.0" newVersion="4.2.1.0" />
      </dependentAssembly>
    </assemblyBinding>

score 0 · Answer 12 · answered May 04 '21 at 15:06

I was working on my simple .Net 5.0 Console app and while modifying my project's namespace the "auto-installation" added only the Microsoft.Extensions.DependencyInjection.Abstraction not the package nuget Microsoft.Extensions.DependencyInjection

It took me a while to realise that...

score 0 · Answer 13 · answered Jan 21 '22 at 10:48

0

I had the same problem with a .Net Framework website that included an assembly using EFCore 3.1.22. I resolved the problem by putting the assembly redirects in the web.config.

answered Jan 21 '22 at 10:48

stevie_c

990
1
8
15

score 0 · Answer 14 · answered Jun 12 '23 at 15:07

I got this error message in my .NET 6 Azure Function App:

Could not load file or assembly 'Microsoft.Extensions.Primitives, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.

As this was the first page that came up when googling the issue, I thought it might help posting my solution. All upgrading, downgrading and re-installing of nuget-packages was unsuccessful. I eventually stumbled across some MS documentation where it says

If you re-target a project to a different version of .NET, your references may not resolve properly in some cases. Explicit fully qualified references to assemblies often cause this issue, but you can resolve it by removing the references that don't resolve and then adding them back to the project.

This was the line in my project file causing the problem:

<PackageReference Include="Microsoft.Extensions.Primitives" Version="8.0.0-preview.4.23259.5" />

Removing the version solved the issue:

<PackageReference Include="Microsoft.Extensions.Primitives" />

score 0 · Answer 15 · answered Aug 08 '23 at 12:16

Deleting the "app.config" file in the project folder solved the problem. It contained references to a different version of the file, while it should have been a certain one given the Nuget package setup I had.

These *.config files are auto-generated, and the program runs without them. The "packages.config" is different.

Always beware when these config files exist in your project, and treat them with due suspicion.

score 0 · Answer 16 · answered Sep 01 '23 at 16:27

I had to upgrade the package in the NuGetPackage Manager and it worked for me

System.IO.FileLoadException
  HResult=0x80131040
  Message=Could not load file or assembly 'Microsoft.Extensions.Primitives, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  Source=Microsoft.Extensions.Configuration
  StackTrace:
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at Microsoft.Extensions.Hosting.HostBuilder.InitializeHostConfiguration()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at Data_Export_Refinity.App..ctor() in C:\Users\Nathaniel\source\repos\........\App.xaml.cs:line 25
   at Data_Export_Refinity.App.Main() in C:\Users\Nathaniel\source\repos\..........\obj\Debug\App.g.cs:line 49

Could not load file or assembly Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0

16 Answers16

I had to upgrade the package in the NuGetPackage Manager and it worked for me

Linked

Related