If NuGet fails to see the dependencies, you can override the behavior by changing the .nuspec file.
Below information is taken from:
.nuspec File Reference for NuGet | Microsoft Docs[
^]
Quote:
To bypass this automatic behavior and explicitly control which files are included in a package, place a <files> element as a child of <package> (and a sibling of <metadata>), identifying each file with a separate <file> element.
Example:
<files>
<file src="bin\Debug\*.dll" target="lib" />
<file src="bin\Debug\*.pdb" target="lib" />
<file src="tools\**\*.*" exclude="**\*.log" />
</files>
I used this to create a NuGet package with both x86 and x64 dll's:
<?xml version="1.0"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
<metadata>
<id>BuildXXXXX</id>
<version>1.0.0</version>
<authors>XXXXX</authors>
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<description>XXXXX 32 amd 64 bits</description>
</metadata>
<files>
<file src="x64\Release\xxxxx.dll" target="lib/net47/x64" />
<file src="x64\Release\xxxxx.pdb" target="lib/net47/x64" />
<file src="x86\Release\xxxxx.dll" target="lib/net47/x86" />
<file src="x86\Release\xxxxx.pdb" target="lib/net47/x86" />
</files>
</package>