Electronize.exe does not let you specify different electron.manifest.json #409

New Issue

claunia · 2026-01-29T16:38:53Z

claunia commented

2026-01-29 16:38:53 +00:00

Originally created by @robertmclaws on GitHub (Nov 13, 2019).

Originally assigned to: @GregorBiswanger on GitHub.

Version: 5.30.1
.NET Core Version: 3.0

Issue: I'm trying to automate my builds and create different "channels" (Dev/Beta/Prod). I wanted to use the /electron-params switch to specify the file myself... but the file name is hardcoded to the executable. I should be able to specify the file name myself, so I can have a electron.manifest.dev.json file, etc.

As for now, I'm kind of stuck, because I can't even use token replacement to get what I want, because that would break local builds. I'm going to have to resort to file renaming on the build server... which is also more complex than necessary.

Thanks so much for looking into this!

Originally created by @robertmclaws on GitHub (Nov 13, 2019). Originally assigned to: @GregorBiswanger on GitHub. * **Version**: 5.30.1 * **.NET Core Version**: 3.0 **Issue**: I'm trying to automate my builds and create different "channels" (Dev/Beta/Prod). I wanted to use the /electron-params switch to specify the file myself... but the file name is hardcoded to the executable. I should be able to specify the file name myself, so I can have a electron.manifest.dev.json file, etc. As for now, I'm kind of stuck, because I can't even use token replacement to get what I want, because that would break local builds. I'm going to have to resort to file renaming on the build server... which is also more complex than necessary. Thanks so much for looking into this!

claunia added the Feature In progress labels 2026-01-29 16:38:53 +00:00

claunia closed this issue

2026-01-29 16:38:54 +00:00

claunia commented

2026-01-29 16:38:55 +00:00

@GregorBiswanger commented on GitHub (Nov 13, 2019):

Thank you for your donation!

At the moment I am sick. If I am well again on the weekend, I will take care of your wishes as soon as possible .. at the latest next week ..

@GregorBiswanger commented on GitHub (Nov 13, 2019): **Thank you for your donation!** At the moment I am sick. If I am well again on the weekend, I will take care of your wishes as soon as possible .. at the latest next week ..

claunia commented

2026-01-29 16:38:55 +00:00

@GregorBiswanger commented on GitHub (Nov 30, 2019):

Implemented! Available in Electron.NET version 7.30.2.

You can add additional manifest files with:

electronize init /manifest beta

The Electron.NET CLI creates a electron.manifest.beta.json file into your project with debug profile.

You can start for debug your Electron.NET app with:

electronize start /manifest electron.manifest.beta.json

You can build your Electron.NET app with:

electronize build /target win /manifest electron.manifest.beta.json

@GregorBiswanger commented on GitHub (Nov 30, 2019): Implemented! Available in Electron.NET version 7.30.2. **You can add additional manifest files with:** `electronize init /manifest beta` The Electron.NET CLI creates a electron.manifest.beta.json file into your project with debug profile. **You can start for debug your Electron.NET app with:** `electronize start /manifest electron.manifest.beta.json` **You can build your Electron.NET app with:** `electronize build /target win /manifest electron.manifest.beta.json`

claunia commented

2026-01-29 16:38:55 +00:00

@arun-chief commented on GitHub (Jan 30, 2020):

There was a manifest error when used visual studio package manager console. but when run with visual studio code it worked.

@arun-chief commented on GitHub (Jan 30, 2020): There was a manifest error when used visual studio package manager console. but when run with visual studio code it worked.

claunia referenced this issue

2026-01-29 16:57:55 +00:00

[PR #409] [MERGED] Add missing config parameter fixes #407 #1160

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#409