Ideas for Sample Applications #1029

Open
opened 2026-01-29 16:55:46 +00:00 by claunia · 3 comments
Owner

Originally created by @softworkz on GitHub (Dec 7, 2025).

If somebody would be interested in contributing app samples, here are some ideas:

  • How to inject a Preload Script
    e.g. for setting up IPC messaging between web content and .net ap
  • Build Customization via electron-builder hook scripts
    like beforePack, afterPack, artifactBuildStarted, artifactBuildCompleted
    This allows for example to manipulate or replace the *.desktop file for Linux apps
  • A comprehensive sample for electron-builder.json
    That's something you can hardly find anywhere...
  • Multi-Project Example
    How you can have a base project with Electron.NET code that is shared by multiple Electron.NET apps
  • ElectronHostHook Sample
    A sample project, showing just ElectronHostHook without any distractions
  • App Icons Sample
    A working sample with icons for all 3 platforms (Win, Linux, Mac)
  • Blazor Server
    e.g. to showcase how to best structure it and how the different parts (client-side interactivity, Electron control, native capabilities) come together

(for most of these, I can provide something based on which a sample can be created)

Note

A good sample should minimal in general. While it can be more complex in the topic that it demonstrates, everything aound that is unrelated must be as minimal as possible and should not use any other patterns - which might be elegant and useful - but they never are for the one who is interested in the topic of the sample - such things are just a distraction.

It's better to have many samples, each of which demonstrating one specific featuie or usage, than a huge all-in-one sample where a new user would have no clue where one feature ends and another one starts in the code.

Originally posted by @softworkz in #947

Originally created by @softworkz on GitHub (Dec 7, 2025). If somebody would be interested in contributing app samples, here are some ideas: - **How to inject a Preload Script** e.g. for setting up IPC messaging between web content and .net ap - **Build Customization via electron-builder hook scripts** like `beforePack`, `afterPack`, `artifactBuildStarted`, `artifactBuildCompleted` This allows for example to manipulate or replace the `*.desktop` file for Linux apps - **A comprehensive sample for electron-builder.json** That's something you can hardly find anywhere... - **Multi-Project Example** How you can have a base project with Electron.NET code that is shared by multiple Electron.NET apps - ~~**ElectronHostHook Sample**~~ ~~A sample project, showing just ElectronHostHook without any distractions~~ - **App Icons Sample** A working sample with icons for all 3 platforms (Win, Linux, Mac) - **Blazor Server** e.g. to showcase how to best structure it and how the different parts (client-side interactivity, Electron control, native capabilities) come together (for most of these, I can provide something based on which a sample can be created) > [!NOTE] > > A good sample should minimal in general. While it can be more complex in the topic that it demonstrates, everything aound that is unrelated must be as minimal as possible and should not use any other patterns - which might be elegant and useful - but they never are for the one who is interested in the topic of the sample - such things are just a distraction. > > It's better to have many samples, each of which demonstrating one specific featuie or usage, than a huge all-in-one sample where a new user would have no clue where one feature ends and another one starts in the code. _Originally posted by @softworkz in [#947](https://github.com/ElectronNET/Electron.NET/issues/947#issuecomment-3620429486)_
claunia added the help wantedgood first issueexamples labels 2026-01-29 16:55:46 +00:00
Author
Owner

@softworkz commented on GitHub (Dec 9, 2025):

Well - just one bullet is closed :-)

@softworkz commented on GitHub (Dec 9, 2025): Well - just one bullet is closed :-)
Author
Owner

@FlorianRappl commented on GitHub (Dec 9, 2025):

A more basic one, but often requested is:

  • Blazor Server
    e.g. to showcase how to best structure it and how the different parts (client-side interactivity, Electron control, native capabilities) come together
@FlorianRappl commented on GitHub (Dec 9, 2025): A more basic one, but often requested is: - **Blazor Server** e.g. to showcase how to best structure it and how the different parts (client-side interactivity, Electron control, native capabilities) come together
Author
Owner

@softworkz commented on GitHub (Dec 9, 2025):

Good idea - added to the OP

@softworkz commented on GitHub (Dec 9, 2025): Good idea - added to the OP
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#1029