How to publish multiple runtimes with dotnet cli to custom output folders
I have a csproj file which contains a few target runtimes, and I was hoping to have a singular command I could run which would build them all and put them in a designated directory. Something like this:
dotnet publish -c release -o ../../some-dist-folder
If I run this command I get a some-dist-folder full of good stuff, but I am unsure if it is just outputting a single runtime or all runtimes, as the folder contains:
|- *.dll
|- Refs
|- *.dll
|- Runtimes
|- Lots of folders
So there is no exe (not that surprised as thats only a windows thing) and the Runtimes seems to contain loads of folders relating to various linux/mac/windows runtimes etc.
However if I was to run:
dotnet publish -c release -r win-x64 -o ../../some-dist-folder
I get some apphost.exe and some other files and the runtimes folder is gone, so I am left wondering if the former approach where I am trying to just build everything at once is not actually working and I need to explicitly publish for each platform or if I need to manually pick out the bits I care about from the output.
Ideally I was hoping to run a command like the ones above and get an output folder like:
|- some-dist-folder
|- win-x64
|- osx-some-version
|- some-linux-distro-version
|- other-runtimes-version
So can I get close to this in a single command or is it just safer to manually run each publish explicitly?
.net .net-core dotnet-cli
asked Nov 12 at 11:42
Grofit
7,0371767150
add a comment |
I have a csproj file which contains a few target runtimes, and I was hoping to have a singular command I could run which would build them all and put them in a designated directory. Something like this:
dotnet publish -c release -o ../../some-dist-folder
If I run this command I get a some-dist-folder full of good stuff, but I am unsure if it is just outputting a single runtime or all runtimes, as the folder contains:
|- *.dll
|- Refs
|- *.dll
|- Runtimes
|- Lots of folders
So there is no exe (not that surprised as thats only a windows thing) and the Runtimes seems to contain loads of folders relating to various linux/mac/windows runtimes etc.
However if I was to run:
dotnet publish -c release -r win-x64 -o ../../some-dist-folder
I get some apphost.exe and some other files and the runtimes folder is gone, so I am left wondering if the former approach where I am trying to just build everything at once is not actually working and I need to explicitly publish for each platform or if I need to manually pick out the bits I care about from the output.
Ideally I was hoping to run a command like the ones above and get an output folder like:
|- some-dist-folder
|- win-x64
|- osx-some-version
|- some-linux-distro-version
|- other-runtimes-version
So can I get close to this in a single command or is it just safer to manually run each publish explicitly?
.net .net-core dotnet-cli
asked Nov 12 at 11:42
Grofit
7,0371767150
add a comment |
I have a csproj file which contains a few target runtimes, and I was hoping to have a singular command I could run which would build them all and put them in a designated directory. Something like this:
dotnet publish -c release -o ../../some-dist-folder
If I run this command I get a some-dist-folder full of good stuff, but I am unsure if it is just outputting a single runtime or all runtimes, as the folder contains:
|- *.dll
|- Refs
|- *.dll
|- Runtimes
|- Lots of folders
So there is no exe (not that surprised as thats only a windows thing) and the Runtimes seems to contain loads of folders relating to various linux/mac/windows runtimes etc.
However if I was to run:
dotnet publish -c release -r win-x64 -o ../../some-dist-folder
I get some apphost.exe and some other files and the runtimes folder is gone, so I am left wondering if the former approach where I am trying to just build everything at once is not actually working and I need to explicitly publish for each platform or if I need to manually pick out the bits I care about from the output.
Ideally I was hoping to run a command like the ones above and get an output folder like:
|- some-dist-folder
|- win-x64
|- osx-some-version
|- some-linux-distro-version
|- other-runtimes-version
So can I get close to this in a single command or is it just safer to manually run each publish explicitly?
.net .net-core dotnet-cli
asked Nov 12 at 11:42
Grofit
7,0371767150
I have a csproj file which contains a few target runtimes, and I was hoping to have a singular command I could run which would build them all and put them in a designated directory. Something like this:
dotnet publish -c release -o ../../some-dist-folder
If I run this command I get a some-dist-folder full of good stuff, but I am unsure if it is just outputting a single runtime or all runtimes, as the folder contains:
|- *.dll
|- Refs
|- *.dll
|- Runtimes
|- Lots of folders
So there is no exe (not that surprised as thats only a windows thing) and the Runtimes seems to contain loads of folders relating to various linux/mac/windows runtimes etc.
However if I was to run:
dotnet publish -c release -r win-x64 -o ../../some-dist-folder
I get some apphost.exe and some other files and the runtimes folder is gone, so I am left wondering if the former approach where I am trying to just build everything at once is not actually working and I need to explicitly publish for each platform or if I need to manually pick out the bits I care about from the output.
Ideally I was hoping to run a command like the ones above and get an output folder like:
|- some-dist-folder
|- win-x64
|- osx-some-version
|- some-linux-distro-version
|- other-runtimes-version
So can I get close to this in a single command or is it just safer to manually run each publish explicitly?
.net .net-core dotnet-cli
.net .net-core dotnet-cli
asked Nov 12 at 11:42
Grofit
7,0371767150
asked Nov 12 at 11:42
Grofit
7,0371767150
asked Nov 12 at 11:42
Grofit
7,0371767150
asked Nov 12 at 11:42
Grofit
7,0371767150
asked Nov 12 at 11:42
Grofit
7,0371767150
7,0371767150
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261427%2fhow-to-publish-multiple-runtimes-with-dotnet-cli-to-custom-output-folders%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261427%2fhow-to-publish-multiple-runtimes-with-dotnet-cli-to-custom-output-folders%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
