Remove .NET nanoFramework support - #1676
Merged
Merged
Conversation
nanoFramework has moved to its own repo, nanoframework/nanoFramework.UnitsNet, which now publishes its own packages. Per #1647, drop the in-repo nanoFramework projects, code generation, build/CI steps and docs. - Remove UnitsNet.NanoFramework projects and generated code - Remove CodeGen NanoFrameworkGen generators and Program.cs wiring - Remove nanoFramework build/pack/version logic from Build scripts - Drop nanoFramework setup steps and -IncludeNanoFramework from GitHub Actions and Azure Pipelines - Delete redundant build-all-targets.bat (now identical to build.bat) - Clean up docs, cSpell and ReSharper dictionary references Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## master #1676 +/- ##
======================================
Coverage 96% 96% ======================================
Files 450 450 Lines 29177 29177 ======================================
Hits 28136 28136 Misses 1041 1041 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes#1647
nanoFramework support has moved to its own repository, nanoframework/nanoFramework.UnitsNet, which now publishes its own NuGet packages. This removes the in-repo nanoFramework stack.
Changes
UnitsNet.NanoFramework/directory (projects + generated code).CodeGen/Generators/NanoFrameworkGen/,NanoFrameworkGenerator.cs,NanoFrameworkVersions.cs, and theskipNanoFramework/updateNanoFrameworkDependencieswiring inProgram.cs.Build/build.ps1,build-functions.psm1,init.ps1,set-version-UnitsNet.ps1, and deletedbuild-pack-nano-nugets.psm1.init.ps1no longer downloads NuGet.exe or the VS nanoFramework extension.-IncludeNanoFrameworkflag from GitHub Actions (ci.yml,pr.yml) and Azure Pipelines.build-all-targets.bat(now identical tobuild.bat),upgrade-nanoframework.sh,Docs/nanoframework.md; cleaned upREADME.md,AGENTS.md,Docs/README.md,cSpell.json, and the ReSharper dictionary.External-port references (the ports table and dependent-projects list in README) are intentionally kept, since the package still exists in its new home.
Verification
dotnet build CodeGen→ 0 warnings, 0 errorsdotnet run --project CodeGen→ regenerates cleanly, no nanoFramework outputdotnet build UnitsNet.slnx -c Release→ 0 errors (only pre-existing obsolete-API benchmark warnings)🤖 Generated with Claude Code