Skip to content
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

Call electronize from the Path instead of via dotnet in launchSettings.json #243

Merged
merged 1 commit into from
May 15, 2019
Merged

Call electronize from the Path instead of via dotnet in launchSettings.json #243

merged 1 commit into from
May 15, 2019

Conversation

Hecatron
Copy link
Contributor

@Hecatron Hecatron commented May 8, 2019

I've noticed that when calling electronize init
The default behaviour is to modify launchSettings.json to add a profile to launch electronize via dotnet
However this would only work if electronize.exe was renamed to dotnet-electronize.exe in the tools directory

I've modified the init routine and the launchSettings.json of the example web app
to instead call electronize directly from the Path
Typically under windows it's located under C:\Users\UserName\.dotnet\tools\electronize.exe
which seems to be on my path by default.
For info the WorkingDirectory parameter of "." is needed to place the working directory in the same directory as the .csproj file instead of somewhere inside a bin/Debug folder.

The only other way to fix this would be to rename electronize.exe to dotnet-electronize.exe when it's installed as a tool

dotnet tool install ElectronNET.CLI -g

see https://github.com/natemcmaster/dotnet-tools

@GregorBiswanger GregorBiswanger merged commit 73f7e5a into ElectronNET:master May 15, 2019
@Hecatron Hecatron deleted the hecatron-dev branch May 15, 2019 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants