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
Framework Dependencies get removed from project files when running paket install. With paket 3.12.0 and later!
Repro steps
We have a package which depends on different framework deps (e.g. System.Configuration, System.IdentityModel, System.Runtime.Serialization, System.Web, System.XML, System.XML.Serialization). Another package has some similar dependencies (System.Configuration, System.IdentityModel, System.ServiceProcess).
When running paket install the references get removed despite the project has no dependencies defined neither the other packages. Somehow all dependencies of dependent packages won't be used.
After some investigation I think the wrong behaviour is, when there is a duplicate framework-dependency, all framework-dependencies get removed. In the case above I would assume that System.ServiceProcess should stay which is not.
The repo attached can be used to replay that. demo160824.zip
Expected behavior
Dependencies should stay as they are. Only remove the duplicates
Known workarounds
Use Version 3.11.3 and lower. It seems with the fix of bug #1333 this behaviour was introduced.
Related information
Windows 7
3.12.0 and later
.NET Runtime
The text was updated successfully, but these errors were encountered:
Description
Framework Dependencies get removed from project files when running
paket install. With paket 3.12.0 and later!Repro steps
We have a package which depends on different framework deps (e.g. System.Configuration, System.IdentityModel, System.Runtime.Serialization, System.Web, System.XML, System.XML.Serialization). Another package has some similar dependencies (System.Configuration, System.IdentityModel, System.ServiceProcess).
When running paket install the references get removed despite the project has no dependencies defined neither the other packages. Somehow all dependencies of dependent packages won't be used.
After some investigation I think the wrong behaviour is, when there is a duplicate framework-dependency, all framework-dependencies get removed. In the case above I would assume that System.ServiceProcess should stay which is not.
The repo attached can be used to replay that.
demo160824.zip
Expected behavior
Dependencies should stay as they are. Only remove the duplicates
Known workarounds
Use Version 3.11.3 and lower. It seems with the fix of bug #1333 this behaviour was introduced.
Related information
The text was updated successfully, but these errors were encountered: