BSynchro.Authorization
8.4.1
dotnet add package BSynchro.Authorization --version 8.4.1
NuGet\Install-Package BSynchro.Authorization -Version 8.4.1
<PackageReference Include="BSynchro.Authorization" Version="8.4.1" />
<PackageVersion Include="BSynchro.Authorization" Version="8.4.1" />
<PackageReference Include="BSynchro.Authorization" />
paket add BSynchro.Authorization --version 8.4.1
#r "nuget: BSynchro.Authorization, 8.4.1"
#:package BSynchro.Authorization@8.4.1
#addin nuget:?package=BSynchro.Authorization&version=8.4.1
#tool nuget:?package=BSynchro.Authorization&version=8.4.1
Package Description
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net8.0
- BSynchro.Cache (>= 8.3.1)
- BSynchro.Common (>= 8.3.3)
- BSynchro.Identity.Public (>= 6.3.1)
- BSynchro.MessageBus.Hosting (>= 8.3.5)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on BSynchro.Authorization:
| Package | Downloads |
|---|---|
|
BSynchro.Tables.Core
A tool for Querying Trees (database level), generated from excel tables uploaded from ProductSetup ( Tables, Rate Tables, Score Tables). |
|
|
BSynchro.CQRS
Package Description |
|
|
BSynchro.Crm.Core.Infrastructure
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 8.4.1 | 0 | 11/19/2026 |
| 8.4.0 | 285 | 9/28/2026 |
| 8.3.5 | 234 | 9/1/2026 |
| 8.3.4 | 784 | 8/6/2026 |
| 8.3.3 | 524 | 7/27/2026 |
| 8.3.2 | 160 | 7/10/2026 |
| 8.3.1 | 263 | 6/24/2026 |
| 8.3.0 | 225 | 6/22/2026 |
| 8.2.1 | 310 | 5/12/2026 |
| 8.2.0 | 277 | 5/8/2026 |
| 8.0.5 | 140 | 7/10/2026 |
| 8.0.4 | 744 | 9/19/2025 |
| 6.4.1 | 0 | 11/19/2026 |
| 6.4.0 | 127 | 9/28/2026 |
| 6.3.2 | 181 | 7/27/2026 |
| 6.3.1 | 155 | 7/10/2026 |
| 6.3.0 | 160 | 6/22/2026 |
| 6.1.0 | 182 | 5/8/2026 |
| 6.0.14 | 165 | 7/13/2026 |
Behaviour change in role matching: with the And operator only the criteria a role fills (users, profiles, organization units) are combined, for inclusion and elimination alike. A role naming only profiles now reaches every holder of those profiles; before, And treated an empty criterion as not matched, so such a role reached nobody. A side that fills nothing still includes nobody and eliminates nobody. Or is unchanged. See docs/breaking-changes/role-and-filled-criteria.md.