You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ElectronNET.CLI Version: 23.6.2.0
ElectronNet.API Version 23.6.2
.NET Core Version 6
Node.js Version 20.11.1
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.
The text was updated successfully, but these errors were encountered: