Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

IPC appears to be broken on Windows

See original GitHub issue

Hi,

I’m working on a proof of concept (Windows not Linux/Mac) prior to us using Electon.NET in an upcoming project and I’m having an issue with the IPC between the main and renderer processes. I can get the IPC working but only very briefly, after a little time messages like this will begin scrolling up the console:

ASP.NET Core Application connected... global.electronsocket cQS8pxM3WoqXUD2IAAAB 2019-01-14T16:17:47.132Z
stdout: BridgeConnector connected!

These messages are generated about every 30s until the program is closed. Once the first of these messages has appeared, IPC between the main and rendered processes stops.

Please note that I raised a very similar issue (number 12) on the electron.net-api-demos project. This issue was closed because the demos code was not created with the latest version of the Electron.NET API but I don’t think that explanation applies to this issue.

Here’s a minimal set of instructions that should let you reproduce the issue starting with a clean Win 2012 R2 VM:

Install dotnet-sdk-2.2.102 (issue also shows up with sdk 2.1) Install Node 10.15.0 LTS Create a new app with dotnet new mvc Install ElectronNET.API 0.0.11 Install ElectronNET.CLI 0.0.11 Add some basic IPC between main and rendered processes, I copied the code Gregor added in his Getting Started video on YouTube

Start the app and try out the IPC, note that it works. Leave the app for a while until one of the BridgeConnector messages appears, re-try the IPC and note that it no longer works.

Note that you may have to edit the Views\Shared_Layout.cshtml file to remove the integrity=“…” attributes from the <Link> tags as Electron doesn’t handle those well.

Please let me know if you have any suggestions as to what might be going on or if you need any more info to help diagnose the issue.

Thanks,

Richard