We have two projects in a solution, A and B. We'd like B to ship the binaries of A when packaged (not referencing it as a standard library dependency). There are existing libs we have seen that ship binaries (https://github.com/valentiniliescu/GraphVizNet/blob/master/GraphVizNet/GraphVizNet.csproj#L25) so, that's not exactly the problem. Where we are stuck is forcing A to build when packaging B, and then retrieving the output path for the binaries of A.
AntonC1/11/2023
it's easier to do with Nuke
AntonC1/11/2023
with MSBuild it's gonna be tough
AntonC1/11/2023
a lot of hacks and headaches
AntonC1/11/2023
with Nuke it should be as straightforward as writing a couple of lines of code
LPeter19971/11/2023
We won't introduce Nuke, very unlikely
AntonC1/11/2023
with MSBuild you're gonna waste a lot of time even if you do manage to pull it off
AntonC1/11/2023
you can't retrieve the output path as far as I know
AntonC1/11/2023
you'll have to hardcode it
AntonC1/11/2023
as for the reference
AntonC1/11/2023
you can add the project A as a build time reference
AntonC1/11/2023
under the condition that some property is set that corresponds to packaging