Why is $(ElectronPackageId) mapped to different electron builder items or am I confused how this works

[markatosi]

• Version: 4.0

• Target: .net 10.0.1

ElectronPackageId seems to be mapped to: (according to the wiki) multiple items from electron builder config that should be separate values. I may be confused on this point though but this is what the wiki implies.

This is problematic. For instance Apple wants the appId value to conform to
com.companyname.appname

{
  "name": "$(ElectronPackageId)", <== HERE
  "productName": "$(ElectronTitle)",
  "build": {
    "appId": "$(ElectronPackageId)", <== HERE
    "linux": {
      "desktop": {
        "entry": { "Name": "$(Title)" }
      },
      "executableName": "$(ElectronPackageId)" <== HERE
    },
    "deb": {
      "desktop": {
        "entry": { "Name": "$(Title)" }
      }
    }
  },
  "description": "$(Description)",
  "version": "$(Version)",
  "main": "main.js",
  "author": {
    "name": "$(Company)"
  },
  "license": "$(License)",
  "executable": "$(TargetName)",
  "singleInstance": "$(ElectronSingleInstance)",
  "homepage": "$(ProjectUrl)",
  "splashscreen": {
    "imageFile": "$(ElectronSplashScreen)"
  }
}

[softworkz]

The only value that is being hard-set here is "name".

The others are only defaults, they are set here because they should have a reasonable and consistent value (by default), especially since electron-builder uses a different executable name on Linux than on other platforms, but for dotnet-first app launch, we need a consistent executable name (unless someone takes control of it explicitly).

So, why "only defaults"? Because the JSON value of "build" is the electron-builder config and what you have in electron-builder.json should get merged over this, allowing you to override those values there.

[markatosi]

Cool, thanks for the clarification