When using multiple FileOnQ imaging libraries in the same downstream project there are naming conflicts with build targets for net48. This is because both FileOnQ.Imaging.Heif and FileOnQ.Imaging.Raw use the same build <Target> name of CopyNativeDlls.
The conflict prevents native assemblies from being copied to the bin directory correctly. This will create a silent error as the build will not fail and the application will have a runtime error.
Description
When using multiple FileOnQ imaging libraries in the same downstream project there are naming conflicts with build targets for net48. This is because both
FileOnQ.Imaging.HeifandFileOnQ.Imaging.Rawuse the same build<Target>name ofCopyNativeDlls.The conflict prevents native assemblies from being copied to the bin directory correctly. This will create a silent error as the build will not fail and the application will have a runtime error.
Proposed Solution
Make the build target names unique