v4.7.2.119

BREAKING: explicit engine reference required

Starting with 4.7.2.119, the precision-neutral integration packages 2dog.xunit, 2dog.nunit, 2dog.avalonia, 2dog.blazor and 2dog.repl no longer bring in 2dog.engine transitively.

New Projects (no action needed)

Hosts created with dnx 2dog new or dnx 2dog add already include an explicit engine reference.

Existing Projects

Existing hosts that relied on that dependency can lose engine APIs and fixtures such as HeadlessFixture when restoring or updating. Floating package versions can pick up this breaking change automatically.

For older hosts, add the reference before running dnx 2dog update / dnx 2dog doctor; the published 4.7.2.119 commands do not insert a missing engine reference automatically.

Migration: add an explicit engine reference to each affected host project, using the same 2dog version as its integration packages:

<ItemGroup>
    <PackageReference Include="2dog.engine" Version="4.7.2.119" />
</ItemGroup>

For double precision, reference 2dog.engine.double instead and use matching double-precision bindings/native packages throughout the game and host. The integration package names stay unchanged. See double-precision configuration.

---

What's Changed

feat: double precision packages on nuget
feat: double precision showcase (doesn't show anything visible other than a few logs, and just runs on double precision :3)

To use them, see: http://2dog.dev/build-configurations.html#double-precision
(will add it to the 2dog tool soon, but the config edit should be quite easy enough)

** Double precision by @thygrrr in #74**
Full Changelog: v4.7.2.118...v4.7.2.119