The Move to .NET 10 Is Complete

For everyone.

Capsuleers,

Underneath every skill queue, wallet chart, and doctrine comparison in EveLens, there is a runtime and a UI framework. As of the 1.5.0 line, both are current: EveLens now runs on .NET 10 and Avalonia 12.

The definition of success for this migration was simple: nothing looks different, nothing breaks, and you never think about it. It shipped in 1.5.0-beta.1 on August 19th, and the bug tracker stayed quiet — exactly the report card we wanted.

01

A Codebase Older Than Some of Your Characters

EveLens inherits its skill math from EVEMon, first released in August 2006 and built on the .NET Framework and WinForms — technology from an era when EVE still had learning skills. By 2021, the original project had gone quiet on .NET Framework 4.6.1, a runtime whose own end-of-support clock is audibly ticking.

The 2026 rebuild that became EveLens made the first jump: .NET 8 and Avalonia, which is what took a Windows-only tool to Windows, macOS, and Linux in one move. That was two runtime generations ago. Staying still is how the original project aged out; we don't intend to repeat the experiment.

02

Why .NET 10, Why Now

Three reasons, in honest order.

Performance you'll eventually feel. Each .NET generation ships real runtime and garbage-collector improvements. EveLens juggles live ESI data for rosters of 30, 70, even 100+ characters — exactly the kind of workload where runtime efficiency stops being a benchmark number and starts being how smooth the overview feels.

Avalonia 12's rendering. The UI framework's new generation brings better text rendering and compositor improvements. If the interface feels slightly crisper, that's not your imagination — but most of what Avalonia 12 buys us is headroom for what's coming.

The ecosystem clock. Libraries, security patches, and tooling all follow the current runtime. Every release we stayed behind was a release where a dependency fix or a profiler improvement was out of reach. Better tools mean we find and fix your bug reports faster.

There's also a fourth reason we didn't fully appreciate until after: the work now landing on macOS — a properly signed, notarized app — leaned on being current. More on that in its own post.

03

Careful… Careful…

A character tool's first duty is to the data. Every skill plan, every settings file, every cached character written under .NET 8 had to read back under .NET 10 exactly as it was.

That's what the test suite is for. EveLens ships with 2,448 automated tests, including round-trip tests for every serialized format and an accuracy suite whose answers are checked against known in-game values. The migration wasn't declared done when it compiled; it was done when all of them passed, on all three platforms, and then when beta users ran it against their real rosters and found nothing to report.

04

What This Means for You

In the short term: nothing, and that is by design. Your settings, plans, and characters carried over untouched.

In the long term, this is groundwork: a faster runtime under your biggest rosters, a UI framework with headroom for what we're building next, security patches that keep arriving, and a codebase that stays pleasant to contribute to — which, for an open-source project, is how features reach you faster.

05

Thank You for Noticing Nothing

The beta channel carried this migration through seventeen releases without ceremony, and the pilots running 30-plus characters on it are the reason 1.5.0 ships as proven rather than merely shipped. If anything ever feels off, the issue tracker is where to tell us.

Fly safe. o7

EVE Online and all related logos and images are trademarks or registered trademarks of CCP hf.