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
Here, we are trying to install WindowsNative in the project Sandbox2.0.
The commands listed below do not have the same effect on the .csproj file. We were expecting the old behavior. If the new behavior is the correct one, why is it so?
Expected behavior
When we ran : .paket\paket.exe.old.exe update (2.66.3.0)
Paket used to create a reference to that dll in the .csproj file.
Actual behavior
Now, when we run : .paket\paket.exe.new.exe update (3.8.1.0)
The reference is removed from the .csproj file.
Known workarounds
Link directly to the .dll (bad workaround)
The text was updated successfully, but these errors were encountered:
Description
We encountered a new problem with one of our packages. When we pulled on it, paket did not add a reference to the dll in the project file.
Repro steps
Here is a repro sample;
https://github.com/franknarf8/paket-issue-repro/tree/b363bf2d50031e71ff9bb3a39ca471b44b64f8c7
Here, we are trying to install WindowsNative in the project Sandbox2.0.
The commands listed below do not have the same effect on the .csproj file. We were expecting the old behavior. If the new behavior is the correct one, why is it so?
Expected behavior
When we ran :
.paket\paket.exe.old.exe update
(2.66.3.0)Paket used to create a reference to that dll in the .csproj file.
Actual behavior
Now, when we run :
.paket\paket.exe.new.exe update
(3.8.1.0)The reference is removed from the .csproj file.
Known workarounds
Link directly to the .dll (bad workaround)
The text was updated successfully, but these errors were encountered: