Sencilla.Component.Security.Mssql
10.0.37
dotnet add package Sencilla.Component.Security.Mssql --version 10.0.37
NuGet\Install-Package Sencilla.Component.Security.Mssql -Version 10.0.37
<PackageReference Include="Sencilla.Component.Security.Mssql" Version="10.0.37" />
<PackageVersion Include="Sencilla.Component.Security.Mssql" Version="10.0.37" />
<PackageReference Include="Sencilla.Component.Security.Mssql" />
paket add Sencilla.Component.Security.Mssql --version 10.0.37
#r "nuget: Sencilla.Component.Security.Mssql, 10.0.37"
#:package Sencilla.Component.Security.Mssql@10.0.37
#addin nuget:?package=Sencilla.Component.Security.Mssql&version=10.0.37
#tool nuget:?package=Sencilla.Component.Security.Mssql&version=10.0.37
Sencilla.Component.Security.Mssql
SQL Server schema (.sql source) for the Sencilla Security component.
Owns the RBAC objects in the [sec] schema:
sec.Role— named roles (identity starts at 100)sec.Action— named actions (Read, Write, Delete, …)sec.Area— named areas / resource groupssec.Matrix— permission rules linking a role, resource, and action (with optional constraint expression)sec.UserRole— assignment of roles to users (FK tosec.User)
Depends on [[Sencilla.Component.Users.Mssql]] — sec.UserRole.UserId references sec.User.Id, so the Users package must be compiled into the same model.
How it works
This package ships schema source, not a dacpac. When referenced, its build/*.props is auto-imported and compiles the sql/ source into the consuming project's own model. So all sec.* RBAC objects land physically in the consumer's dacpac — self-contained: deploys with no IncludeCompositeObjects flag and no co-located dacpacs.
Consume
<PackageReference Include="Sencilla.Component.Users.Mssql" Version="10.0.*" />
<PackageReference Include="Sencilla.Component.Security.Mssql" Version="10.0.*" />
Deploy normally:
sqlpackage /Action:Publish /SourceFile:App.dacpac ...
Reference data (seed)
Role, Action, and Area seed rows ship as package content under seed/ (not compiled into the model). The package auto-defines the SQLCMD variable $(Sencilla_Component_Security) pointing at that seed folder. Run it from your post-deployment script:
:r $(Sencilla_Component_Security)/ApplyData.sql
The seed scripts are idempotent and inline at build time, so they run as part of the consumer's normal post-deployment.
Learn more about Target Frameworks and .NET Standard.
-
.NETStandard 2.1
- Sencilla.Component.Users.Mssql (>= 10.0.37)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.