You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
against Project B where Project B has a paket.references defined as
nuget ProjectA
Then the packaging process will fail
Paket version 2.52.3.0
Paket failed with:
The given key was not present in the dictionary.
This is because the solution level paket.dependencies doesn't contain an entry for ProjectA.
It would be nice to have a friendly error message rather than the generic key not found exception in this case. However I do accept this is user error :)
nuget ProjectA is actually not correct syntax in paket.references.
It would be correct to inly write ProjectA - but I see this as a common mistake and made the parser accept this.
Very minor issue.
If you create a solution with two projects. Project A and B.
Project B depends on Project A.
If you attempt to run
paket.exe pack buildconfig "Debug" buildplatform "AnyCPU" output ..\..\Binagainst Project B where Project B has a paket.references defined as
nuget ProjectAThen the packaging process will fail
Paket version 2.52.3.0
Paket failed with:
The given key was not present in the dictionary.
This is because the solution level paket.dependencies doesn't contain an entry for ProjectA.
It would be nice to have a friendly error message rather than the generic key not found exception in this case. However I do accept this is user error :)
zip which reproduces the issue is attached.
PaketDemo.zip
The text was updated successfully, but these errors were encountered: