Why not use GitHub's native Electron? Just remember what Microsoft did to Java with JNI. Assimilate. Resistance is futile.
Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
11–20 of 138 posts
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#12I was really excited when I saw this because I thought someone had finally brought us a .net alternative to electron, using xaml. Unfortunately this seems to be electron but with a .net webapp running in the background? You still need node and webkit for the UI it seems. If that's what this is, it was already possible to do with edge.js and electron so I'm not sure what advantage there is here.
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#13Why not use GitHub's native Electron? Just remember what Microsoft did to Java with JNI. Assimilate. Resistance is futile.
Well the point of this project is to allow someone to use .net in the background, although this is already possible with the edge.js project (nothing to do with the edge browser)
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#14Can someone explain what is this? Why someone might need this??
I don't think there is currently any easy way to build a GUI app using .NET Core. This might come in handy for such projects.
I can't find any GUI info here, I'm assuming that you still need to use html/CSS on top of webkit on top of node.js which then runs .net core in another process
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#15Why not use GitHub's native Electron? Just remember what Microsoft did to Java with JNI. Assimilate. Resistance is futile.
This project doesn't appear to have anything to do with Microsoft other than the fact that it uses .NET.
Your comment is not only uncalled for, it's also very off-topic.
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#16Is this a framework built on top of electron? Is there an ASP.NET server running in addition to the electron processes? It's just serving pages to the electron renderer processes, and there's an api bridge over socket IO to invoke electron methods from .NET-land? ...mindblown...
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#17Is this a framework built on top of electron? Is there an ASP.NET server running in addition to the electron processes? It's just serving pages to the electron renderer processes, and there's an api bridge over socket IO to invoke electron methods from .NET-land? ...mindblown...
cool, but unfortunately not what I was expecting
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#18This is amazing and frustrating at the same time. The biggest problems, both of which are I think unavoidable, are the necessity to be aware of serialization and the version lock.
keeping up with electron api changes is going to be a nightmare
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#19Earlier quoted context omitted.
I don't think there is currently any easy way to build a GUI app using .NET Core. This might come in handy for such projects.
I can't find any GUI info here, I'm assuming that you still need to use html/CSS on top of webkit on top of node.js which then runs .net core in another process
It just enables you to serve pages from an ASP.NET server running locally. In the client code, you get access to nodejs apis, in the server code, you can call electron apis using the api bridge
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#20I think this highlights the need for Microsoft to open source Edge’s new rendering engine. I’d love to be able to use the renderer in .NET Core for a whole host of applications (including rendering dynamic HTML to OpenGL) but unfortunately EdgeHTML has remained closed source! With many components of the .NET stack being open sourced, and even some of the Edge stack, I had high hopes for seeing the rendering engine open sourced as well too - but no such luck.
Can anyone on the Edge team comment on this? There would be so many major use cases for this in .NET. Currently we have to use CEF but I really don’t like being forced to delegate work to Chrome - it further secures Chrome’s place as “the only browser”. Not to mention the Edge team would likely receive many benefits from open sourcing the project in the way of pull requests, even if this is a little more managerial overhead.
This has been requested on MS’ UserVoice site. Would love to see it get some love. https://wpdev.uservoice.com/forums/257854-microsoft-edge-dev...
Also, what I'd love to see would be some sort of UI subsystem that all vendors target. Something built on a protocol that can be implemented in any language, and communicated to by any other language. That way all browsers' HTML renderers would target the same UI subsystem, and any UI framework could choose to either target HTML or the UI subsystem itself, as well. That UI framework (if it targets the UI subsystem) could then be run in a different context (say a JS engine running in .NET) and its output could be routed to a .NET implementation of the UI subsystem. This would allow any components built in any language to interface and work together using a common protocol, and as long as you can host the language a given UI framework is built in, you can use it to create UI elements in whatever platform you want. I see this as being THE solution to JS/web/UI stuff - there's tons of amazing developments happening there, but we can't use them in the desktop world. I'd like to see that change, and in a way that doesn't require running an entire browser inside a desktop app.