I have two solutions:
Solution A
Project "A.Application" (0.0.1-alpha3)
Project "A.Domain" (0.0.1-alpha2)
Project "A.Infrastructure" (0.0.1-alpha2)
A.Application references A.Domain and A.Infrastructure as a ProjectReference.
Solution B
- Project "B.WebUI"
B.WebUI consumes each Project from A as separate Nugetpackage.
What i do:
Now i make a change in one Library. I publish the package to our local Nuget-Source in the Package Manager Console and increase the Prerelease-Number:
dotnet pack .\A.Application --version-suffix "-alpha.4" --output "mypath"
Problem:
When i want to update the Project "A.Application" in B.WebUI over the Nuget-Package-Explorer to the newest version i get following errors:
Unable to find package A.Domain with version (>= 0.0.1-alpha.4)Unable to find package A.Infrastructure with version (>= 0.0.1-alpha.4)
alpha4 does not exist because this packages are still in alpha2. I don't want to pack all unchanged libraries again and again to match the same number.
Question:
How can i define that A.Applicaton should still be happy with older versions? Do i have to specify a nuspec file or ist there another possibility inside the PMC or the Project-File?
Edit:
The contents of the nupkg. The depencies are also incremented to alpha6 because this dlls are added as projectreferences: