Pregunta

I have a solution that uses a few portable class libraries and I can't figure out how to fix the default rules that look for certain attributes to be defined on the assembly when the assembly is a portable class library.

For example, the rule Mark assemblies with CLSCompliant

warnif count > 0 from a in Application.Assemblies where 
  !a.HasAttribute("System.CLSCompliantAttribute".AllowNoMatch())
select a

Based on the output it appears that NDepend is looking for the attribute as defined in mscorlib but in a portable class library the attribute is defined in System.Runtime.dll.

Is there a way to change the rule so it handles PCL projects properly?

Note: NDepend version 5.2.1.8320

¿Fue útil?

Solución

This issue has indeed been fixed as of NDepend v5.4.0.

Licenciado bajo: CC-BY-SA con atribución
No afiliado a StackOverflow
scroll top