starred/Electron.NET
1
0
Fork 0
mirror of https://github.com/ElectronNET/Electron.NET.git synced 2026-02-03 21:25:13 +00:00
Code Issues 668 Packages Projects Releases 20 Wiki Activity

It's not possible to have two apps open simultaneously #993

New Issue
Closed
opened 2026-01-29 16:54:06 +00:00 by claunia · 2 comments
claunia commented 2026-01-29 16:54:06 +00:00
Owner
Copy Link

Originally created by @FrankBoehringerKirchner on GitHub (Oct 31, 2025).

  • ElectronNET.API Version: 23.6.2
  • ElectronNET.CLI Version: 23.6.2
  • Node: v22.19.0
  • .NET Core: 8
  • Target: Windows

I know ElectronNET should find the next available port if the default one is occupied, but for me (and my colleague) the port scanner hasn’t been working reliably inside the ElectronNET host. After multiple attempts, I’ve found it succeeds roughly 30% of the time. In other cases, it fails with the following error:

Image

I haven’t been able to determine exactly why the port scanner fails intermittently, especially since it works fine when tested in a separate project. However, I managed to fix the issue locally by modifying the main.js of the ElectronNET host to retry finding an available port if listening to the created socket fails.

Before I open a PR with this retry logic, I wanted to ask if anyone else has encountered this issue. It seems odd that no one has reported it yet. 😄 Although, to be fair, I think a retry loop would be beneficial anyway because it makes this critical part of the program more stable- and it would, for example, solve issue #871 as well.

Steps to Reproduce:

  1. create an empty ElectronNET app
  2. run it and wait for the application to pop up
  3. run it again

OR

  1. create an empty ElectronNET app
  2. build app for windows
  3. run the app and wait for the application to pop up
  4. run it again

By the way, as a longtime ElectronJS fan I was excited to see there’s a way to use it in .NET, since I need to create a cross-platform C# project for work. :D

Originally created by @FrankBoehringerKirchner on GitHub (Oct 31, 2025). * **ElectronNET.API Version**: 23.6.2 * **ElectronNET.CLI Version**: 23.6.2 * **Node**: v22.19.0 * **.NET Core**: 8 * **Target**: Windows I know ElectronNET should find the next available port if the default one is occupied, but for me (and my colleague) the port scanner hasn’t been working reliably inside the ElectronNET host. After multiple attempts, I’ve found it succeeds roughly 30% of the time. In other cases, it fails with the following error: <img width="443" height="215" alt="Image" src="https://github.com/user-attachments/assets/30d8c8f8-f00f-44a3-98a0-fc5c22537543" /> I haven’t been able to determine exactly why the port scanner fails intermittently, especially since it works fine when tested in a separate project. However, I managed to fix the issue locally by modifying the `main.js` of the ElectronNET host to retry finding an available port if listening to the created socket fails. Before I open a PR with this retry logic, I wanted to ask if anyone else has encountered this issue. It seems odd that no one has reported it yet. 😄 Although, to be fair, I think a retry loop would be beneficial anyway because it makes this critical part of the program more stable- and it would, for example, solve issue #871 as well. Steps to Reproduce: 1. create an empty ElectronNET app 2. run it and wait for the application to pop up 3. run it again **OR** 1. create an empty ElectronNET app 2. build app for windows 3. run the app and wait for the application to pop up 4. run it again By the way, as a longtime ElectronJS fan I was excited to see there’s a way to use it in .NET, since I need to create a cross-platform C# project for work. :D
claunia added the bug label 2026-01-29 16:54:06 +00:00
claunia commented 2026-01-29 16:54:07 +00:00
Author
Owner
Copy Link

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

I did see it one time. Was wondering what was wrong and then it didnt appear anymore.

Now it makes sense, i guess. Normally i dont have two electronNet applications open at the same time but by misconfiguration it could be possible this was the case when it failed.

@Fibsi90 commented on GitHub (Oct 31, 2025): I did see it one time. Was wondering what was wrong and then it didnt appear anymore. Now it makes sense, i guess. Normally i dont have two electronNet applications open at the same time but by misconfiguration it could be possible this was the case when it failed.
claunia commented 2026-01-29 16:54:07 +00:00
Author
Owner
Copy Link

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

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

See Wiki / What's New.

For a recent take on this see #901.

@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). For a recent take on this see #901.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
api
applications
bug
bug
dev-experience
discussion
documentation
duplicate
enhancement
examples
Feature
Feature
good first issue
help wanted
In progress
information
infrastructure
invalid
javascript
macos
more-information-needed
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#993
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?