Skip to content

Compile the NwcIO native engine independently of frozen extras - #255

Merged
mahach666 merged 3 commits into
mainfrom
codex/nwcio-native-boundaries
Nov 18, 2026
Merged

mahach666 merged 3 commits into
mainfrom
codex/nwcio-native-boundaries

Conversation

@mahach666

@mahach666 mahach666 commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

Changes

  • Put the frozen export, coordination and viewer implementations in Compatibility. Keep XML federation manifests there and binary NWF loading in the native engine.
  • Preserve the declaring .NET types, members, namespaces and assembly name in the default library, including the existing builder and assembly entry points.
  • Compile the engine without Compatibility as a separate non-packable CI check.

Verification

  • The native-only compile passed on .NET 8 and .NET 10.
  • The full solution passed 1,286 core/CLI and 98 scene tests on each target, with 12 tests requiring local fixtures skipped per target.
  • The full packages built with package compatibility validation.
  • git diff --check passed.
  • The scene adapter now builds with the compatibility diagnostic excluded in the compile check. The existing tests confirm the warning is still present in the ordinary build. A separate .NET 8/10 consumer round-tripped NWC using the native-only assembly. The normal public type/member surface matched the prior build. JSON, scene JSON, HTML and GLB matched byte for byte on a local sample.

@mahach666
mahach666 merged commit 75826bc into main Nov 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant