ElectronSharp.API 33.2.0.53881

dotnet add package ElectronSharp.API --version 33.2.0.53881                
NuGet\Install-Package ElectronSharp.API -Version 33.2.0.53881                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="ElectronSharp.API" Version="33.2.0.53881" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add ElectronSharp.API --version 33.2.0.53881                
#r "nuget: ElectronSharp.API, 33.2.0.53881"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install ElectronSharp.API as a Cake Addin
#addin nuget:?package=ElectronSharp.API&version=33.2.0.53881

// Install ElectronSharp.API as a Cake Tool
#tool nuget:?package=ElectronSharp.API&version=33.2.0.53881                

<img src="https://github.com/theolivenbaum/electron-sharp/blob/main/assets/electron-sharp-logo.svg" width="100" height="100"/>

ElectronSharp

Build cross platform desktop apps with .NET 9 and ASP.NET Core (Razor Pages, MVC), Blazor or h5.

ElectronSharp is a wrapper around a "normal" Electron application with an embedded ASP.NET Core application. It uses a socket-based IPC bridge we can invoke Electron APIs from .NET.

The CLI extensions hosts the toolset to build and start ElectronSharp-based applications.

ElectronSharp is a hard fork from the original Electron.NET project, mantained by me and used to build the Curiosity app.

📦 NuGet:

  • API NuGet
  • CLI NuGet

🛠 Requirements to run:

The current ElectronSharp CLI builds Windows/macOS/Linux binaries. The API uses .NET 9, so our minimum base OS is the same as .NET 9.

Also you should have installed:

👩‍🏫 Usage

To activate and communicate with the Electron API, include the ElectronSharp.API NuGet package in your ASP.NET Core app. Check out the Electron.SampleApp for an example of how to use ElectronSharp.

PM> Install-Package ElectronSharp.API

Program.cs

You start ElectronSharp up with an UseElectron WebHostBuilder-Extension.

public static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureWebHostDefaults(webBuilder =>
        {
            Electron.ReadAuth();
            webBuilder.UseElectron(args);
            webBuilder.UseStartup<Startup>();
        });

Startup.cs

Open the Electron Window in the Startup.cs file:

public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    ...

    // Open the Electron-Window here
    Task.Run(async () => await Electron.WindowManager.CreateWindowAsync());
}

Setup Using Minimal-API

Electron.ReadAuth();

var builder = WebApplication.CreateBuilder(args);
builder.WebHost.UseElectron(args);
...
var browserWindow = await Electron.WindowManager.CreateWindowAsync(new BrowserWindowOptions
{
    Width = 1152,
    Height = 940,
});
await app.RunAsync();

🚀 Start the Application

To start the application make sure you have installed the "ElectronSharp.CLI" packages as global tool:

dotnet tool install ElectronSharp.CLI -g

At the first time, you need an ElectronSharp project initialization. Type the following command in your app folder:

electron-sharp init
  • Now a electronnet.manifest.json should appear in your ASP.NET Core project
  • Now run the following:
electron-sharp start

Hint

If invoking any of those commands gives you strange errors (like .NET 5 not installed), it means you've typed electronize instead of electron-sharp.

Note

Only the first run is usually slow due to dependency downloads. The next will go on faster.

🔭 Develop ElectronSharp apps using a file watcher

You can use a file watcher mode to monitor your project folder for changes, and automatically restart the project:

electron-sharp start /watch

🐞 Debug

Start your ElectronSharp application with the ElectronSharp 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:
ElectronSharp Sample App

⛏ Build

Here you need the ElectronSharp CLI as well. Type the following command in your ASP.NET Core folder:

electronize build /target win

There are additional platforms available:

electron-sharp build /target win
electron-sharp build /target osx
electron-sharp build /target osx-arm64
electron-sharp build /target linux

Those four "default" targets will produce packages for those platforms. Note that the osx-arm64 is for Apple Silicon Macs.

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 runtime, the electron platform and electron architecture like this:

electron-sharp 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). macOS builds can be produced on either Linux or macOS machines.

Develop

Install dotnet tool locally

  • Build the CLI tool using dotnet build, this should create a nuget package in the artifact directory
  • Execute in the main electronnet solution folder
dotnet tool update --add-source ./artifacts/ -g electronsharp.cli -v d	

👨‍💻 Original (Electron.NET) Authors

  • Gregor Biswanger - (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 - Twitter @BFreakout
  • Robert Muehsig - Software Developer - from Dresden, Germany, now living & working in Switzerland. Microsoft MVP & Web Geek. - codeinside Blog - Twitter @robert0muehsig

See also the list of contributors who participated in the original 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. Please make sure all commits are properly documented.

🎉 License

MIT-licensed

Product Compatible and additional computed target framework versions.
.NET net9.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
33.2.0.53881 168 11/21/2024
33.2.0.53880 67 11/21/2024
32.0.1.51369 1,247 8/23/2024
31.3.1.50855 168 7/29/2024
31.3.0.50755 165 7/28/2024
31.3.0.50594 157 7/25/2024
31.2.1.50335 258 7/16/2024
31.2.0.50292 136 7/15/2024
31.1.0.50269 96 7/13/2024
31.1.0.49989 237 6/27/2024
30.0.6.49104 513 5/22/2024
30.0.6.49034 94 5/19/2024
30.0.6.48961 227 5/16/2024
30.0.4.48738 162 5/14/2024
30.0.2.48552 173 5/9/2024
30.0.2.48434 159 5/7/2024
30.0.2.48296 119 5/2/2024
30.0.1.47933 253 4/19/2024
30.0.0.47870 114 4/17/2024
29.3.0.47750 212 4/12/2024
29.1.5.47165 320 3/22/2024
29.1.5.47134 183 3/21/2024
29.1.4.46985 235 3/14/2024
29.0.1.46142 865 2/22/2024
28.2.0.44969 1,460 1/27/2024
28.1.3.44599 248 1/11/2024
28.0.0.44380 348 12/14/2023
27.1.0.43670 1,215 11/17/2023
27.1.0.43644 132 11/16/2023
27.1.0.43604 201 11/16/2023
27.0.4.43553 178 11/13/2023
27.0.4.43552 128 11/13/2023
27.0.4.43498 245 11/9/2023
27.0.2.43249 179 10/24/2023
27.0.1.43128 474 10/19/2023
27.0.0.43002 244 10/13/2023
26.3.0.42624 387 10/5/2023
26.3.0.42623 147 10/5/2023
26.2.4.42548 212 10/2/2023
26.2.2.42382 251 9/20/2023
26.2.1.42149 232 9/16/2023
26.2.1.42101 196 9/15/2023
26.2.0.41770 240 9/7/2023
26.1.0.41750 138 9/6/2023
26.1.0.41739 250 9/6/2023
26.1.0.41637 182 9/5/2023
26.1.0.41603 135 9/4/2023
26.1.0.41265 311 8/28/2023
26.1.0.41264 171 8/28/2023
26.1.0.41263 158 8/28/2023
26.1.0.41243 178 8/28/2023
26.1.0.41010 259 8/24/2023
26.0.0.40902 233 8/22/2023
25.3.1.40533 410 8/8/2023
25.3.1.40262 249 7/20/2023
25.3.0.40090 180 7/16/2023
25.2.0.39535 582 6/27/2023
25.2.0.39487 172 6/26/2023
25.0.1.39151 335 6/2/2023
25.0.0.39150 211 6/2/2023
25.0.0.38955 243 5/30/2023
24.4.0.38875 221 5/25/2023
24.4.0.38874 196 5/25/2023
24.0.0.37423 804 4/11/2023
23.1.3.36686 789 3/15/2023
23.1.3.36685 258 3/15/2023
23.1.3.36684 264 3/15/2023
23.1.3.36622 272 3/9/2023
23.0.0.36276 461 2/15/2023
23.0.0.36236 335 2/14/2023
23.0.0.36228 304 2/13/2023
23.0.0.36192 322 2/13/2023
23.0.0.35946 384 2/7/2023
22.2.0.35891 371 2/5/2023
22.2.0.35887 327 2/4/2023
22.1.0.35531 462 1/27/2023
22.0.2.35227 731 1/15/2023
22.0.0.35063 370 1/5/2023
22.0.0.35062 354 1/5/2023
22.0.0.35061 374 1/5/2023
22.0.0.35059 355 1/5/2023
22.0.0.35057 385 1/5/2023