Skip to content

Commit

Permalink
Version 5.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
JonPSmith committed May 31, 2023
1 parent bc77524 commit 65df7a7
Show file tree
Hide file tree
Showing 4 changed files with 17 additions and 12 deletions.
10 changes: 6 additions & 4 deletions AuthPermissions.AspNetCore/CreateNuGetRelease.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,17 @@
<package xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
<metadata>
<id>AuthPermissions.AspNetCore</id>
<version>5.0.0-preview012</version>
<version>5.0.0</version>
<authors>Jon P Smith</authors>
<product>AuthPermissions.AspNetCore</product>
<copyright>Copyright (c) 2021 Jon P Smith</copyright>
<description>Provides extra authorization and multi-tenant features to a ASP.NET Core application.</description>
<releaseNotes>
- BREAKING CHANGE(small): If you are using sharding with your multi-tenant app, then read the UpdateToVersion5.md file.
- New feature: You can use any database provider supported by EF Core, not just SQLServer and Postgres - see documentation for more details
</releaseNotes>
- BREAKING CHANGE(medium): If you are using sharding with your multi-tenant app, then read the UpdateToVersion5.md file.
- New feature: You can now use a custom database provider with the AuthP library - see documentation for more details.
- New feature: It easier to setup sharding / hybrid multi-tenant application via extension method called SetupMultiTenantSharding
- New feature: Ability to replace parts of the sharding services, e.g. store sharding data in a database instead of a json file.
</releaseNotes>
<license type="expression">MIT</license>
<projectUrl>https://github.com/JonPSmith/AuthPermissions.AspNetCore</projectUrl>
<icon>images\AuthPermissionsAspNetCoreNuGetIcon.png</icon>
Expand Down
10 changes: 6 additions & 4 deletions AuthPermissions.AspNetCore/MultiProjPack.xml
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,17 @@
<!-- See documentation for all the possible values -->
<metadata>
<id>AuthPermissions.AspNetCore</id>
<version>5.0.0-preview022debug</version>
<version>5.0.0</version>
<authors>Jon P Smith</authors>
<product>AuthPermissions.AspNetCore</product>
<copyright>Copyright (c) 2021 Jon P Smith</copyright>
<description>Provides extra authorization and multi-tenant features to a ASP.NET Core application.</description>
<releaseNotes>
- BREAKING CHANGE(small): If you are using sharding with your multi-tenant app, then read the UpdateToVersion5.md file.
- New feature: You can use any database provider supported by EF Core, not just SQLServer and Postgres - see documentation for more details
</releaseNotes>
- BREAKING CHANGE(medium): If you are using sharding with your multi-tenant app, then read the UpdateToVersion5.md file.
- New feature: You can now use a custom database provider with the AuthP library - see documentation for more details.
- New feature: It easier to setup sharding / hybrid multi-tenant application via extension method called SetupMultiTenantSharding
- New feature: Ability to replace parts of the sharding services, e.g. store sharding data in a database instead of a json file.
</releaseNotes>
<license type="expression">MIT</license>
<projectUrl>https://github.com/JonPSmith/AuthPermissions.AspNetCore</projectUrl>
<icon>images\AuthPermissionsAspNetCoreNuGetIcon.png</icon>
Expand Down
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,9 @@ The AuthP is an open-source library under the MIT licence (and remain as a open-

The AuthP library is being built in versions (see [roadmap](https://github.com/JonPSmith/AuthPermissions.AspNetCore/discussions/2)). If you have already built your application using an older version, then you need to look at the following "how up update" documents

- From Migrating from AuthPermissions.AspNetCore 1.* to 1.0 see [UpdateToVersion2.md](https://github.com/JonPSmith/AuthPermissions.AspNetCore/blob/main/UpdateToVersion2.md)
- From Migrating from AuthPermissions.AspNetCore 2, 3 or 4.* to 5.0 see [UpdateToVersion3.md](https://github.com/JonPSmith/AuthPermissions.AspNetCore/blob/main/UpdateToVersion5.md)
- From Migrating from AuthPermissions.AspNetCore 2.* to 3.0 see [UpdateToVersion3.md](https://github.com/JonPSmith/AuthPermissions.AspNetCore/blob/main/UpdateToVersion3.md)
- From Migrating from AuthPermissions.AspNetCore 1.* to 1.0 see [UpdateToVersion2.md](https://github.com/JonPSmith/AuthPermissions.AspNetCore/blob/main/UpdateToVersion2.md)

The AuthP library also:

Expand Down
6 changes: 3 additions & 3 deletions UpdateToVersion5.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Updating your code from AuthPermissions.AspNetCore 4.* to 5.0

Version 5.0.0 of the AuthPermissions.AspNetCore library (shortened to **AuthP** from now on) contains various new features (LINK TO roadmap), but this document only covers **BREAKING CHANGES** in version 5.0.0, which are in _sharding_ multi-tenant applications.
Version 5.0.0 of the AuthPermissions.AspNetCore library (shortened to **AuthP** from now on) contains various new features (LINK TO roadmap), but this document covers **BREAKING CHANGES** in version 5.0.0, which are in _sharding_ multi-tenant applications. I purposely cause compile errors so that the breaking changes are obvious to you.

_NOTE: I purposely cause compile errors so that the breaking changes are obvious to you._
_NOTE: The fill list of changes !!! Links to article and documentation ._

## TABLE OF CONTENT

Expand Down Expand Up @@ -43,7 +43,7 @@ Because of the new custom database feature the `DatabaseType` in your shardingse

The problem with Postgres database is `Npgsql.EntityFrameworkCore.PostgreSQL` so the short name is `PostgreSQL`, not `Postgres`

_Solution:_ make sure your shardingsetting.json entries that use Postgres has the `DatabaseType` set to "PostgreSQL".
_Solution:_ make sure your shardingsetting.json entries that use Postgres has the `DatabaseType` set to "PostgreSQL".
_NOTE: If you don't change this you will have an exception with the following message._

```text
Expand Down

0 comments on commit 65df7a7

Please sign in to comment.