The application has been generated successfully. No interface will be displayed when opening exe? #749

Closed
opened 2026-01-29 16:47:37 +00:00 by claunia · 8 comments
Owner

Originally created by @lzb949838390 on GitHub (Jan 2, 2022).

🚨 The issue tracker is not for questions 🚨

Originally created by @lzb949838390 on GitHub (Jan 2, 2022). 🚨 The issue tracker is not for questions 🚨
claunia added the question label 2026-01-29 16:47:37 +00:00
Author
Owner

@lzb949838390 commented on GitHub (Jan 2, 2022):

97a5fe99a40ecb2c614272205d4678c
1641106026(1)

@lzb949838390 commented on GitHub (Jan 2, 2022): ![97a5fe99a40ecb2c614272205d4678c](https://user-images.githubusercontent.com/49229285/147868456-7d8846db-de1b-4fe7-9eb0-5f37ba0c09f5.png) ![1641106026(1)](https://user-images.githubusercontent.com/49229285/147868461-b8fba6b5-a070-4ce8-b3b0-717140730544.jpg)
Author
Owner

@lzb949838390 commented on GitHub (Jan 2, 2022):

“electronize start” success
“electronize build /target win” has question

@lzb949838390 commented on GitHub (Jan 2, 2022): “electronize start” success “electronize build /target win” has question
Author
Owner

@lzb949838390 commented on GitHub (Jan 2, 2022):

I run \bin\Desktop\win-unpacked\resources\bin\OOP.BMS.Web.exe
1641107119(1)

@lzb949838390 commented on GitHub (Jan 2, 2022): I run \bin\Desktop\win-unpacked\resources\bin\OOP.BMS.Web.exe ![1641107119(1)](https://user-images.githubusercontent.com/49229285/147868784-0c799c49-ffcb-4048-a423-1713c89844ab.jpg)
Author
Owner

@danatcofo commented on GitHub (Jan 2, 2022):

Looks like a bug in your code. This is not likely an electron.net issue.

@danatcofo commented on GitHub (Jan 2, 2022): Looks like a bug in your code. This is not likely an electron.net issue.
Author
Owner

@schaveyt commented on GitHub (Jan 3, 2022):

@lzb949838390

NOTE: When electronzie build is executed, it calls to generate a single-file, self-contained exe:

 dotnet publish ....... /p:PublishReadyToRun=true /p:PublishSingleFile=true --self-contained

By the looks of the exception, your code is utilizing reflection in a particular why that does not work when things are published as a single file. I found this issue over in the dotnet/runtime repo explaining why this is so.

You can either adjust your code or you can disable the single-file flag by:

electronize build /target win /p:publishSingleFile=false
@schaveyt commented on GitHub (Jan 3, 2022): @lzb949838390 __NOTE:__ When `electronzie build` is executed, it calls to generate a single-file, self-contained exe: ~~~bash dotnet publish ....... /p:PublishReadyToRun=true /p:PublishSingleFile=true --self-contained ~~~ By the looks of the exception, your code is utilizing reflection in a particular why that does __not__ work when things are published as a single file. I found [this issue](https://github.com/dotnet/runtime/issues/44511#issuecomment-768345967) over in the dotnet/runtime repo explaining why this is so. You can either adjust your code or you can disable the single-file flag by: ~~~bash electronize build /target win /p:publishSingleFile=false ~~~
Author
Owner

@lzb949838390 commented on GitHub (Jan 4, 2022):

@schaveyt Thank you.I have solved the problem of win build. But I have a new problem,Error occurred while linux build.
look...
1641283801(1)

@lzb949838390 commented on GitHub (Jan 4, 2022): @schaveyt Thank you.I have solved the problem of win build. But I have a new problem,Error occurred while linux build. look... ![1641283801(1)](https://user-images.githubusercontent.com/49229285/148028525-fb681504-8f9c-4e9a-a147-808301157235.jpg)
Author
Owner

@sirkadirov commented on GitHub (Jan 10, 2022):

Hi, @lzb949838390! As I can see (https://github.com/electron-userland/electron-builder/issues/3569), it's a temporary (or not so temporary 😢: https://github.com/electron-userland/electron-build-service/issues/17) error caused due to unreachable remote build server, which is used by electron-builder - a npm package and an infrastructure that handles electron apps packaging. You can try again later, or set up a build agent on a local machine. If you need to automate your Electron.NET app's builds, try using CI services like Travis CI, GitHub Actions or AppVeyor - I think that it would be easier to set up and maintain than hosting own build agent for electron-builder.

@sirkadirov commented on GitHub (Jan 10, 2022): Hi, @lzb949838390! As I can see (https://github.com/electron-userland/electron-builder/issues/3569), it's a temporary (or not so temporary 😢: https://github.com/electron-userland/electron-build-service/issues/17) error caused due to unreachable remote build server, which is used by `electron-builder` - a npm package and an infrastructure that handles electron apps packaging. You can try again later, or [set up a build agent on a local machine](https://www.electron.build/multi-platform-build). If you need to automate your Electron.NET app's builds, try using CI services like Travis CI, GitHub Actions or AppVeyor - I think that it would be easier to set up and maintain than hosting own build agent for `electron-builder`.
Author
Owner

@FlorianRappl commented on GitHub (Nov 2, 2025):

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

See Wiki / What's New.

@FlorianRappl commented on GitHub (Nov 2, 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#749