Skip to content

fix: correct NuGet package tags - #45

Merged
giammin merged 1 commit into
mainfrom
fix/package-tags
Oct 22, 2026
Merged

giammin merged 1 commit into
mainfrom
fix/package-tags

Conversation

@giammin

@giammin giammin commented Oct 22, 2026

Copy link
Copy Markdown
Owner

Problem

The provider csproj files used ${PackageTags}, which is not MSBuild syntax, so the published nuspec contained the literal text (<tags>${PackageTags} dapper sql server</tags>). The PostgreSQL package was also tagged sql server.

Changes

  • ${PackageTags} -> $(PackageTags) in the Dapper, SQL Server and PostgreSQL csproj files.
  • PostgreSQL package: dapper;postgresql.
  • SQL Server package: dapper;sqlserver instead of dapper;sql server. NuGet tags are space-separated, so sql server was published as two tags, sql and server.

Verification

Release build (0 warnings), tags read from each generated nuspec:

Package Tags
AspNetCore.DataProtection.CustomStorage aspnetcore dataprotection storage
...Dapper aspnetcore dataprotection storage dapper
...Dapper.PostgreSQL aspnetcore dataprotection storage dapper postgresql
...Dapper.SQLServer aspnetcore dataprotection storage dapper sqlserver

Closes #21

The provider csproj files used ${PackageTags}, which is not MSBuild
syntax, so the published nuspec contained the literal text. Use
$(PackageTags), tag the PostgreSQL package postgresql instead of
sql server, and tag the SQL Server package sqlserver: NuGet tags are
space-separated, so "sql server" was published as two tags.

Closes #21
@giammin
giammin merged commit d5eec83 into main Oct 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Package tags contain the literal text ${PackageTags}

1 participant