birger
(Birger Buhl Dinesen)
December 11, 2019, 3:59pm
1
This used to work (I think).
Quite simple setup: One .NET solution with
a) Console App EXE
b) Class Library Assembly DLL (references external NuGet packages)
NuGet reference in project b:
<NuGetReference Include="FirebirdSql.Data.FirebirdClient:*">
<Private>True</Private>
</NuGetReference>
Project a references project b.
The FireBird DLL is referenced implicitly/indirectly in project a (through project b reference).
The problem now is that the FireBird DLL is no longer copied to the output folder of project a. As it used to.
So, now I have to reference the NuGet package as well directly from project a.
birger
(Birger Buhl Dinesen)
December 11, 2019, 4:00pm
2
Using Water .2459 and .2961
mh
(marc hoffman)
December 11, 2019, 8:32pm
3
Is this a project reference? is the project ref and the NuGet reference set to CopyLocal? If so, that should work, I’d appreciate a testcase oof you have one.
mh
(marc hoffman)
December 11, 2019, 8:36pm
4
Reproduces, something is going wrong here. I’ll investigate.
mh
(marc hoffman)
December 11, 2019, 8:44pm
5
Yep, I know whats going on; this will need a more elaborate fix tomorrow. Workaround for now: add the NuGtet reference to the other project explicitly, and it compile ok. My apologies.
Thanks, logged as bugs://83641
bugs://83641 got closed with status fixed.
mh
(marc hoffman)
December 12, 2019, 12:58pm
9
Fixed, I’ll send you a new build when one is done.