-
-
Notifications
You must be signed in to change notification settings - Fork 735
Build fails with latest electron-builder version #288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! I have same problem! Its the first time that I trying Electron.NET and I can't generate executable of my application... |
@fabio-basedev, as far as I can tell, an older version won't help you either since it's internally calling the |
I think the problem with https://www.npmjs.com/package/electron-builder version 21.* if update command "npm install electron-builder --global" to "npm install [email protected] --global" application will be created as usual |
@GeorgDangl steps for a workaround
|
@denisHordienko, thanks for the input! I've created PR #289 with the fix. Looking forward to feedback! |
Awesome! Here works like a charm! Thanks! |
Arghh - I can't use this fix as I'm building my releases on Azure DevOps. Any ideas when a fix will be applied to the nuget packages / Electron.net global tools? |
@robalexclark, it's the same for me in my CI builds. I think you could do automate the replacement for the changed binaries in the CI environment, but that's a route I wouldn't want to go😉 @robertmuehsig, @GregorBiswanger, do you have an ETA for how fast you can merge this PR and create a new release? If you're not available, I can upload a fork with the fix to NuGet to be used as temporary workaround. |
Hey guys, I've uploaded a temporary package with the hotfix: ElectronNET.CLI-hotfix. You can install it via
and just use |
@GeorgDangl Thank you very much for your support! We will gladly accept your PR. I think additional NuGet packages would only irritate. For the new version, however, I have time until next week. |
Hi - Any news on when updated nuget packages and tools will be published? My CI pipeline is not longer continuous... |
Hi @robalexclark, I‘ve published the ElectronNET.CLI-hotfix Package on NuGet last week, see my comment a few posts above. You should be able to use this in the meantime. |
Hey Community, |
Hey @GregorBiswanger, no worries, sometimes there are more important things. Thank you for the great work you're doing with Electron.NET, I really appreciate it! |
@GregorBiswanger I agree with @GeorgDangl , family comes first. |
RESOLVED@GeorgDangl I'm currently using your hotfix as Chrome doesn't open using the original electronize. With your hotfix, Chrome opens and my javascript runs but I encountered a problem during startup. |
Hi @rakista112, unfortunately, I have no idea what's causing this. All I did was create a NuGet package that includes PR #289 and released it. Do you have any idea where the relevant bits of the code are? I'm not yet familiar with the Electron.NET codebase. |
RESOLVED@GeorgDangl oh it seems to be caused by my Vue build. Nothing to do with Electron. I'll just mark my comments as resolved. |
I implemented the support for the newest electron-builder. |
Build Electron Application... after this it do not even provides the build for application. @GregorBiswanger help me out in this regard. |
Steps to Reproduce:
Performing a regular build with
fails since the BuildCommand seems to pass invalid CLI arguments to
electron-builder
.I'm getting the following output:
Please note how the
BuildCommand
passes arguments forplatform
andarch
toelectron-builder
, both don't seem to be supported.I've also noticed that the BuildCommand performs a global installation of
electron-builder
on each run, which results in always using the latest version. This seems very prone to similar errors like this due to future breaking changes inelectron-builder
.Would it be possible to simply install
electron-builder
locally with a fixed version? That should also solve the problem of it not working on Linux. If you're OK with that, I'd be happy to provide a PR.Btw, this is currently totally blocking for me and I don't have any workarounds😊
The text was updated successfully, but these errors were encountered: