Dangling Electron Processes

[AeonSake]

Whenever the main application exits unexpectedly or before the electron window is shown (e.g., by returning before building/running the WebApplication instance), a few electron processes will remain running (usually 4, 1 main process, 3 sub-processes). It would be great if all dangling electron process would be killed once the main C# process exits. It looks like the main electron process is not always listening for the exit of the C# process?

[softworkz]

That's more a flaw of the original design than a bug.

I can only recommend to try dotnet-first instead: https://github.com/ElectronNET/Electron.NET/wiki/Startup-Methods

What you are describing is the exact reason why this new mode exists: While there may be some improvements possible, the classic "electron-first" approach will never be 100% reliable and solid.

[AeonSake]

Is it possible to force the .NET-first mode without the process argument? Where can I get the electron port at runtime, or is it always hard-coded to 8001? Can this mode somehow be set as default for publishing?

[softworkz]

I believe that I made it work for ASP.Net as well, don't remember atm, but at least with console projects, You can just start either this or that.

[AeonSake]

I might not understand this properly, but that doesn't work in the packaged variant...right? So I probably need to package the application myself to make it work; or is there a way to start the ASP.NET executable instead of the electron one from the package itself?