Sencilla.Component.Users.Mssql
10.0.37
dotnet add package Sencilla.Component.Users.Mssql --version 10.0.37
NuGet\Install-Package Sencilla.Component.Users.Mssql -Version 10.0.37
<PackageReference Include="Sencilla.Component.Users.Mssql" Version="10.0.37" />
<PackageVersion Include="Sencilla.Component.Users.Mssql" Version="10.0.37" />
<PackageReference Include="Sencilla.Component.Users.Mssql" />
paket add Sencilla.Component.Users.Mssql --version 10.0.37
#r "nuget: Sencilla.Component.Users.Mssql, 10.0.37"
#:package Sencilla.Component.Users.Mssql@10.0.37
#addin nuget:?package=Sencilla.Component.Users.Mssql&version=10.0.37
#tool nuget:?package=Sencilla.Component.Users.Mssql&version=10.0.37
Sencilla.Component.Users.Mssql
SQL Server schema (.sql source) for the Sencilla Users component.
Owns the [sec] schema and the user-identity tables:
sec.User— the core identity (email/phone, name, status/type/gender, audit dates)sec.UserAuth— credentials / external logins (PasswordHashnullable)sec.UserClaim,sec.UserContact,sec.UserAddress- reference tables:
sec.UserType,sec.UserStatus,sec.UserGender,sec.UserContactType,sec.UserAddressType
Self-contained — every foreign key targets another sec.* table. This is the keystone
schema component: it creates [sec], so [[Sencilla.Component.Security.Mssql]] and any
database that needs sec.User compile this package into their own 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 sec.* lands physically in the consumer's dacpac — it is self-contained:
deploys with no IncludeCompositeObjects flag and no co-located dacpacs.
Consume
<PackageReference Include="Sencilla.Component.Users.Mssql" Version="10.0.*" />
That's it for schema — sec.* is now part of your model. Deploy normally:
sqlpackage /Action:Publish /SourceFile:App.dacpac ...
Reference data (seed)
Lookup rows (user types / statuses / genders / contact + address types) ship as package
content under seed/ (not compiled into the model). The package auto-defines a SQLCMD
variable (via build/*.props) named after the package — PackageId with .Mssql dropped and
dots replaced by underscores — $(Sencilla_Component_Users), pointing at that seed folder.
It also provides an ordered entrypoint ApplyData.sql. Run it from your post-deployment
script with one line:
:r $(Sencilla_Component_Users)/ApplyData.sql
The seed scripts are idempotent (IF NOT EXISTS ... SET IDENTITY_INSERT) and inline at
build time, so they run as part of the consumer's normal post-deployment.
Related
- [[Sencilla.Component.Geography.Mssql]] —
geo.*(referenced bysec.UserAddresscolumns, no FK) - [[Sencilla.Component.Security.Mssql]] —
sec.Role/sec.UserRole/ ... (depends on this) - [[Sencilla.Component.Setting.Mssql]] —
dbo.Setting(will FK tosec.User)
Learn more about Target Frameworks and .NET Standard.
-
.NETStandard 2.1
- No dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Sencilla.Component.Users.Mssql:
| Package | Downloads |
|---|---|
|
Sencilla.Component.Security.Mssql
SQL Server schema (.sql source) for the Sencilla Security component: RBAC tables (Action / Area / Role / Matrix / UserRole) in the [sec] schema. Compiled into the consuming database's own model (self-contained); generic seed data ships separately. |
GitHub repositories
This package is not used by any popular GitHub repositories.