Transitive dependencies from PackageReferences are not investigated/signed about strongnamesigner HOT 3 CLOSED

This should be supported and should work because for each referenced assembly the entire dependency tree is traversed and all unsigned references will get signed and their references changed in the parent.

Thanks for the example code, will reproduce this and see if it can be fixed. I think your mention of "metepackage" might be the root cause because there is not direct reference to an assembly to start traversing from.

from strongnamesigner.

@brutaldev doesn't the code exclude any references coming from nuget packages?
see

from strongnamesigner.

technically I believe that these lines would also exclude NuGet references. This seems like the wrong approach as you likely want any unsigned references (particularly NuGet references) to also be signed.

from strongnamesigner.