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

build.cmd doesn't produce nuget packages #843

Open
nazar322 opened this issue Apr 17, 2024 · 1 comment
Open

build.cmd doesn't produce nuget packages #843

nazar322 opened this issue Apr 17, 2024 · 1 comment
Labels

Comments

@nazar322
Copy link

  • Version: 23.6.2
  • Target:

Steps to Reproduce:

The wiki states Both projects create their own nuget package. The resulting nuget packages are saved under "/artifacts".
After build.cmd completes I don't get any files in the artifacts folder.

The story is that I'm trying to ping-point issue I posted here #842
So I've added handlers for apiProcess's uncaughtException and unhandledRejection.
I also want to add render-process-gone listener.

The problem is I want to replace electron.net's nuget files inside %userprofile%/.dotnet and %userprofile%/.nuget with the files containing my changes but I cannot do it since nuget files missing in the artifacts folder. For instance, the plain build does not create electronize.exe executable of the CLI project.

@nazar322 nazar322 added the bug label Apr 17, 2024
@gorsheninmv
Copy link

gorsheninmv commented May 4, 2024

What command do you use to create the packages?
Checked right now and the command build.cmd --target createpackages produces packages under the artifacts directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants