ReoGrid One
V4 and V5, side by side.
One license covers both.
ReoGrid One licenses are version-independent. There is no forced upgrade and no end-of-life for V4 — you choose per project, and your existing key works with V5 as-is, with no re-issue.
The license is version-independent
One key, both versions
A key issued for V4 activates V5 — and vice versa. Nothing to re-issue, nothing to exchange. One license also covers WinForms, WPF and Avalonia (V5+).
V4 is not going away
V4 stays on sale and supported. There is no end-of-sale or end-of-life planned, so staying on V4 — for one project or all of them — is a fully supported choice.
Perpetual, no kill switch
Licenses are buy-once and perpetual. The first year of updates & support is included; renewing is optional, and your installed versions keep working either way.
Installing both, without conflicts
V5 ships under a separate package family precisely so the two versions never collide: different NuGet IDs, different assemblies, different namespaces. A solution can contain V4 projects and V5 projects side by side. The recommended pattern is one version per project — for example, keep an existing V4 desktop app unchanged while new server-side code targets unvell.ReoGrid.One.Core — and exchange data between them via XLSX.
| V4 | V5 | |
|---|---|---|
| NuGet packages | unvell.ReoGrid4 / unvell.ReoGrid4.Wpf (frozen at 4.x) | unvell.ReoGrid.One / .One.Wpf / .One.Avalonia / .One.Core |
| Assemblies | unvell.ReoGrid.dll | unvell.ReoGrid.One*.dll |
| Root namespace | unvell.ReoGrid | unvell.ReoGrid.Core (+ platform namespaces) |
| .NET | .NET Framework 4.8 / .NET 8 | .NET 10 |
| License & key | One ReoGrid One license | The same license and the same key |
Data exchange: V5 does not read RGF files — save as XLSX from V4 (while V4 is installed) and read it in V5. XLSX round-trips between both versions and with Excel.
Choosing per project
Reach for V4 when…
- You need charts, cell comments, shapes, data binding, input validation or text search today
- The project cannot move to .NET 10 yet (.NET Framework 4.8 / .NET 8)
- You rely on RGF files or ReoScript
Reach for V5 when…
- Large sheets — V5 uses ~16–23 bytes per cell (measured) vs ~150–200 bytes in V4
- Cross-platform desktop with Avalonia (Windows / macOS / Linux)
- Server-side or batch processing with the headless, UI-independent core
- Direct, dependency-free PDF export (CJK font embedded)
Either way, the license is the same — so the choice is purely technical, and you can revisit it per project. The full comparison is on What's New in V5.