Migrating from .NET Framework 4.8 to .NET 8+: GSF.Core Support?

GPA Products Grid Solutions Framework
1

Hi folks,
We are migrating a legacy ingestion component from .NET Framework 4.8 to modern .NET (targeting net8/net10) in order to run it cross-platform (Linux/Docker).

Today our code depends on GSF/openHistorian-related assemblies (e.g., namespaces like GSF.Core and openHistorian.*). When targeting net8+/net10, NuGet restores GSF.Core using .NET Framework assets (NU1701 warning), which suggests it may not be fully compatible with modern .NET / Linux.

Questions:

  1. Is there an official plan to ship GSF.Core (and the required Snap/openHistorian-related assemblies) for modern .NET targets (net8.0+ / netstandard), so it runs on Linux?
  2. If not, what is the recommended replacement path in the Gemstone ecosystem for Snap/openHistorian integrations ?
  3. If Gemstone is the intended path, is there guidance/mapping for which Gemstone packages replace the older GSF/openHistorian components we already use?

Thanks in advance!

2
  1. Already have these, see here: snapdb/SnapDB: The SNAPdb Engine is a high-performance key/value pair archiving technology.
  2. Generally, you have to migrate to .NET 9/10 and reference Gemstone/SnapDB packages instead of GSF ones.
  3. The code is basically the same, save for places where direct conversion was not possible, e.g., user authentication. Namespaces have the same basic hierarchy, but with some extra logic applied where applicable. As an example, STTP now has a branch with the same base code with two projects, one .NET Framework referencing GSF, one .NET 9.0 referencing Gemstone. Each individual project uses global using references for desired GSF/Gemstone elements and the base “shared code” is the same: snapdb/SnapDB: The SNAPdb Engine is a high-performance key/value pair archiving technology.