The plot thickens...
Here are all of the copies of SaxonCS.dll
that appear in the build directory.
norm@wynngifu MINGW64 /c/Volumes/Saxonica/src/saxonica/saxondev (saxon11)
$ find . -type f -name SaxonCS.dll -print -exec file {} \;
./build/cs/bin/Release/net5.0/ref/SaxonCS.dll
./build/cs/bin/Release/net5.0/ref/SaxonCS.dll: PE32 executable (console) Intel 80386 Mono/.Net assembly, for MS Windows
./build/cs/bin/Release/net5.0/SaxonCS.dll
./build/cs/bin/Release/net5.0/SaxonCS.dll: PE32 executable (console) Intel 80386 Mono/.Net assembly, for MS Windows
./build/cs/bin/Release/net5.0/win-x64/ref/SaxonCS.dll
./build/cs/bin/Release/net5.0/win-x64/ref/SaxonCS.dll: PE32+ executable (console) x86-64 Mono/.Net assembly, for MS Windows
./build/cs/bin/Release/net5.0/win-x64/SaxonCS.dll
./build/cs/bin/Release/net5.0/win-x64/SaxonCS.dll: PE32+ executable (console) x86-64 Mono/.Net assembly, for MS Windows
./build/cs/obj/Release/net5.0/ref/SaxonCS.dll
./build/cs/obj/Release/net5.0/ref/SaxonCS.dll: PE32 executable (console) Intel 80386 Mono/.Net assembly, for MS Windows
./build/cs/obj/Release/net5.0/SaxonCS.dll
./build/cs/obj/Release/net5.0/SaxonCS.dll: PE32 executable (console) Intel 80386 Mono/.Net assembly, for MS Windows
./build/cs/obj/Release/net5.0/win-x64/ref/SaxonCS.dll
./build/cs/obj/Release/net5.0/win-x64/ref/SaxonCS.dll: PE32+ executable (console) x86-64 Mono/.Net assembly, for MS Windows
./build/cs/obj/Release/net5.0/win-x64/SaxonCS.dll
./build/cs/obj/Release/net5.0/win-x64/SaxonCS.dll: PE32+ executable (console) x86-64 Mono/.Net assembly, for MS Windows
./build/testdrivers/bin/Release/net5.0/SaxonCS.dll
./build/testdrivers/bin/Release/net5.0/SaxonCS.dll: PE32 executable (console) Intel 80386 Mono/.Net assembly, for MS Windows
This is what I find in saxoncs.11.4.0.nupkg
.
./x/lib/net5.0/SaxonCS.dll: PE32+ executable (console) x86-64 Mono/.Net assembly, for MS Windows
So I've managed to build 32 bit DLLs, but the version that's being packaged for nuget is the 64 bit version.
But the 11.3 release DLL is a 32 bit DLL. And I can't immediately see why we got a different release this time.