HiLang 2.5.47

.NET Standard 2.0 This package targets .NET Standard 2.0. The package is compatible with this framework or higher. 
dotnet add package HiLang --version 2.5.47
                    


                    

                
NuGet\Install-Package HiLang -Version 2.5.47
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="HiLang" Version="2.5.47" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="HiLang" Version="2.5.47" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="HiLang" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add HiLang --version 2.5.47
                    


                    

                
#r "nuget: HiLang, 2.5.47"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package HiLang@2.5.47
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=HiLang&version=2.5.47
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=HiLang&version=2.5.47
                    


                            Install as a Cake Tool

HiLang

HiLang is a minimal high-level language to describe the schema of a domain, taking inspiration from protobuf (.proto models) for hierarchical structures and SQL DML for entities, relations and views.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on HiLang:

Package Downloads
Hiperspace.SQL

Package Description

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.5.47 85 4/15/2026
2.5.43 119 4/1/2026
2.5.39 424 3/20/2026
2.5.35 131 2/27/2026
2.5.33 1,060 2/14/2026
2.5.32 2,930 1/30/2026
2.5.29 4,294 1/17/2026
2.5.28 6,007 12/31/2025
2.5.26 7,029 12/21/2025
2.5.21 9,219 12/10/2025
2.5.18 11,280 12/3/2025
2.5.8 10,768 11/15/2025
2.5.2 10,788 11/6/2025
2.5.1 10,760 10/23/2025
2.5.0 10,767 10/20/2025
2.4.6 10,782 9/23/2025
2.4.4 10,863 8/7/2025
2.4.2 10,739 7/28/2025
2.4.0 10,767 7/10/2025
2.3.8 10,750 7/1/2025
Loading failed

https://www.cepheis.com/hiperspace/20260415
# Overview
This release is a minor update to support the presentation Cube data in  Graph views with **Hiperspace.DB**, and minor updated to external references.
## Fact enhancement
Every instance of a `_Fact` or `_Cube` element now includes a `Facts` property that excludes `Node` that is a view of a fact but have no underlying value.
## Node Enhancement
`Node` now includes a `Measures` property, which is a `List<MeasureValue>` to eliminate the need to separately fetch measures when displaying `Cube` `Node` in a **Hiperspace.DB** graph display.  Normally a *graph* showing "*which client Sectors trade which products*" would involve connecting the edges *Sector->Client->Account->Trade->Leg->Asset->Instrument->Product* or `HiperEdge` *Sector=>Trade=>Product*, and then aggregate results.  When *Sector* and *Product* are *`@CubeDimension`* and *Trade* is a *`@CubeFact`* the aggregate values are available directly through *Sector->Trade_Cube->Product* with *streaming calculation* in **Hiperspace.DB**.  Displaying aggregate values in a graph is so useful for analysis that it is worth extending the `Node` model to include them as an optional property.
[image]Sites/hiperspace/cube/hipercube.png[/image]
> **NB** This diagram is from a `HiperGraph` of the Sector "All", Product hierarchy aggregates are connected to the Sector hierarchy (without spider connections)
## Hilang enhancement
* Added support for `enum` values in messages.
* Resolved issue with self-referencing messages `message Dimension { Branches : List<Dimension> };`
* Name resolution of types now uses global namespace resolution to avoid clashes.  

## SubSpace enhancement
Currently Blazer Web Assembly clients cannot (*currently*) support threads and therefore cannot perform synchronous IO - `FindAsync()` and `GetAsync()`  requests can be routed (*over **gRpc***) to a remote store, `Find()` and `Get()` request are therefore *cache-local*. the test for `OperatingSystem.IsBrowser()` has been replaced  with a `CachePolicy` that default to *`CachingPolicy.Cache`* for Browser and *`CachingPolicy.Space`* otherwise.  This allows `message` to be used to *pre-fetch* dependencies on the server-side in addition to browser.