Tomáš Matoušek
Tomáš Matoušek
See https://github.com/dotnet/metadata-tools/blob/555fdc5c22d4bed4a2dd306b528e0c04e1c2ac23/src/mdv/Mdv.cs#L112
I see. You can use MetadataReader.MetadataPointer and MetadataReader.Length to read the data.
What version of the compiler is this compiled with?
(you can ignore the error, btw)
If these binaries were built by an old compiler (pre-Roslyn, that is before VS 2015) it is possible that some of the metadata and debug information is bad. The old...
Re errors: Most of the conversion errors are recoverable. If the converter produces PDB then you're good. The converter skips bad data and continues converting.
It's linked in from a source package published from Roslyn repo. You should be able to step thru and let Source Link fetch the source :) It is possible that...
@CyrusNajmabadi Msbuild targets pass all dlls in the analyzer package to the compiler as /analyzer command line params. AnalyzerAssemblyLoader then loads all these dlls. The loader could definitely check whether...
> This is also a regression in functionality. This error today catches developers who are constructing incorrect NuPkg files. Or packaging up DLLs that are meant to be managed but...