Skip to content

fix: target netstandard2.0 instead of net10.0 - #9

Merged
dbrattli merged 4 commits into
mainfrom
target-netstandard2.0
Mar 13, 2026
Merged

dbrattli merged 4 commits into
mainfrom
target-netstandard2.0

Conversation

@dbrattli

Copy link
Copy Markdown
Collaborator

Summary

  • Change target framework from net10.0 to netstandard2.0 in both Fable.Beam.fsproj and Fable.Beam.Cowboy.fsproj
  • Fable plugins need to target netstandard2.0 for compatibility

Test plan

  • Verify packages build correctly with netstandard2.0
  • Verify Fable can load the plugin

🤖 Generated with Claude Code

dbrattli and others added 4 commits March 13, 2026 19:18
Fable plugins need to target netstandard2.0 for compatibility.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The paket.dependencies also had framework: net10.0, which prevented
Fable.Core from being resolved for netstandard2.0 builds.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The test project is compiled via Fable, not dotnet run, so it also
needs to target netstandard2.0 for Fable.Core resolution.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The test project is an application that can consume netstandard2.0
libraries. Only the paket Test group framework needed updating.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@dbrattli
dbrattli merged commit 0506adb into main Mar 13, 2026
2 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