Use local project instead of referenced package dependency #11076
tarastriska
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have my own nuget package PackageA that depends on my other package PackageB (let say with version >=2.0.1)
Then I have solution with
MyTestProject that references MyOtherTestProject that references MyProjectB (this project produces PackageB).
MyTestProject references PackageA
As result I have runtime error when I try running the project because it expects PackageB dll from nuget.
I tried as a workaround to set Version and PackageVersion in MyProjectB but it did not help.
There was no issue with PackageB version like 0.1.* and it used default generated dll with version 1.0.0.0. But now I need to use higher version and it does not work.
And the idea is that MyTestProject is later built in docker with standard dotnet restore, build publish. So it must work both locally and in docker container.
This is the project that is used for testing purposes so I can do workaround. Could you please suggest any?
The only trick I can do is just to push some dummy version of PackageB with version starts with 0.* and it will work. But this workaround seems quite stupid so I'd like to hear better suggestions.
Beta Was this translation helpful? Give feedback.
All reactions