Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present

Hello,

I use paket for many years now and really like it.

However, now I have problems with a nuget package (openssl-native 3.5.x).
This package contains two targets files that are imported into the .vcxproj by paket:

build/openssl-native.targets and build/native/openssl-native.targets

If I add that package directly in VisualStudio, only build/native/openssl-native.targets is imported.
The problem is that build/openssl-native.targets is for dotnet projects and issues an error when imported in the c++ project.

A quick search revealed, that this behavior is not officially documented, but it makes packages that work with the VisualStudio built in NuGet mechanism incompatible with paket.

I think it would make sense that paket behaves the same as VisualStudio.

Thanks
Bernhard

Start by tracing how Paket handles build/openssl-native.targets and build/native/openssl-native.targets when importing NuGet package targets into a .vcxproj. Compare that selection with Visual Studio's behavior using openssl-native 3.5.x; done means the native targets file is selected for C++ projects without breaking applicable imports for other project types.