Sencilla.Component.Setting.Mssql
10.0.37
dotnet add package Sencilla.Component.Setting.Mssql --version 10.0.37
NuGet\Install-Package Sencilla.Component.Setting.Mssql -Version 10.0.37
<PackageReference Include="Sencilla.Component.Setting.Mssql" Version="10.0.37" />
<PackageVersion Include="Sencilla.Component.Setting.Mssql" Version="10.0.37" />
<PackageReference Include="Sencilla.Component.Setting.Mssql" />
paket add Sencilla.Component.Setting.Mssql --version 10.0.37
#r "nuget: Sencilla.Component.Setting.Mssql, 10.0.37"
#:package Sencilla.Component.Setting.Mssql@10.0.37
#addin nuget:?package=Sencilla.Component.Setting.Mssql&version=10.0.37
#tool nuget:?package=Sencilla.Component.Setting.Mssql&version=10.0.37
Sencilla.Component.Setting.Mssql
SQL Server schema (.sql source) for the Sencilla Setting component.
Ships the canonical [dbo].[Setting] table — a hierarchical, optionally user-scoped
key/value store (Type / ParentId / Name / Value).
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 dbo.Setting lands physically in the consumer's dacpac — self-contained:
deploys with no IncludeCompositeObjects flag and no co-located dacpacs.
Consume
<PackageReference Include="Sencilla.Component.Setting.Mssql" Version="10.0.*" />
Then deploy normally: sqlpackage /Action:Publish /SourceFile:App.dacpac ...
Notes
[UserId]will be foreign-keyed to[sec].[User]onceSencilla.Component.Users.Mssqlexists (the consuming model that compiles both will already containsec.User, so the FK can simply be uncommented).
Learn more about Target Frameworks and .NET Standard.
-
.NETStandard 2.1
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.