base on :electron: Build cross platform desktop apps with ASP.NET Core (Razor Pages, MVC, Blazor). [](https://github.com/ElectronNET/Electron.NET) [](https://donorbox.org/electron-net) [](https://gitter.im/ElectronNET/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) [](https://github.com/ElectronNET/Electron.NET/actions/workflows/ci.yml) Build cross platform desktop apps with .NET 8 and Blazor, ASP.NET Core (Razor Pages, MVC). Electron.NET is a __wrapper__ around a native Electron application with an embedded ASP.NET Core application. Via our Electron.NET IPC bridge we can invoke Electron APIs from .NET. The CLI extensions hosts our toolset to build and start Electron.NET applications. ## Wait - you host a .NET Core app inside Electron? Why? Well... there are lots of different approaches how to get a X-plat desktop app running. We thought it would be nice for .NET devs to use the ASP.NET Core environment and just embed it inside a pretty robust X-plat enviroment called Electron. Porting Electron to .NET is not a goal of this project, at least we don't have any clue how to do it. We just combine ASP.NET Core & Electron. ## 📦 NuGet [ ElectronNET.API ](https://www.nuget.org/packages/ElectronNET.API/) | [ ElectronNET.CLI](https://www.nuget.org/packages/ElectronNET.CLI/) ## 🛠 Requirements to Run The current Electron.NET CLI builds Windows/macOS/Linux binaries. Our API uses .NET 8, so our minimum base OS is the same as [.NET 8](https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md). Also you should have installed: * npm [contained in nodejs (at least Version 16.17.1)](https://nodejs.org) ## 💬 Community [](https://gitter.im/ElectronNET/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) Besides the chat on Gitter and the issues [discussed here](https://github.com/ElectronNET/Electron.NET/issues) you can also use [StackOverflow](https://stackoverflow.com/questions/tagged/electron.net) with the tag `electron.net`. If you want to sponsor the further maintenance and development of this project [see the donate section](#🙏-donate). ## 👩‍🏫 Usage To activate and communicate with the "native" (sort of native...) Electron API include the [ElectronNET.API NuGet package](https://www.nuget.org/packages/ElectronNET.API/) in your ASP.NET Core app. ```ps1 PM> Install-Package ElectronNET.API ``` ## Setup Using Minimal-API You start Electron.NET up with an `UseElectron` WebHostBuilder-Extension and open the Electron Window: ### Program.cs ```csharp using ElectronNET.API; using ElectronNET.API.Entities; var builder = WebApplication.CreateBuilder(args); builder.WebHost.UseElectron(args); // Is optional, but you can use the Electron.NET API-Classes directly with DI (relevant if you want more encoupled code) builder.Services.AddElectron(); var app = builder.Build(); ... await app.StartAsync(); // Open the Electron-Window here await Electron.WindowManager.CreateWindowAsync(); app.WaitForShutdown(); ``` ## Setup using Normal-API ### Program.cs You start Electron.NET up with an `UseElectron` WebHostBuilder-Extension. ```csharp public static IHostBuilder CreateHostBuilder(string[] args) => Host.CreateDefaultBuilder(args) .ConfigureWebHostDefaults(webBuilder => { webBuilder.UseElectron(args); webBuilder.UseStartup<Startup>(); }); ``` ### Startup.cs Open the Electron Window in the *Startup.cs* file: ```csharp public void Configure(IApplicationBuilder app, IWebHostEnvironment env) { //... Electron.WindowManager.CreateWindowAsync(); } ``` ## 🚀 Starting the Application To start the application make sure you have installed the "[ElectronNET.CLI](https://www.nuget.org/packages/ElectronNET.CLI/)" packages as global tool: ```sh dotnet tool install ElectronNET.CLI -g ``` At the first time, you need an Electron.NET project initialization. Type the following command in your ASP.NET Core folder: ```sh electronize init ``` * Now a electronnet.manifest.json should appear in your ASP.NET Core project * Now run the following: ```sh electronize start ``` ### Note > Only the first `electronize start` is slow. The next will go on faster. ## 🔭 Develop Electron.NET apps using a file watcher The file watcher is included with version 8.31.1 of Electron.NET. For example, a file change can trigger compilation, test execution, or deployment. The Electron.NET window will automatically refresh and new code changes will be visible more quickly. The following Electron.NET CLI command is required: ```sh electronize start /watch ``` ### Note > Only the first `electronize start` is slow. The next will go on faster. ## 🐞 Debugging the Application Start your Electron.NET application with the Electron.NET CLI command. In Visual Studio attach to your running application instance. Go in the __Debug__ Menu and click on __Attach to Process...__. Sort by your projectname on the right and select it on the list. ## 📔 Usage of the Electron API A complete documentation will follow. Until then take a look in the source code of the sample application: [Electron.NET API Demos](https://github.com/ElectronNET/electron.net-api-demos) In this YouTube video, we show you how you can create a new project, use the Electron.NET API, debug a application and build an executable desktop app for Windows: [Electron.NET - Getting Started](https://www.youtube.com/watch?v=nuM6AojRFHk) ## ⛏ Building Release Artifacts Here you need the Electron.NET CLI as well. Type the following command in your ASP.NET Core folder: ```sh electronize build /target win ``` There are additional platforms available: ```sh electronize build /target win electronize build /target osx electronize build /target linux ``` Those three "default" targets will produce x64 packages for those platforms. For certain NuGet packages or certain scenarios you may want to build a pure x86 application. To support those things you can define the desired [.NET Core runtime](https://docs.microsoft.com/en-us/dotnet/core/rid-catalog), the [electron platform](https://github.com/electron-userland/electron-packager/blob/master/docs/api.md#platform) and [electron architecture](https://github.com/electron-userland/electron-packager/blob/master/docs/api.md#arch) like this: ```sh electronize build /target custom "win7-x86;win32" /electron-arch ia32 ``` The end result should be an electron app under your __/bin/desktop__ folder. ### Note > macOS builds can't be created on Windows machines because they require symlinks that aren't supported on Windows (per [this Electron issue](https://github.com/electron-userland/electron-packager/issues/71)). macOS builds can be produced on either Linux or macOS machines. ## 🔄 Update After an update to the latest Electron.API package, an update to the latest Electron.CLI is always required. In addition, always update the CLI via NuGet: ```sh dotnet tool update ElectronNET.CLI -g ``` ## 👨‍💻 Authors * **[Gregor Biswanger](https://github.com/GregorBiswanger)** - (Microsoft MVP, Intel Black Belt and Intel Software Innovator) is a freelance lecturer, consultant, trainer, author and speaker. He is a consultant for large and medium-sized companies, organizations and agencies for software architecture, web- and cross-platform development. You can find Gregor often on the road attending or speaking at international conferences. - [Cross-Platform-Blog](http://www.cross-platform-blog.com) - Twitter [@BFreakout](https://www.twitter.com/BFreakout) * **[Dr. Florian Rappl](https://github.com/FlorianRappl)** - Software Developer - from Munich, Germany. Microsoft MVP & Web Geek. - [The Art of Micro Frontends](https://microfrontends.art) - [Homepage](https://florian-rappl.de) - Twitter [@florianrappl](https://twitter.com/florianrappl) * **[Robert Muehsig](https://github.com/robertmuehsig)** - Software Developer - from Dresden, Germany, now living & working in Switzerland. Microsoft MVP & Web Geek. - [codeinside Blog](https://blog.codeinside.eu) - Twitter [@robert0muehsig](https://twitter.com/robert0muehsig) See also the list of [contributors](https://github.com/ElectronNET/Electron.NET/graphs/contributors) who participated in this project. ## 🙋‍♀️🙋‍♂ Contributing Feel free to submit a pull request if you find any bugs (to see a list of active issues, visit the [Issues section](https://github.com/ElectronNET/Electron.NET/issues). Please make sure all commits are properly documented. ## 🧪 Working with this Repo This video provides an introduction to development for Electron.NET: [Electron.NET - Contributing Getting Started](https://youtu.be/Po-saU_Z6Ws) This repository consists of the main parts (API & CLI) and it's own "playground" ASP.NET Core application. Both main parts produce local NuGet packages, that are versioned with 99.0.0. The first thing you will need is to run one of the build scripts (.cmd or .ps1 for Windows, the .sh for macOS/Linux). If you look for pure __[demo projects](https://github.com/ElectronNET)__ checkout the other repositories. The problem working with this repository is, that NuGet has a pretty aggressive cache, see [here for further information](https://github.com/ElectronNET/Electron.NET/wiki). ## 🙏 Donate We do this open source work in our free time. If you'd like us to invest more time on it, please [donate](https://donorbox.org/electron-net). Donation can be used to increase some issue priority. Thank you! [](https://donorbox.org/electron-net) Alternatively, consider using a GitHub sponsorship for the core maintainers: - [Gregor Biswanger](https://github.com/sponsors/GregorBiswanger) - [Florian Rappl](https://github.com/sponsors/FlorianRappl) Any support appreciated! 🍻 ## 🎉 License MIT-licensed. See [LICENSE](./LICENSE) for details. **Enjoy!** ## 📝 Important notes ### ElectronNET.API & ElectronNET.CLI Version 9.31.2 Make sure you also have the new Electron.NET API & CLI 9.31.2 version. ```sh dotnet tool update ElectronNET.CLI -g ``` This now uses [electron-builder](https://www.electron.build/configuration/configuration) and the necessary configuration to build is made in the **electron.manifest.json** file (on the build part). In addition, own Electron.NET configurations are stored (on the root). Please make sure that your **electron.manifest.json** file has the following new structure: ```json { "executable": "{{executable}}", "splashscreen": { "imageFile": "" }, "name": "{{executable}}", "author": "", "singleInstance": false, "build": { "appId": "com.{{executable}}.app", "productName": "{{executable}}", "copyright": "Copyright © 2020", "buildVersion": "1.0.0", "compression": "maximum", "directories": { "output": "../../../bin/Desktop" }, "extraResources": [ { "from": "./bin", "to": "bin", "filter": ["**/*"] } ], "files": [ { "from": "./ElectronHostHook/node_modules", "to": "ElectronHostHook/node_modules", "filter": ["**/*"] }, "**/*" ] } } ``` ### ElectronNET.CLI Version 0.0.9 In the Version 0.0.9 the CLI was not a global tool and needed to be registered like this in the *.csproj*: ```xml <ItemGroup> <DotNetCliToolReference Include="ElectronNET.CLI" Version="0.0.9" /> </ItemGroup> ``` After you edited the *.csproj* file, you need to restore your NuGet packages within your Project. Run the following command in your ASP.NET Core folder: ```sh dotnet restore ``` If you still use this version you will need to invoke it like this: ```sh electronize ... ``` ### Node.js Integration Electron.NET requires Node.js integration to be enabled for IPC to function. If you are not using the IPC functionality you can disable Node.js integration like so: ```csharp WebPreferences wp = new WebPreferences(); wp.NodeIntegration = false; BrowserWindowOptions browserWindowOptions = new BrowserWindowOptions { WebPreferences = wp }; ``` ### Dependency Injection ElectronNET.API can be added to your DI container within the `Startup` class. All of the modules available in Electron will be added as Singletons. ```csharp using ElectronNET.API; public void ConfigureServices(IServiceCollection services) { services.AddElectron(); } ``` ", Assign "at most 3 tags" to the expected json: {"id":"11633","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"