Allow us to pass our own JsonSerializerSettings for IPC communication #584

New Issue

claunia · 2026-01-29T16:43:28Z

claunia commented

2026-01-29 16:43:28 +00:00

Originally created by @lukasportal on GitHub (Nov 4, 2020).

This is a very easy task to accomplish, really (unless I'm missing something 😄)

Basically, here, 5e0ef7edb5/ElectronNET.API/IpcMain.cs (L182)
we have the JSON settings hardcoded and very basic.
I would like to have control on how we serialize our JSON in the IPC communication.

It would be good to expose that setting to the public and allow us to change it somewhere, maybe like Electron.IpcMain.JSONSerializerSettings or something similar

Or maybe when calling Electron.IpcMain.Send(), add an overload that accepts a JsonSerializerSettings and use that instead.

Originally created by @lukasportal on GitHub (Nov 4, 2020). This is a very easy task to accomplish, really (unless I'm missing something 😄) Basically, here, https://github.com/ElectronNET/Electron.NET/blob/5e0ef7edb5012a8713d02f657f828b3a687d95c0/ElectronNET.API/IpcMain.cs#L182 we have the JSON settings hardcoded and very basic. I would like to have control on how we serialize our JSON in the IPC communication. It would be good to expose that setting to the public and allow us to change it somewhere, maybe like `Electron.IpcMain.JSONSerializerSettings` or something similar Or maybe when calling `Electron.IpcMain.Send()`, add an overload that accepts a `JsonSerializerSettings` and use that instead.

claunia added the Feature label 2026-01-29 16:43:28 +00:00

claunia referenced this issue

2026-01-29 16:58:36 +00:00

[PR #585] [MERGED] If we provide the Version parameter and haven't included the version … #1224

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#584