What exactly is it? NET wrapper on top of Electron? #42

New Issue

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

claunia commented

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

Originally created by @jitbit on GitHub (Nov 3, 2017).

The homepage lacks the most important information... What is this exactly? I though tit was a .net alternative to Electron, turns out it's it's just Electron (JS-based yeah) with a web-app running on the background?

Originally created by @jitbit on GitHub (Nov 3, 2017). The homepage lacks the most important information... What is this exactly? I though tit was a .net alternative to Electron, turns out it's it's just Electron (JS-based yeah) with a web-app running on the background?

claunia added the question label 2026-01-29 16:28:26 +00:00

claunia closed this issue

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

claunia commented

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

@robertmuehsig commented on GitHub (Nov 3, 2017):

Valid point.

I quote my intro blogpost, which may show you the basic "communication"

The basic functionality is not too complex:

We ship a “standard” (more or less blank) Electron app
Inside the Electron part two free ports are searched:
The first free port is used inside the Electron app itself
The second free port is used for the ASP.NET Core process
The app launches the .NET Core process with ASP.NET Core port (e.g. localhost:8002) and injects the > first port as parameter
Now we have a Socket.IO based linked between the launched ASP.NET Core app and the Electron app itself - this is our communication bridge!

Currently it is a Wrapper - not a port. We heard the feedback and I assume that many think Electron.NET is a port. I will open another issue how a port might look like and what the problems are. Some aspects and ideas are already mentioned in this issue.

I think we need to update the readme @GregorBiswanger

Anyway - thanks for your feedback 👍

@robertmuehsig commented on GitHub (Nov 3, 2017): Valid point. I quote my [intro blogpost](https://blog.codeinside.eu/2017/10/31/introducing-electrondotnet/), which may show you the basic "communication" > The basic functionality is not too complex: > We ship a “standard” (more or less blank) Electron app > Inside the Electron part two free ports are searched: > The first free port is used inside the Electron app itself > The second free port is used for the ASP.NET Core process > The app launches the .NET Core process with ASP.NET Core port (e.g. localhost:8002) and injects the > first port as parameter > Now we have a Socket.IO based linked between the launched ASP.NET Core app and the Electron app itself - this is our communication bridge! Currently it is a __Wrapper__ - __not a port__. We heard the feedback and I assume that many think Electron.NET is a port. I will open another issue how a port might look like and what the problems are. Some aspects and ideas are already mentioned in this [issue](https://github.com/ElectronNET/Electron.NET/issues/22). I think we need to update the readme @GregorBiswanger Anyway - thanks for your feedback 👍

claunia commented

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

@jitbit commented on GitHub (Nov 3, 2017):

Thanks! You should probable mention this on the home page to fix this issue

@jitbit commented on GitHub (Nov 3, 2017): Thanks! You should probable mention this on the home page to fix this issue

claunia commented

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

@joaocc commented on GitHub (Nov 3, 2017):

Have you guys considered using something like Bridge.Net (https://bridge.net/) to speed up the integration work?

@joaocc commented on GitHub (Nov 3, 2017): Have you guys considered using something like Bridge.Net (https://bridge.net/) to speed up the integration work?

claunia commented

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

@robertmuehsig commented on GitHub (Nov 3, 2017):

I saw this project in combination with Retyped a couple of weeks back. There are lot of possibilities. The idea was to get a familiar environment for ASP.NET Core devs, this might not be ideal, but we are looking for feedback :)

@robertmuehsig commented on GitHub (Nov 3, 2017): I saw this project in combination with [Retyped](https://retyped.com/) a couple of weeks back. There are lot of possibilities. The idea was to get a familiar environment for ASP.NET Core devs, this might not be ideal, but we are looking for feedback :)

claunia commented

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

@joaocc commented on GitHub (Nov 3, 2017):

Hi. Googled a bit more and I found these https://github.com/bridgedotnet/Widgetoko which seems closer to what I was asking about (something about it https://blog.bridge.net/widgetoko-a-node-js-and-electron-application-written-in-c-1a2be480e4f9).
Both approaches seem very interesting even though, in our case, the Widgetoko seems more interesting (we have an existing Electron/Angular/TS app).
Anyway, excellent initiative!

@joaocc commented on GitHub (Nov 3, 2017): Hi. Googled a bit more and I found these https://github.com/bridgedotnet/Widgetoko which seems closer to what I was asking about (something about it https://blog.bridge.net/widgetoko-a-node-js-and-electron-application-written-in-c-1a2be480e4f9). Both approaches seem very interesting even though, in our case, the Widgetoko seems more interesting (we have an existing Electron/Angular/TS app). Anyway, excellent initiative!

claunia commented

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

@Suchiman commented on GitHub (Nov 3, 2017):

I wonder how much effort it would be to plug into electron to create a <script type="text/csharp" /> since that would perform better than compiling C# to JS

@Suchiman commented on GitHub (Nov 3, 2017): I wonder how much effort it would be to plug into electron to create a `<script type="text/csharp" />` since that would perform better than compiling C# to JS

claunia commented

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

@robertmuehsig commented on GitHub (Nov 7, 2017):

So - I added some notes to the Readme.md and hope it is now clear what it is. Feel free to comment here if you have some more questions.

@robertmuehsig commented on GitHub (Nov 7, 2017): So - I added some notes to the Readme.md and hope it is now clear what it is. Feel free to comment here if you have some more questions.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#42