-
Notifications
You must be signed in to change notification settings - Fork 29
Nuget package dependency incorrect version.. #11
Comments
@srininz77 Thank you for reporting this problem. It is actually an issue with NuGet: NuGet/Home#4337 |
Thanks. |
I've reopened this issue so that others can find the workaround more easily. I'll close it when the blocking NuGet issue is fixed. |
@srininz77 I've added your workaround to the readme. As it turns out, NuGet/Home#4790 is the blocking issue. |
Hi, using 2.3.2 even with @srininz77's workaround I see the problem behavior. I also noticed thats the deps.json file in the output directory appears to be ahead by 1:
In the .csproj file both MyProject and MyProject.Core had version 1.0.0-dev0006 before build and version 1.0.0-dev0007 after build. It seems like a mismatch in the json selection above. Update: I was seeing the .nuspec file problem because I was using Thanks! |
@achandlerwhite could you please create a repo to demonstrate the problem? |
@BalassaMarton sure here it is: https://github.com/achandlerwhite/MSBumpExample |
Good news, the NuGet issue has been fixed. Update NuGet with |
I have 2 projects - ProjectA and ProjectB.
I added MSBump nuget package to both the projects. I have the following version in both csproj files:
1.0.0-pre000002
ProjectB has dependency on ProjectA.
When I build the solution, the version number in both the projects are incremented to 1.0.0-pre000003 which is CORRECT.
However, the resulting ProjectB nuget package has dependency on ProjectA nuget package 1.0.0-pre000002 instead of 1.0.0-pre000003.
Any ideas why this is happening. Thank you.
The text was updated successfully, but these errors were encountered: