• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

lduchosal / ipnetwork / 968 / 1
94%
master: 94%

Build:
DEFAULT BRANCH: master
Ran 17 May 2026 02:48PM UTC
Files 48
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

17 May 2026 02:43PM UTC coverage: 94.053% (+0.4%) from 93.637%
968.1

push

appveyor

web-flow
feat: re-enable netstandard2.0 with Windows/net48 CI gate (#412)

* feat: re-enable netstandard2.0 target on IPNetwork library

ns2.0 lets the library be consumed by .NET Framework 4.6.1+ and other
ns2.0-compatible runtimes. Source compat changes:

- Polyfills.cs: internal NotNullWhenAttribute shim under #if NETSTANDARD2_0
- UniqueLocalAddress: SHA256.HashData is .NET 5+; widen the
  ComputeHash fallback from #if NETSTANDARD2_1 to #if NETSTANDARD
- IPNetwork2WideSubnet: replace nnin[^1] with nnin[Length-1]
  (System.Index is ns2.1+)
- CidrNetworkAware: Contains(char) is .NET Core 2.1+; use IndexOf and
  add null-forgive since string.IsNullOrWhiteSpace lacks [NotNullWhen]
  annotation on ns2.0

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* ci: add Windows net48 job to gate netstandard2.0 build

Multi-target TestProject to net10.0;net48 so the net48 build links
against the library's ns2.0 output. This is the only CI path that
actually loads the ns2.0 DLL — without it, the new ns2.0 target
ships untested.

- TestProject.csproj: net10.0;net48; ConsoleApplication ref is
  net10.0-only (the CLI only targets net10.0); ArchitectureTest,
  ConsoleUnitTest, ConsoleJsonOutputTest excluded from net48
  (they test the CLI, not the library)
- IPAddressExtensionTests: SHA256.HashData fallback for non-.NET 5+
- dotnet.yml: new windows-net48 job runs TestProject.exe under net48

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* ci: use dotnet test for net48 job

EnableMSTestRunner=true doesn't emit a TestProject.exe on net48,
so the previous invocation path didn't exist. dotnet test handles
both VSTest hosting on .NET Framework and the platform bridge.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* ci: emit TestProject.exe for net48 and run directly

dotnet test no longer bridges to VSTest under Microsoft.Testing.Platform
on .NET 10 SDK. Easiest path: explicit OutputType=Exe so net48 produces
Te... (continued)

2293 of 2438 relevant lines covered (94.05%)

491933.55 hits per line

Source Files on job 968.1
  • Tree
  • List 48
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 968
  • 866f7243 on github
  • Prev Job for on master (#25993294482.1)
  • Next Job for on master (#969.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc