search

JonPSmith / AuthPermissions.AspNetCore

This library provides extra authorization and multi-tenant features to an ASP.NET Core application.
https://www.thereformedprogrammer.net/finally-a-library-that-improves-role-authorization-in-asp-net-core/
MIT License
788 stars 159 forks source link

Support .NET 8 #95

Closed raulidavid closed 10 months ago

raulidavid commented 10 months ago

Jiban.Domain -> Microsoft.EntityFrameworkCore 8.0.0 -> Microsoft.EntityFrameworkCore.Abstractions (>= 8.0.0) Jiban.Domain -> AuthPermissions.AspNetCore 6.0.0 -> Npgsql.EntityFrameworkCore.PostgreSQL 7.0.0 -> Microsoft.EntityFrameworkCore.Abstractions (>= 7.0.0 && < 8.0.0). @JonPSmith

JonPSmith commented 10 months ago

Hi @raulidavid,

I will update AuthP library to .NET 8, but I have to update three of my libraries that AuthP uses to .NET 8 first. I'm currently waiting for the Npgsql.EntityFrameworkCore.PostgreSQL NuGet to get to .NET 8.

raulidavid commented 10 months ago

@JonPSmith https://www.nuget.org/packages/Npgsql.EntityFrameworkCore.PostgreSQL#versions-body-tab is ready for .NET 8.0 😎

JonPSmith commented 10 months ago

I have released various libraries see my twitter feed, some of which I needed to make AuthP supports .NET 8. However I found some breaking changes in the .NET 8. EF Core release that stops from AuthP working with .NET 8.

I will look at this but it will take some time. When I have solved these problems I will close this issue as completed.

JonPSmith commented 10 months ago

I have released AuthPermissions.AspNetCore 6.1.0. The release adds .NET 8 support to this library, so version 6.1.0 supports .NET 6, 7, and 8.

This release took some time because:

  1. Creating libraries that supports multiple .NET releases is complex.
  2. The AuthP library if very big, and its easy to miss a change to NuGet libraries. That's why you MUST have unit tests for each .NET release version.
  3. There were two changes in the .NET 8 EF Core code that caused problems in the unit tests and require extra code.