starred/Electron.NET
1
0
Fork 0
mirror of https://github.com/ElectronNET/Electron.NET.git synced 2026-02-03 21:25:13 +00:00
Code Issues 668 Packages Projects Releases 20 Wiki Activity

electronize build failing in Azure DevOps #950

New Issue
Closed
opened 2026-01-29 16:52:33 +00:00 by claunia · 1 comment
claunia commented 2026-01-29 16:52:33 +00:00
Owner
Copy Link

Originally created by @ayeshap20 on GitHub (May 9, 2024).

ElectronNET.CLI Version: 23.6.2.0
ElectronNet.API Version 23.6.2

  • Version:

.NET Core Version 6
Node.js Version 20.11.1

  • Target:
    Windows, Linux

I'm trying to create a windows installer for my app in CI but I'm running into a build error in my official release-signed pipeline:

CSC : error CS8002: Referenced assembly 'ElectronNET.API, Version=23.6.2.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.

I have disabled strong name signing but this error occurs in the build step (before signing). The command that I am using to generate the installer is: electronize build /target win /dotnet-configuration release.
I am able to build locally but I see that the ElectronNet.API dlls do not have any certification. I cannot use ElectronNet.API in production unless the binaries are signed. I'm looking for a workaround for this issue but if there's none available, I would like to request the dlls to be signed.

Originally created by @ayeshap20 on GitHub (May 9, 2024). <!-- Please search existing issues to avoid creating duplicates. --> <!-- Which version of Electron.NET CLI and API are you using? --> ElectronNET.CLI Version: 23.6.2.0 ElectronNet.API Version 23.6.2 <!-- Please always try to use latest version before report. --> * **Version**: <!-- Which version of .NET Core and Node.js are you using (if applicable)? --> .NET Core Version 6 Node.js Version 20.11.1 <!-- What target are you building for? --> * **Target**: Windows, Linux <!-- Enter your issue details below this comment. --> I'm trying to create a windows installer for my app in CI but I'm running into a build error in my official release-signed pipeline: _CSC : error CS8002: Referenced assembly 'ElectronNET.API, Version=23.6.2.0, Culture=neutral, PublicKeyToken=null' does not have a strong name._ I have disabled strong name signing but this error occurs in the build step (before signing). The command that I am using to generate the installer is: **electronize build /target win /dotnet-configuration release**. I am able to build locally but I see that the ElectronNet.API dlls do not have any certification. I cannot use ElectronNet.API in production unless the binaries are signed. I'm looking for a workaround for this issue but if there's none available, I would like to request the dlls to be signed. <!-- If you want, you can donate to increase issue priority (https://donorbox.org/electron-net) -->
claunia added the bug label 2026-01-29 16:52:33 +00:00
claunia commented 2026-01-29 16:52:34 +00:00
Author
Owner
Copy Link

@FlorianRappl commented on GitHub (Oct 31, 2025):

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

See Wiki / What's New.

@FlorianRappl commented on GitHub (Oct 31, 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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
api
applications
bug
bug
dev-experience
discussion
documentation
duplicate
enhancement
examples
Feature
Feature
good first issue
help wanted
In progress
information
infrastructure
invalid
javascript
macos
more-information-needed
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#950
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?