--no-self-contained flag is forced upon build #486

New Issue

claunia · 2026-01-29T16:40:59Z

claunia commented

2026-01-29 16:40:59 +00:00

Originally created by @kylethomas320 on GitHub (May 11, 2020).

Originally assigned to: @GregorBiswanger on GitHub.

Version: 8.31.1

Target: .NET Core 3.1

I recently upgraded from the previous electron v7 to v8.31.1 and noticed that --no-self-contained is put in the build command. I need my build to be a self contained file, as in previous versions of Electron .NET. Will this be fixed in a later version? As this is hardcoded in the c# CLI code, I can't force it to go to self-contained myself. See: b6417d0718 (diff-3da8aff670c488206e99f7abe0c6f1bd).

Build command used:
dotnet build /target win

Thanks for the support!

Originally created by @kylethomas320 on GitHub (May 11, 2020). Originally assigned to: @GregorBiswanger on GitHub.    * **Version**: 8.31.1   * **Target**: .NET Core 3.1  I recently upgraded from the previous electron v7 to v8.31.1 and noticed that `--no-self-contained` is put in the build command. I need my build to be a self contained file, as in previous versions of Electron .NET. Will this be fixed in a later version? As this is hardcoded in the c# CLI code, I can't force it to go to self-contained myself. See: https://github.com/ElectronNET/Electron.NET/commit/b6417d0718bca7a155b293175aa9afd50ce194d0#diff-3da8aff670c488206e99f7abe0c6f1bd. Build command used: `dotnet build /target win` Thanks for the support!

claunia added the bug label 2026-01-29 16:40:59 +00:00

claunia referenced this issue

2026-01-29 16:58:19 +00:00

[PR #486] [MERGED] 442: maintain references between socket.io connection events #1197

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#486