.NET.Core “Framework-dependent deployment” with NuGet 3rd party dependencies for a different environment
Perhaps I understand correctly from here, that the "Framework-dependent deployment" does not contain 3rd party dependent assemblies added through package references to the .NET Core console app project.
Running it (I mean something like dotnet myproj.dll) seems to work for the development environment it self without any troubles. I encountered troubles in case of "Framework-dependent deployment" to the Raspberry Pi though, where it was not easy to figure out all of the 3rd party assemblies I have to include.
I believe, that similar difficulties can appear also in case of deployment to just a different environment.
I am not good in NuGet packages, so is there a tooling (or a possible planned switch for the "Framework-dependent deployment") or a different way to automatically include actually needed 3rd party assemblies to that "Framework-dependent deployment"?
I also found out, that my own project references are correctly included in the deployment. (Theoretically if the 3rd party licences would allow, I could add those 3rd party libs source code as a referenced project and the deployment will contain the needed dll(s). But I believe, there could be more elegant way to accomplish that. So any ideas/ hints here?
deployment .net-core nuget
edited Nov 24 at 7:46
marc_s
570k12811021250
asked Nov 21 at 0:13
Mojmir Rychly
88119
add a comment |
Perhaps I understand correctly from here, that the "Framework-dependent deployment" does not contain 3rd party dependent assemblies added through package references to the .NET Core console app project.
Running it (I mean something like dotnet myproj.dll) seems to work for the development environment it self without any troubles. I encountered troubles in case of "Framework-dependent deployment" to the Raspberry Pi though, where it was not easy to figure out all of the 3rd party assemblies I have to include.
I believe, that similar difficulties can appear also in case of deployment to just a different environment.
I am not good in NuGet packages, so is there a tooling (or a possible planned switch for the "Framework-dependent deployment") or a different way to automatically include actually needed 3rd party assemblies to that "Framework-dependent deployment"?
I also found out, that my own project references are correctly included in the deployment. (Theoretically if the 3rd party licences would allow, I could add those 3rd party libs source code as a referenced project and the deployment will contain the needed dll(s). But I believe, there could be more elegant way to accomplish that. So any ideas/ hints here?
deployment .net-core nuget
edited Nov 24 at 7:46
marc_s
570k12811021250
asked Nov 21 at 0:13
Mojmir Rychly
88119
add a comment |
Perhaps I understand correctly from here, that the "Framework-dependent deployment" does not contain 3rd party dependent assemblies added through package references to the .NET Core console app project.
Running it (I mean something like dotnet myproj.dll) seems to work for the development environment it self without any troubles. I encountered troubles in case of "Framework-dependent deployment" to the Raspberry Pi though, where it was not easy to figure out all of the 3rd party assemblies I have to include.
I believe, that similar difficulties can appear also in case of deployment to just a different environment.
I am not good in NuGet packages, so is there a tooling (or a possible planned switch for the "Framework-dependent deployment") or a different way to automatically include actually needed 3rd party assemblies to that "Framework-dependent deployment"?
I also found out, that my own project references are correctly included in the deployment. (Theoretically if the 3rd party licences would allow, I could add those 3rd party libs source code as a referenced project and the deployment will contain the needed dll(s). But I believe, there could be more elegant way to accomplish that. So any ideas/ hints here?
deployment .net-core nuget
edited Nov 24 at 7:46
marc_s
570k12811021250
asked Nov 21 at 0:13
Mojmir Rychly
88119
Perhaps I understand correctly from here, that the "Framework-dependent deployment" does not contain 3rd party dependent assemblies added through package references to the .NET Core console app project.
Running it (I mean something like dotnet myproj.dll) seems to work for the development environment it self without any troubles. I encountered troubles in case of "Framework-dependent deployment" to the Raspberry Pi though, where it was not easy to figure out all of the 3rd party assemblies I have to include.
I believe, that similar difficulties can appear also in case of deployment to just a different environment.
I am not good in NuGet packages, so is there a tooling (or a possible planned switch for the "Framework-dependent deployment") or a different way to automatically include actually needed 3rd party assemblies to that "Framework-dependent deployment"?
I also found out, that my own project references are correctly included in the deployment. (Theoretically if the 3rd party licences would allow, I could add those 3rd party libs source code as a referenced project and the deployment will contain the needed dll(s). But I believe, there could be more elegant way to accomplish that. So any ideas/ hints here?
deployment .net-core nuget
deployment .net-core nuget
edited Nov 24 at 7:46
marc_s
570k12811021250
asked Nov 21 at 0:13
Mojmir Rychly
88119
edited Nov 24 at 7:46
marc_s
570k12811021250
asked Nov 21 at 0:13
Mojmir Rychly
88119
edited Nov 24 at 7:46
marc_s
570k12811021250
edited Nov 24 at 7:46
marc_s
570k12811021250
edited Nov 24 at 7:46
marc_s
570k12811021250
570k12811021250
asked Nov 21 at 0:13
Mojmir Rychly
88119
asked Nov 21 at 0:13
Mojmir Rychly
88119
asked Nov 21 at 0:13
Mojmir Rychly
88119
88119
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%2f53403521%2fnet-core-framework-dependent-deployment-with-nuget-3rd-party-dependencies-for%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%2f53403521%2fnet-core-framework-dependent-deployment-with-nuget-3rd-party-dependencies-for%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
