[GH-ISSUE #56] Publishing does not create an executable #26

New issue

Open

opened 2026-05-05 10:59:50 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 10:59:50 -06:00

Owner

Originally created by @MaxMommersteeg on GitHub (Aug 12, 2018).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/56

Today I tried to publish my application, but it does not seem to create an executable in the publish folder. I also tried this with the PhotoFrame.App and got the same result. Am I missing something?

Originally created by @MaxMommersteeg on GitHub (Aug 12, 2018). Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/56 Today I tried to publish my application, but it does not seem to create an executable in the publish folder. I also tried this with the PhotoFrame.App and got the same result. Am I missing something?

gitea-mirror commented

2026-05-05 10:59:53 -06:00

Author

Owner

@pauldotknopf commented on GitHub (Aug 12, 2018):

What command are you using to publish?

dotnet publish

That produces an output of this: http://termbin.com/2ekwe

Then the following is used to run the app.

cd bin/Debug/netcoreapp2.1/publish/
dotnet PhotoFrame.App.dll

There is an issue currently with deploying with a runtime ID specified (see here). If you wish to deploy with the runtime ID specific (which gives you native executables), you must dotnet publish without the Qml.Net.*Binaries packages, and then after publising, extract the Qml.Net.*Binaries NuGet package to your published directory manually.

@pauldotknopf commented on GitHub (Aug 12, 2018): What command are you using to publish? ``` dotnet publish ``` That produces an output of this: http://termbin.com/2ekwe Then the following is used to run the app. ``` cd bin/Debug/netcoreapp2.1/publish/ dotnet PhotoFrame.App.dll ``` There is an issue currently with deploying with a runtime ID specified (see [here](https://github.com/dotnet/cli/issues/9794)). If you wish to deploy with the runtime ID specific (which gives you native executables), you must ```dotnet publish``` without the ```Qml.Net.*Binaries``` packages, and then after publising, extract the ```Qml.Net.*Binaries``` NuGet package to your published directory manually.

gitea-mirror commented

2026-05-05 10:59:55 -06:00

Author

Owner

@MaxMommersteeg commented on GitHub (Aug 13, 2018):

Alright, I did not know about the issue. I indeed wanted native executables. Thanks, this issue can be closed.

@MaxMommersteeg commented on GitHub (Aug 13, 2018): Alright, I did not know about the issue. I indeed wanted native executables. Thanks, this issue can be closed.

gitea-mirror commented

2026-05-05 10:59:58 -06:00

Author

Owner

@pauldotknopf commented on GitHub (Oct 10, 2018):

Reopening, since this needs to be fixed. Multiple people keep running into this problem.

@pauldotknopf commented on GitHub (Oct 10, 2018): Reopening, since this needs to be fixed. Multiple people keep running into this problem.