Skip to content

Fix: add binding projects to the solution so examples resolve in IDEs#54

Merged
MDA2AV merged 1 commit into
mainfrom
fix/sln-binding-projects
Jun 17, 2026
Merged

Fix: add binding projects to the solution so examples resolve in IDEs#54
MDA2AV merged 1 commit into
mainfrom
fix/sln-binding-projects

Conversation

@MDA2AV

@MDA2AV MDA2AV commented Jun 17, 2026

Copy link
Copy Markdown
Member

Problem: Glyph11.Pico (and Glyph11.Native) couldn't be resolved when the Glyph11.Pico.Example / Glyph11.Native.Example projects were open — the examples ProjectReference the binding projects, but those weren't members of src/Glyph11.sln, so IDEs flagged the references as unresolved (CLI builds worked because MSBuild follows the path regardless).

Fix:

  • Added Glyph11.Native and Glyph11.Pico to src/Glyph11.sln, so everything the examples reference is in the solution.
  • They were originally left out so the managed Release job (which packed the whole src solution) wouldn't ship them without their native binaries. To keep that safe, the Release job now packs Glyph11/Glyph11.csproj specifically — the bindings publish via package-native.yml / package-pico.yml with their natives bundled.
  • Gitignore the local benchmarking NuGet feed.

Verified: the full solution builds (0 errors, examples resolve), and dotnet pack Glyph11/Glyph11.csproj produces only Glyph11.0.3.5.nupkg.

The examples ProjectReference Glyph11.Native / Glyph11.Pico, but those projects
weren't in src/Glyph11.sln — so IDEs couldn't resolve them (CLI builds were fine).
Add both to the solution. To keep release.yml from shipping them (the solution
pack would have packed the bindings without their native binaries), point the
managed Release job at Glyph11/Glyph11.csproj specifically — the bindings publish
via package-native.yml / package-pico.yml. Also gitignore the local benchmarking
feed.

Verified: solution builds; packing Glyph11.csproj produces only Glyph11.
@MDA2AV MDA2AV merged commit ac166ba into main Jun 17, 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