Update to Electron 29 (Electron 23 No Longer Supported) #940

Closed
opened 2026-01-29 16:52:22 +00:00 by claunia · 4 comments
Owner

Originally created by @scottkuhl on GitHub (Mar 17, 2024).

The version of Electron that Electron.NET is using (23) is no longer supported as of August last year. The project needs to update to the latest version of Electron.

Originally created by @scottkuhl on GitHub (Mar 17, 2024). The version of Electron that Electron.NET is using (23) is no longer supported as of August last year. The project needs to update to the latest version of Electron.
claunia added the Feature label 2026-01-29 16:52:22 +00:00
Author
Owner

@scottkuhl commented on GitHub (Mar 17, 2024):

I looked at updating this myself in the package.json files, but it's a six version jump and I'm not sure I would be able to test the code base well enough to support the community.

@scottkuhl commented on GitHub (Mar 17, 2024): I looked at updating this myself in the package.json files, but it's a six version jump and I'm not sure I would be able to test the code base well enough to support the community.
Author
Owner

@scottkuhl commented on GitHub (Mar 17, 2024):

Also, IMO there should be a policy in place in when the version of Electron in this project will be updated. For example, "We commit to updating to the new version of Electron within 4 weeks of its release."

@scottkuhl commented on GitHub (Mar 17, 2024): Also, IMO there should be a policy in place in when the version of Electron in this project will be updated. For example, "We commit to updating to the new version of Electron within 4 weeks of its release."
Author
Owner

@FlorianRappl commented on GitHub (Oct 31, 2025):

Outdated - use ElectronNET.Core and ElectronNET.Core.AspNet.

See Wiki / What's New.

@FlorianRappl commented on GitHub (Oct 31, 2025): Outdated - use `ElectronNET.Core` and `ElectronNET.Core.AspNet`. See [Wiki / What's New](https://github.com/ElectronNET/Electron.NET/wiki/What's-New).
Author
Owner

@scottkuhl commented on GitHub (Oct 31, 2025):

Version Independence

The removal of rigid Electron version coupling means developers can now choose the Electron version that best fits their needs, with build-time validation ensuring compatibility. This approach encourages community feedback and enables faster adoption of new Electron features.

@FlorianRappl This is fantastic news. Keeping up with Electron was always a security and functionality concern with using Electron.NET as it often lagged behind. This completely removes that concern now and in the future. Great job!

@scottkuhl commented on GitHub (Oct 31, 2025): > Version Independence > > The removal of rigid Electron version coupling means developers can now choose the Electron version that best fits their needs, with build-time validation ensuring compatibility. This approach encourages community feedback and enables faster adoption of new Electron features. @FlorianRappl This is fantastic news. Keeping up with Electron was always a security and functionality concern with using Electron.NET as it often lagged behind. This completely removes that concern now and in the future. Great job!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#940