We want users of the Rebuild library to be able to diagnose rebuild failures, e.g. by diffing the outputs of mdv or ildasm. We don't want stuff that does file I/O to be included in the library, but rather would prefer to have some methods which would for example visualize a PE or PDB image via various tools, allow you to consume those visualizations as strings, and then either:
- write them to disk in the BuildValidator scenario, or
- pass them through a diff tool and write them to the test output in the unit test scenario.
We would also prefer to avoid the ildasm dependency in the library, because it requires file I/O and spawning subprocesses, so would like to look at whether just mdv would be adequate. For example, can we get the same amount of info that we currently get from ildasm by using Microsoft.Metadata.Tools.ILVisualizer? @tmat
We want users of the Rebuild library to be able to diagnose rebuild failures, e.g. by diffing the outputs of mdv or ildasm. We don't want stuff that does file I/O to be included in the library, but rather would prefer to have some methods which would for example visualize a PE or PDB image via various tools, allow you to consume those visualizations as strings, and then either:
We would also prefer to avoid the ildasm dependency in the library, because it requires file I/O and spawning subprocesses, so would like to look at whether just mdv would be adequate. For example, can we get the same amount of info that we currently get from ildasm by using
Microsoft.Metadata.Tools.ILVisualizer? @tmat