Referenced assemblies need to be relative to project location

[Brian Lewis]

Using absolute paths to different path locations for assembly references means that project files are not compatible on two systems. Find a location to store references - beside the nuget folder

[Brian Lewis]

new folder assemblies sits under the solution root. This is a sibling of the nuget packages folder.

[Brian Lewis]

Softwords libraries will be located in the assemblies folder. Others are either framework or nuget

[Ghislain Hachey]

This is not really working on a fresh clone. The references had to be changed as shown in the attachments. Is this due to version mismatch? Can this be fixed to just work?

[Brian Lewis]

revised - this should finally fix this. References now point either to

..\assemblies - for non-nuget assemblies

or

..\packages - for nuget assemblies

I think this is to be preferred to pointing the reference (a project input) to bin\debug (the project output) which to me feels a bit circular.

When you Build in VS, VS will copy all the compiled outputs of your solution(e.g. pineapples.dll) together with all referenced assemblies to the bin\debug (or bin\release) folder.

[Ghislain Hachey]

I do not get any errors with these changes. I think this can be considered resolved.