Repository navigation
With proj A depending on proj B - want to pack A with a.dll and b.dll #3893
Description
Details about Problem
NuGet Pack Task
NuGet version 4.0
VS version (if appropriate): VS 15
Detailed repro steps so we can see the same problem
-
Create a .Net Class Library (A)
-
Add another .Net Core Class Library (B)
-
Reference B from A
-
Set type in ProjectReference to Project
-
Pack A
Expected
Binaries from B are copied to lib/tfm
Actual
Still treats it as a PackageReference
...
Activity
[-]Unable to pack P2P dependencies as Project references[/-][+]With proj A depending on proj B - want to pack A with a.dll and b.dll[/+]rrelyea commentedon Dec 8, 2016
We don't plan to enable this in dotnet pack / msbuild /t:pack in 4.0 timeframe.
We'll listen to customer feedback and consider in the future.
rohit21agrawal commentedon Dec 9, 2016
Closing as duplicate of : #3891
kkm000 commentedon Jan 31, 2020
@rrelyea, "Focusing on NuGet client software to enable great work by the NuGet community!", wrote not even 3 years past:
If you want to hear the customer feedback, please go no further than #3891. 3.5 years worth of customer feedback is quite a collection. I must give you a fair warning, though, that the feedback is not exactly positive. I would call it rather agitated.
The biggest problem with the future is that it inevitably comes, but nobody knows exactly when this capricious creature will arrive. "we'll consider it in the future," let me express myself in a straightforward manner, is not a very informative answer. After 3 and a half years it would certainly be quite educating to understand how far, by the planning methodology that the team adopted, "the future" is from now. The only certain things I know about the future is that we will all die and that we'll pay taxes one way or another. Any other concept of "the future" is implicitly operational, and therefore requires a clarification, in my opinion. A rough numeric estimate expressed in time units would be immensely helpful. Thanks!