electronize build /target Mac/Linux/Win does not create custom packaged executable #731

Closed
opened 2026-01-29 16:47:11 +00:00 by claunia · 11 comments
Owner

Originally created by @SESA11057 on GitHub (Dec 9, 2021).

When I build my Electron.NET app with "electronize build /target Mac" and run on a Mac system, the menu at the top of the screen shows "Electron" as the title of the application. However, I'd think this is a "bug" of sorts, because most people will want the name of their own application to show up there. Shouldn't it be the default to build the application such that the product name listed in electron.manifest.json is used as the application name?

Originally created by @SESA11057 on GitHub (Dec 9, 2021). When I build my Electron.NET app with "electronize build /target Mac" and run on a Mac system, the menu at the top of the screen shows "Electron" as the title of the application. However, I'd think this is a "bug" of sorts, because most people will want the name of their own application to show up there. Shouldn't it be the default to build the application such that the product name listed in electron.manifest.json is used as the application name?
claunia added the question label 2026-01-29 16:47:11 +00:00
Author
Owner

@danatcofo commented on GitHub (Dec 9, 2021):

electronize build /target osx is the proper command

@danatcofo commented on GitHub (Dec 9, 2021): `electronize build /target osx` is the proper command
Author
Owner

@bman46 commented on GitHub (Dec 9, 2021):

the menu at the top of the screen shows "Electron" as the title of the application

The application built using the build command will have a custom name and other settings. See @danatcofo comment for that command. When running using the electronize start command, the executable will use a precompiled version of electron that has a default configuration of the name, logo, and toolbar.

@bman46 commented on GitHub (Dec 9, 2021): > the menu at the top of the screen shows "Electron" as the title of the application The application built using the `build` command will have a custom name and other settings. See @danatcofo comment for that command. When running using the `electronize start` command, the executable will use a _precompiled_ version of electron that has a default configuration of the name, logo, and toolbar.
Author
Owner

@SESA11057 commented on GitHub (Dec 9, 2021):

I tried both osx and mac as the target for the build command, and "Electron" still showed up as the menu name on a Mac, as seen here:

image

@SESA11057 commented on GitHub (Dec 9, 2021): I tried both osx and mac as the target for the build command, and "Electron" still showed up as the menu name on a Mac, as seen here: ![image](https://user-images.githubusercontent.com/93392942/145473246-5a3005cf-26af-4094-8fa9-7c034a8106f4.png)
Author
Owner

@bman46 commented on GitHub (Dec 9, 2021):

Did you set the productName under electron.manifest.json?
It is under the build section:

  "build": {
   ...
    "productName": "Your Name Here",
   ...
@bman46 commented on GitHub (Dec 9, 2021): Did you set the productName under `electron.manifest.json`? It is under the build section: ``` "build": { ... "productName": "Your Name Here", ... ```
Author
Owner

@danatcofo commented on GitHub (Dec 9, 2021):

ok....

{
  "name" : "myname",
  "executable": "myname",
  "build": {
    "productName": "myname",
    ...
  }

I have these fields filled in and my app name shows up just fine.... They are defined by electron-builder I believe

@danatcofo commented on GitHub (Dec 9, 2021): ok.... ``` { "name" : "myname", "executable": "myname", "build": { "productName": "myname", ... } ``` I have these fields filled in and my app name shows up just fine.... They are defined by electron-builder I believe
Author
Owner

@SESA11057 commented on GitHub (Dec 9, 2021):

image

Here's what I have in my electron.manifest.json file.

@SESA11057 commented on GitHub (Dec 9, 2021): ![image](https://user-images.githubusercontent.com/93392942/145474585-afdbc0ed-1854-41e9-8b86-f94acbdb4349.png) Here's what I have in my electron.manifest.json file.
Author
Owner

@SESA11057 commented on GitHub (Dec 9, 2021):

In reading over your posts, I think the disconnect I'm having is that even after compiling as /target osx, I'm still starting the app on the Mac using electronize start.

Per your posts above, that means I'm running with the precompiled Electron host at that point, rather than the custom packaged host created under the hood by electron-builder.

I'll retry it this evening, and avoid running using electronize start, and since it's working for you, I'll assume it will for me as well.

Thanks for the assistance.

@SESA11057 commented on GitHub (Dec 9, 2021): In reading over your posts, I think the disconnect I'm having is that even after compiling as /target osx, I'm still starting the app on the Mac using electronize start. Per your posts above, that means I'm running with the precompiled Electron host at that point, rather than the custom packaged host created under the hood by electron-builder. I'll retry it this evening, and avoid running using electronize start, and since it's working for you, I'll assume it will for me as well. Thanks for the assistance.
Author
Owner

@bman46 commented on GitHub (Dec 9, 2021):

The correct application should be packaged in a .dmg under yourproject/bin/Desktop/Application Full Name-version.dmg

The application in that dmg file is the direct result of the build command and must be built on a linux/mac computer (not windows).

@bman46 commented on GitHub (Dec 9, 2021): The correct application should be packaged in a .dmg under _yourproject_/bin/Desktop/_Application Full Name_-_version_.dmg The application in that dmg file is the direct result of the build command and must be built on a linux/mac computer (not windows).
Author
Owner

@danatcofo commented on GitHub (Dec 9, 2021):

@SESA11057 correct, it will always be Electron when you use electronize start nothing you need to do about that, when you build and run the packaged version output from electronize build it will show the proper name. electronize start is intedended for development only and not production run.

@danatcofo commented on GitHub (Dec 9, 2021): @SESA11057 correct, it will always be Electron when you use `electronize start` nothing you need to do about that, when you build and run the packaged version output from `electronize build` it will show the proper name. `electronize start` is intedended for development only and not production run.
Author
Owner

@jesseflikweert commented on GitHub (Mar 15, 2022):

@bman46 When I execute the command electronize build /target osx /PublishReadyToRun false on Ubuntu, it seems to build correctly (as the return text ends with ...done). However, I can't find any .dmg file under myproject/bin/Desktop/. Doing the same for ... /target win ... works as I'm seeing a setup .exe file here. You probably need more information of me, but do you maybe have any idea what could be going wrong here?

@jesseflikweert commented on GitHub (Mar 15, 2022): @bman46 When I execute the command `electronize build /target osx /PublishReadyToRun false` on Ubuntu, it seems to build correctly (as the return text ends with `...done`). However, I can't find any .dmg file under _myproject/bin/Desktop/_. Doing the same for `... /target win ...` works as I'm seeing a setup .exe file here. You probably need more information of me, but do you maybe have any idea what could be going wrong here?
Author
Owner

@FlorianRappl commented on GitHub (Nov 1, 2025):

Outdated - use ElectronNET.Core and ElectronNET.Core.AspNet.

See Wiki / What's New.

@FlorianRappl commented on GitHub (Nov 1, 2025): Outdated - use `ElectronNET.Core` and `ElectronNET.Core.AspNet`. See [Wiki / What's New](https://github.com/ElectronNET/Electron.NET/wiki/What's-New).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#731