Electronize Command Imporvements #380

New Issue

claunia · 2026-01-29T16:38:04Z

claunia commented

2026-01-29 16:38:04 +00:00

Originally created by @Nikey646 on GitHub (Aug 24, 2019).

Originally assigned to: @GregorBiswanger on GitHub.

The CLI is so bare bones, that it's actually hard to work with.

Some suggestions include providing the capability to automatically use Environment Variables provided via the default launch profiles. This will allow the usage of env.IsDevelopment() and etc.

Rather than building the main application and than executing the binary, launching the application via dotnet run on the .csproj would be preferable. Continuing from this, it should support the dotnet watch tool, allowing the developer to make changes to the the ASP.Net Core webapp and having the server automatically re-compile.

On a side note, because I don't really want to make another issue to suggest this, pointing developers using SPA frameworks to the SpaServices extension (Mircosoft.AspNetCore.SpaServices) and using the ISpaBuilder.UseProxyToSpaDevelopmentServer method to provide hot reloading without any additional configuration from the standard framework methods,

Originally created by @Nikey646 on GitHub (Aug 24, 2019). Originally assigned to: @GregorBiswanger on GitHub. The CLI is so bare bones, that it's actually hard to work with. Some suggestions include providing the capability to automatically use Environment Variables provided via the default launch profiles. This will allow the usage of `env.IsDevelopment()` and etc. Rather than building the main application and than executing the binary, launching the application via `dotnet run` on the .csproj would be preferable. Continuing from this, it should support the `dotnet watch` tool, allowing the developer to make changes to the the ASP.Net Core webapp and having the server automatically re-compile. On a side note, because I don't really want to make another issue to suggest this, pointing developers using SPA frameworks to the SpaServices extension (`Mircosoft.AspNetCore.SpaServices`) and using the `ISpaBuilder.UseProxyToSpaDevelopmentServer` method to provide hot reloading without any additional configuration from the standard framework methods,

claunia added the Feature label 2026-01-29 16:38:04 +00:00

claunia closed this issue

2026-01-29 16:38:04 +00:00

claunia commented

2026-01-29 16:38:05 +00:00

@GregorBiswanger commented on GitHub (Dec 3, 2019):

For 90% of the cases, it is enough to implement the application in the browser and then process it for Electron. So you can easily maintain your developer comfort without any problems.

I'm thinking about a solution for dotnet watch with Electron.NET CLI.

@GregorBiswanger commented on GitHub (Dec 3, 2019): For 90% of the cases, it is enough to implement the application in the browser and then process it for Electron. So you can easily maintain your developer comfort without any problems. I'm thinking about a solution for `dotnet watch` with Electron.NET CLI.

claunia commented

2026-01-29 16:38:05 +00:00

@GregorBiswanger commented on GitHub (Apr 21, 2020):

Live reload is on the way with Electron.NET version 8.31.1 >> #380

@GregorBiswanger commented on GitHub (Apr 21, 2020): Live reload is on the way with Electron.NET version 8.31.1 >> #380

claunia referenced this issue

2026-01-29 16:57:51 +00:00

[PR #380] [CLOSED] Live Reload Implemented #1151

Sign in to join this conversation.