Fix .NET Core 3.0 build #6

Open
opened 2026-01-29 21:04:47 +00:00 by claunia · 0 comments
Owner

Originally created by @mnadareski on GitHub (Feb 19, 2020).

Originally assigned to: @mnadareski on GitHub.

At the moment, the .NET Core 3.0 build will fail anytime it runs across an MS cabinet file due to the library that it uses, libmspack4n, not supporting .NET Core 3.0. To address this, there are 2 options:

  • Update the base project to support .NET Core 3.0 by default (in-progress with the PR here: https://github.com/activescott/libmspack4n/pull/7)
  • Pull a local version of the code into the external code folder and keep it up to date with the base project, giving full attribution. This is less preferred since it's far less automated than the former.
Originally created by @mnadareski on GitHub (Feb 19, 2020). Originally assigned to: @mnadareski on GitHub. At the moment, the .NET Core 3.0 build will fail anytime it runs across an MS cabinet file due to the library that it uses, libmspack4n, not supporting .NET Core 3.0. To address this, there are 2 options: - Update the base project to support .NET Core 3.0 by default (in-progress with the PR here: https://github.com/activescott/libmspack4n/pull/7) - Pull a local version of the code into the external code folder and keep it up to date with the base project, giving full attribution. This is less preferred since it's far less automated than the former.
claunia added the enhancementbug labels 2026-01-29 21:04:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/BinaryObjectScanner#6