How to test nuget packages without officially publishing?
If I have one repo that holds libraries (that are published to Nuget) and a separate repo that holds the application code (that consumes the Nuget packages), is there an easy way to test changes to the library code within the application repo without publishing to the official Nuget feed?
nuget
asked Nov 20 at 20:52
user3338893
227412
add a comment |
If I have one repo that holds libraries (that are published to Nuget) and a separate repo that holds the application code (that consumes the Nuget packages), is there an easy way to test changes to the library code within the application repo without publishing to the official Nuget feed?
nuget
asked Nov 20 at 20:52
user3338893
227412
Publish to a private feed?
– Joe
Nov 20 at 20:55
What would the workflow look like for that? I imagine: update nuget.config with private feed (need to remove later), point all packages.config to the version on the private feed. Is there an easy way to do all of this? Looking for a solution with the least amount of resistance.
– user3338893
Nov 20 at 21:08
Your NuGet config or Visual Studio Nuget package settings would include both public and private sources. Create a branch for the application code and update to the new version (that initially only exists in the private feed). Test and if all OK publish to the public feed. You can also mark packages as being pre-release, whether on the private or public feed is up to you.
– Joe
Nov 21 at 7:09
add a comment |
If I have one repo that holds libraries (that are published to Nuget) and a separate repo that holds the application code (that consumes the Nuget packages), is there an easy way to test changes to the library code within the application repo without publishing to the official Nuget feed?
nuget
asked Nov 20 at 20:52
user3338893
227412
If I have one repo that holds libraries (that are published to Nuget) and a separate repo that holds the application code (that consumes the Nuget packages), is there an easy way to test changes to the library code within the application repo without publishing to the official Nuget feed?
nuget
nuget
asked Nov 20 at 20:52
user3338893
227412
asked Nov 20 at 20:52
user3338893
227412
asked Nov 20 at 20:52
user3338893
227412
asked Nov 20 at 20:52
user3338893
227412
asked Nov 20 at 20:52
user3338893
227412
227412
Publish to a private feed?
– Joe
Nov 20 at 20:55
What would the workflow look like for that? I imagine: update nuget.config with private feed (need to remove later), point all packages.config to the version on the private feed. Is there an easy way to do all of this? Looking for a solution with the least amount of resistance.
– user3338893
Nov 20 at 21:08
Your NuGet config or Visual Studio Nuget package settings would include both public and private sources. Create a branch for the application code and update to the new version (that initially only exists in the private feed). Test and if all OK publish to the public feed. You can also mark packages as being pre-release, whether on the private or public feed is up to you.
– Joe
Nov 21 at 7:09
add a comment |
Publish to a private feed?
– Joe
Nov 20 at 20:55
What would the workflow look like for that? I imagine: update nuget.config with private feed (need to remove later), point all packages.config to the version on the private feed. Is there an easy way to do all of this? Looking for a solution with the least amount of resistance.
– user3338893
Nov 20 at 21:08
Your NuGet config or Visual Studio Nuget package settings would include both public and private sources. Create a branch for the application code and update to the new version (that initially only exists in the private feed). Test and if all OK publish to the public feed. You can also mark packages as being pre-release, whether on the private or public feed is up to you.
– Joe
Nov 21 at 7:09
Publish to a private feed?
– Joe
Nov 20 at 20:55
Publish to a private feed?
– Joe
Nov 20 at 20:55
What would the workflow look like for that? I imagine: update nuget.config with private feed (need to remove later), point all packages.config to the version on the private feed. Is there an easy way to do all of this? Looking for a solution with the least amount of resistance.
– user3338893
Nov 20 at 21:08
What would the workflow look like for that? I imagine: update nuget.config with private feed (need to remove later), point all packages.config to the version on the private feed. Is there an easy way to do all of this? Looking for a solution with the least amount of resistance.
– user3338893
Nov 20 at 21:08
Your NuGet config or Visual Studio Nuget package settings would include both public and private sources. Create a branch for the application code and update to the new version (that initially only exists in the private feed). Test and if all OK publish to the public feed. You can also mark packages as being pre-release, whether on the private or public feed is up to you.
– Joe
Nov 21 at 7:09
Your NuGet config or Visual Studio Nuget package settings would include both public and private sources. Create a branch for the application code and update to the new version (that initially only exists in the private feed). Test and if all OK publish to the public feed. You can also mark packages as being pre-release, whether on the private or public feed is up to you.
– Joe
Nov 21 at 7:09
add a comment |
1 Answer
1
active
oldest
votes
Your build script could be something like this
step 1. build your package and copy your .nupkg's to %buildroot%newPackages
step 2. create a nuget.config file in your application code's root that adds %buildroot%newPackages as a packageSource. If your application code is a functional test, then you can probably check in the nuget.config, so it doesn't need to be recreated by the build machine every build.
step 3. Have a shell script or small program that updates your application code's references to the newly built package, to match the version that was just built
step 4 build/test your applicationCode
answered Nov 20 at 22:22
zivkan
1,104717
add a comment |
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%2f53401344%2fhow-to-test-nuget-packages-without-officially-publishing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your build script could be something like this
step 1. build your package and copy your .nupkg's to %buildroot%newPackages
step 2. create a nuget.config file in your application code's root that adds %buildroot%newPackages as a packageSource. If your application code is a functional test, then you can probably check in the nuget.config, so it doesn't need to be recreated by the build machine every build.
step 3. Have a shell script or small program that updates your application code's references to the newly built package, to match the version that was just built
step 4 build/test your applicationCode
answered Nov 20 at 22:22
zivkan
1,104717
add a comment |
Your build script could be something like this
step 1. build your package and copy your .nupkg's to %buildroot%newPackages
step 2. create a nuget.config file in your application code's root that adds %buildroot%newPackages as a packageSource. If your application code is a functional test, then you can probably check in the nuget.config, so it doesn't need to be recreated by the build machine every build.
step 3. Have a shell script or small program that updates your application code's references to the newly built package, to match the version that was just built
step 4 build/test your applicationCode
answered Nov 20 at 22:22
zivkan
1,104717
add a comment |
Your build script could be something like this
step 1. build your package and copy your .nupkg's to %buildroot%newPackages
step 2. create a nuget.config file in your application code's root that adds %buildroot%newPackages as a packageSource. If your application code is a functional test, then you can probably check in the nuget.config, so it doesn't need to be recreated by the build machine every build.
step 3. Have a shell script or small program that updates your application code's references to the newly built package, to match the version that was just built
step 4 build/test your applicationCode
answered Nov 20 at 22:22
zivkan
1,104717
Your build script could be something like this
step 1. build your package and copy your .nupkg's to %buildroot%newPackages
step 2. create a nuget.config file in your application code's root that adds %buildroot%newPackages as a packageSource. If your application code is a functional test, then you can probably check in the nuget.config, so it doesn't need to be recreated by the build machine every build.
step 3. Have a shell script or small program that updates your application code's references to the newly built package, to match the version that was just built
step 4 build/test your applicationCode
answered Nov 20 at 22:22
zivkan
1,104717
answered Nov 20 at 22:22
zivkan
1,104717
answered Nov 20 at 22:22
zivkan
1,104717
answered Nov 20 at 22:22
zivkan
1,104717
1,104717
add a comment |
add a comment |
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%2f53401344%2fhow-to-test-nuget-packages-without-officially-publishing%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
Publish to a private feed?
– Joe
Nov 20 at 20:55
What would the workflow look like for that? I imagine: update nuget.config with private feed (need to remove later), point all packages.config to the version on the private feed. Is there an easy way to do all of this? Looking for a solution with the least amount of resistance.
– user3338893
Nov 20 at 21:08
Your NuGet config or Visual Studio Nuget package settings would include both public and private sources. Create a branch for the application code and update to the new version (that initially only exists in the private feed). Test and if all OK publish to the public feed. You can also mark packages as being pre-release, whether on the private or public feed is up to you.
– Joe
Nov 21 at 7:09