Sharp.EntityFrameworkCore.DM 10.0.0

Sharp.EntityFrameworkCore.DM

Dameng database provider for Entity Framework Core 10.0.

Sample

The repository includes a runnable data-access sample at samples/DmDataAccessSample.

Preview generated SQL without a live database:

dotnet run --project .\samples\DmDataAccessSample\DmDataAccessSample.csproj

Run the full create, update, delete, and query flow against a dedicated Dameng database:

dotnet run --project .\samples\DmDataAccessSample\DmDataAccessSample.csproj -- --run --init --connection "Server=localhost;User ID=SYSDBA;PWD=SYSDBA001;DATABASE=EFCORE_SAMPLE"

Status

• Target framework: net10.0
• EF Core relational dependency: Microsoft.EntityFrameworkCore.Relational 10.0.0
• ADO.NET driver dependency: DM.DmProvider 8.3.1.37876
• Current net10.0 validation uses the DM.DmProvider lib/net9.0 asset, which is covered by automated runtime compatibility smoke tests in this repository

Build

Preferred local validation entrypoint:

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

Manual build command:

$env:MSBuildEnableWorkloadResolver='false'
dotnet build tests\DM.Microsoft.EntityFrameworkCore.Tests\DM.Microsoft.EntityFrameworkCore.Tests.csproj -c Debug --no-restore -v minimal

Test

Manual full test command:

$env:MSBuildEnableWorkloadResolver='false'
dotnet test tests\DM.Microsoft.EntityFrameworkCore.Tests\DM.Microsoft.EntityFrameworkCore.Tests.csproj --no-build --no-restore

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

Pack

Manual package command:

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

CI/CD

The repository now includes a GitLab CI pipeline in .gitlab-ci.yml with three delivery paths:

• main / master: restore and build only
• Git tags: build, pack, and publish the package to the TAG_NUGET_URL feed
• INTERNAL_PUBLISH_BRANCH (defaults to net10): build, pack, and publish an internal prerelease package to the test NuGet feed

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
• NUGET_HOSTED: test NuGet feed URL
• NUGET_HOSTED_APIKEY: API key for the test NuGet feed

Optional GitLab CI/CD variables:

• INTERNAL_PUBLISH_BRANCH: internal publish branch name, defaults to net10
• NUGET_PROXY: alternate restore source used during CI restore

Internal branch packages are published with an automatic version suffix in the format -internal.<pipeline id> to avoid duplicate package versions on the test feed.