Sharp.EntityFrameworkCore.DM 10.0.1

Sharp.EntityFrameworkCore.DM

Dameng database provider for Entity Framework Core 10.0.

Live Dameng Validation

The repository includes a direct-run provider validation console at samples/DmProviderValidation. It reads ConnectionStrings:Dm from .NET User Secrets, automatically creates the target user/schema and validation tables, then exercises CRUD, batch operations, queries, transactions, concurrency, cancellation, migrations, identity/sequence generation, nullable values, and provider type round trips.

dotnet user-secrets set "ConnectionStrings:Dm" "<connection string including DBAPassword>" --project .\samples\DmProviderValidation\DmProviderValidation.csproj
dotnet run --project .\samples\DmProviderValidation\DmProviderValidation.csproj

Use a dedicated target user/schema. The program has no command-line options and never prints the connection string.

Status

• Target framework: net10.0
• Provider package version: 10.0.1
• EF Core relational dependency: Microsoft.EntityFrameworkCore.Relational [10.0.5,11.0.0)
• ADO.NET driver dependency: DM.DmProvider 8.3.1.47463
• Current net10.0 validation uses the DM.DmProvider lib/net9.0 asset. Automated tests cover assembly loading and SQL generation; live Dameng database validation requires a separate test environment.

Build

Preferred local validation entrypoint:

powershell -ExecutionPolicy Bypass -File .\scripts\validate-efcore10.ps1

Manual build command:

$env:MSBuildEnableWorkloadResolver='false'
dotnet build .\EFCore.DM.slnx -c Release --no-restore -v minimal

Test

Manual full test command:

$env:MSBuildEnableWorkloadResolver='false'
dotnet test .\EFCore.DM.slnx -c Release --no-build --no-restore -v minimal

The test suite includes query pipeline coverage, provider behavior regression tests, package boundary checks, and runtime compatibility smoke tests for the accepted DM.DmProvider 8.3.1.47463 strategy under net10.0.

Pack

Manual package command:

$env:MSBuildEnableWorkloadResolver='false'
dotnet pack .\src\DM.Microsoft.EntityFrameworkCore\DM.Microsoft.EntityFrameworkCore.csproj -c Release --no-restore -o .\artifacts -v minimal

Release tags must match the package version, for example v10.0.1. The tag pipeline checks this before packing; the project validates its own assembly/package version relationship. The tag pipeline restores the generated package into an isolated package cache and runs scripts/package-consumer-smoke against EF Core 10.0.5.

CI/CD

The GitLab pipeline has the following validation and delivery paths:

• Merge requests: restore, Release build, and the complete unit test suite, with TRX and diagnostic logs retained as artifacts
• main, master, and net10: restore, Release build, and the complete unit test suite
• Git tags: build, test, pack, validate the generated package with an independent consumer, and publish to TAG_NUGET_URL

Required GitLab CI/CD variables:

• TAG_NUGET_URL: publish URL used by tag pipelines, defaults to https://api.nuget.org/v3/index.json
• TAG_NUGET_API_KEY: API key for the tag publish feed

Optional GitLab CI/CD variables:

• NUGET_PROXY: alternate restore source used during CI restore