v0.1.1
Multi-RID (RID-specific) .NET tools now run instead of failing on the wrapper package.
Multi-RID tool packages
.NET 10 can pack a tool as a thin wrapper plus per-RID nupkgs (RuntimeIdentifierPackages in DotnetToolSettings.xml). v0.1.0 stopped on those wrappers with declares RID-specific packages, which are not resolved by this runner.
ndnx now hops the same way the SDK does:
- Pick the best declared RID for this machine (exact host RID, then the portable RID graph — e.g.
ubuntu.24.04-x64→linux-x64— thenany) - Download that mapped package at the same version
- Run the RID package’s
EntryPoint+Runner
That unblocks Native AOT tools such as stop and winget, and the same layout used by go, runfile, and gist. Classic tools/{tfm}/{rid} packages are unchanged.
Executable payloads extracted from nupkgs also get Unix execute bits, so RID binaries actually run after extract on macOS and Linux.
Packaging
Windows release zips are submitted to WinGet (Devlooped.ndnx) after a published GitHub release.
Sponsors
The following sponsors made this release possible: @clarius, @MFB-Technologies-Inc, @sandrock, @drivenet, @Keflon, @tbolon, @kfrancis, @rbnswartz, @jfoshee, @Mrxx99, @eajhnsn1, @Jonathan-Hickey, @KenBonny, @SimonCropp, @agileworks-eu, @arsdragonfly, @vezel-dev, @ChilliCream, @4OTC, @DominicSchell, @adalon, @torutek, @mccaffers, @SeikaLogiciel, @wizardness, @eska-gmbh, @geodata-no.
Thanks 💜
