AsmSpy: Your Next Must-Have Tool If You Write in C#, VB, or F#
-
Identifying the source of a build warning,
MSB3276
, about conflicting versions of an assembly that I signed with a strong name led to the discovery of an incredibly useful little tool called AsmSpy. See [https://lnkd.in/eMFbuBT\](https://github.com/mikehadlow/AsmSpy) for details, including a link to its Chocolatey package. Though this use case just scratched the surface of its capabilities, I can safely say that I wish that I'd known about it long ago. Generating its most basic report for the debug output directory led quickly to the identity of the conflict, along with the realization that it is inconsequential in this instance, since the conflicting assembly is present only to satisfy a binding to another assembly that never calls into the conflicting assembly in this instance. Even if it did, the new assembly is fully backward compatible.David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting