How can I automate the addition of a Nuget package source?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
0
I'm trying to automate the restoration of some custom Nuget packages, which are stored at a custom repository host. I've got the package installed locally, but a fresh developer machine will fail to restore these packages because it won't know about the custom NuGet repository if my understanding of the configuration is correct.
Adding a custom NuGet source is not a huge deal, but I'd really like to get everything so that the developer can build right after pulling from version control. Is there...
- Any way to automate the addition of the custom NuGet repo as part of the source pull, i.e., is that stored anywhere in the source? Or...
- Is there any way to designate the custom source in the package config?
nuget nuget-package-restore
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
add a comment |
0
I'm trying to automate the restoration of some custom Nuget packages, which are stored at a custom repository host. I've got the package installed locally, but a fresh developer machine will fail to restore these packages because it won't know about the custom NuGet repository if my understanding of the configuration is correct.
Adding a custom NuGet source is not a huge deal, but I'd really like to get everything so that the developer can build right after pulling from version control. Is there...
- Any way to automate the addition of the custom NuGet repo as part of the source pull, i.e., is that stored anywhere in the source? Or...
- Is there any way to designate the custom source in the package config?
nuget nuget-package-restore
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
Did you try including a NuGet.Config file with your source in version control? You can define custom package sources in that file. So there is no need to add extra package sources in Visual Studio. NuGet will look for a NuGet.Config file based on the solution directory and work its way back up the directories to the root. So if you add it to the root of the version control source code then all solutions in the tree should use the information defined there.
– Matt Ward
Nov 26 '18 at 18:15
This may be the answer...but I thought they'd deprecated solution config in favor of machine-wide config.
– Chris B. Behrens
Nov 26 '18 at 19:19
I gave this a try, and it seems to work. If you want to move your comment to an answer, I'll mark it as correct.
– Chris B. Behrens
Nov 26 '18 at 19:47
Using a NuGet.Config file alongside your solution is not deprecated as far as I am aware. There is documentation on how the settings in NuGet.config files are applied - docs.microsoft.com/en-us/nuget/consume-packages/…
– Matt Ward
Nov 26 '18 at 23:18
add a comment |
0
0
0
I'm trying to automate the restoration of some custom Nuget packages, which are stored at a custom repository host. I've got the package installed locally, but a fresh developer machine will fail to restore these packages because it won't know about the custom NuGet repository if my understanding of the configuration is correct.
Adding a custom NuGet source is not a huge deal, but I'd really like to get everything so that the developer can build right after pulling from version control. Is there...
- Any way to automate the addition of the custom NuGet repo as part of the source pull, i.e., is that stored anywhere in the source? Or...
- Is there any way to designate the custom source in the package config?
nuget nuget-package-restore
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
I'm trying to automate the restoration of some custom Nuget packages, which are stored at a custom repository host. I've got the package installed locally, but a fresh developer machine will fail to restore these packages because it won't know about the custom NuGet repository if my understanding of the configuration is correct.
Adding a custom NuGet source is not a huge deal, but I'd really like to get everything so that the developer can build right after pulling from version control. Is there...
- Any way to automate the addition of the custom NuGet repo as part of the source pull, i.e., is that stored anywhere in the source? Or...
- Is there any way to designate the custom source in the package config?
nuget nuget-package-restore
nuget nuget-package-restore
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
asked Nov 26 '18 at 17:37
Chris B. BehrensChris B. Behrens
5,17963661
5,17963661
Did you try including a NuGet.Config file with your source in version control? You can define custom package sources in that file. So there is no need to add extra package sources in Visual Studio. NuGet will look for a NuGet.Config file based on the solution directory and work its way back up the directories to the root. So if you add it to the root of the version control source code then all solutions in the tree should use the information defined there.
– Matt Ward
Nov 26 '18 at 18:15
This may be the answer...but I thought they'd deprecated solution config in favor of machine-wide config.
– Chris B. Behrens
Nov 26 '18 at 19:19
I gave this a try, and it seems to work. If you want to move your comment to an answer, I'll mark it as correct.
– Chris B. Behrens
Nov 26 '18 at 19:47
Using a NuGet.Config file alongside your solution is not deprecated as far as I am aware. There is documentation on how the settings in NuGet.config files are applied - docs.microsoft.com/en-us/nuget/consume-packages/…
– Matt Ward
Nov 26 '18 at 23:18
add a comment |
Did you try including a NuGet.Config file with your source in version control? You can define custom package sources in that file. So there is no need to add extra package sources in Visual Studio. NuGet will look for a NuGet.Config file based on the solution directory and work its way back up the directories to the root. So if you add it to the root of the version control source code then all solutions in the tree should use the information defined there.
– Matt Ward
Nov 26 '18 at 18:15
This may be the answer...but I thought they'd deprecated solution config in favor of machine-wide config.
– Chris B. Behrens
Nov 26 '18 at 19:19
I gave this a try, and it seems to work. If you want to move your comment to an answer, I'll mark it as correct.
– Chris B. Behrens
Nov 26 '18 at 19:47
Using a NuGet.Config file alongside your solution is not deprecated as far as I am aware. There is documentation on how the settings in NuGet.config files are applied - docs.microsoft.com/en-us/nuget/consume-packages/…
– Matt Ward
Nov 26 '18 at 23:18
Did you try including a NuGet.Config file with your source in version control? You can define custom package sources in that file. So there is no need to add extra package sources in Visual Studio. NuGet will look for a NuGet.Config file based on the solution directory and work its way back up the directories to the root. So if you add it to the root of the version control source code then all solutions in the tree should use the information defined there.
– Matt Ward
Nov 26 '18 at 18:15
Did you try including a NuGet.Config file with your source in version control? You can define custom package sources in that file. So there is no need to add extra package sources in Visual Studio. NuGet will look for a NuGet.Config file based on the solution directory and work its way back up the directories to the root. So if you add it to the root of the version control source code then all solutions in the tree should use the information defined there.
– Matt Ward
Nov 26 '18 at 18:15
This may be the answer...but I thought they'd deprecated solution config in favor of machine-wide config.
– Chris B. Behrens
Nov 26 '18 at 19:19
This may be the answer...but I thought they'd deprecated solution config in favor of machine-wide config.
– Chris B. Behrens
Nov 26 '18 at 19:19
I gave this a try, and it seems to work. If you want to move your comment to an answer, I'll mark it as correct.
– Chris B. Behrens
Nov 26 '18 at 19:47
I gave this a try, and it seems to work. If you want to move your comment to an answer, I'll mark it as correct.
– Chris B. Behrens
Nov 26 '18 at 19:47
Using a NuGet.Config file alongside your solution is not deprecated as far as I am aware. There is documentation on how the settings in NuGet.config files are applied - docs.microsoft.com/en-us/nuget/consume-packages/…
– Matt Ward
Nov 26 '18 at 23:18
Using a NuGet.Config file alongside your solution is not deprecated as far as I am aware. There is documentation on how the settings in NuGet.config files are applied - docs.microsoft.com/en-us/nuget/consume-packages/…
– Matt Ward
Nov 26 '18 at 23:18
add a comment |
0
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
});
}
});
draft saved
draft discarded
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%2f53486334%2fhow-can-i-automate-the-addition-of-a-nuget-package-source%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53486334%2fhow-can-i-automate-the-addition-of-a-nuget-package-source%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
Did you try including a NuGet.Config file with your source in version control? You can define custom package sources in that file. So there is no need to add extra package sources in Visual Studio. NuGet will look for a NuGet.Config file based on the solution directory and work its way back up the directories to the root. So if you add it to the root of the version control source code then all solutions in the tree should use the information defined there.
– Matt Ward
Nov 26 '18 at 18:15
This may be the answer...but I thought they'd deprecated solution config in favor of machine-wide config.
– Chris B. Behrens
Nov 26 '18 at 19:19
I gave this a try, and it seems to work. If you want to move your comment to an answer, I'll mark it as correct.
– Chris B. Behrens
Nov 26 '18 at 19:47
Using a NuGet.Config file alongside your solution is not deprecated as far as I am aware. There is documentation on how the settings in NuGet.config files are applied - docs.microsoft.com/en-us/nuget/consume-packages/…
– Matt Ward
Nov 26 '18 at 23:18