openiddict-core: Error after upgrade to Asp.net core 1.0.0.

Hi there & thanks for your amazing work 😃

I ran into an issue after upgrading asp.net core rc2 -> 1.0.0. yesterday:

When loading my dev-app, the line services.AddOpenIddict<Core.Entities.User, DataAccess.ApoNextDbContext>).DisableHttpsRequirement(); causes

An exception of type ‘System.TypeLoadException’ occurred in OpenIddict.dll but was not handled in user code

Additional information: Der Typ “Microsoft.Extensions.DependencyInjection.Extensions.ServiceCollectionExtensions” in der Assembly “Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60” konnte nicht geladen werden.

(translates as ‘Type … in assebly … could not be loaded’)

I am using Openiddict 1.0.0-alpha2-0331 . Everything was running fine with asp.net core RC2 & OpenIddict alpha 302.

Let me know if you need additional information!

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 1
Comments: 17 (6 by maintainers)

Most upvoted comments

FYI, the “OpenIddict for RTM” packages are now on MyGet.org

kevinchalet on Jun 30, 2016

@moraleslos change project.json to:

"dependencies": {
...
  "OpenIddict": "1.0.0-alpha2-*"
...
}

jaredcnance on Jun 30, 2016

Update 2: Using a proper version of AspNet.Security.OAuth.Validation (1.0.0-alpha3-0181) fixed the issue. My bad, sorry!

I’d recommend using 1.0.0-alpha2-final. It was published yesterday on MyGet and will be pushed soon on NuGet.org.

kevinchalet on Jun 30, 2016

For those who want to try the experimental “OpenIddict for RTM” bits, you can download the corresponding packages here: https://ci.appveyor.com/project/openiddict/openiddict-core/build/1.0.0-alpha2-337/artifacts

kevinchalet on Jun 29, 2016

Not to push but any idea when a new package that targets the RTM bits will be available?

In the next few days. Actually, I already have a working “OpenIddict for ASP.NET Core RTM” prototype, but I’d like to share it with a few testers before releasing it publicly.

kevinchalet on Jun 28, 2016

Hi there & thanks for your amazing work 😃

Haha, thanks 😄

The issue you’re seeing is unfortunately a known one, caused by class name changes in the logging stack (and in a few other places): https://github.com/aspnet/DependencyInjection/issues/411

This incompatibility will be fixed when migrating to the RTM bits. In the meantime, I’d recommend using the ASP.NET Core RC2 packages 👏

kevinchalet on Jun 28, 2016