This is my scenario:
During the development of the nuget A package in project A in solution A, we constantly need to test it in another project. For this reason, we have the dev nuget channel, which contains the unreleased package A. When you create solution A, it will be automatically inserted into this dev file.
For testing, we have solution B with several projects that all reference packages A from this dev nuget feed.
Whenever we rebuild solution A (and package a gets to the feed), we want to use the new package assembly in all projects of solution B during testing.
Once package A has actually been released, it will be redirected to the nuget release channel, and then Solution B should pull the package out of the release feed, not the dev file.
And these are my two questions:
What is the correct way to force package A to be downloaded to the package folder of Solution B and make all projects use the new package assembly , even if the package version has not changed.
What is the suggested workflow for this (general?) Scenario? Should I do it differently?
c # nuget nuget-package
bitbonk
source share