You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ILSupport is an extension for VisualStudio providing... IL support. As far as I know, it's the only IL syntax classifier, and also provides project templates. The use case here is obvious, as verification should be done as part of the build process.
I happen to do language R&D, and there's an obvious use case there as well, in making sure I've got valid IL coming out of a compiler.
Would it make more sense to move the sources into the Arcade repository which allows easier packaging and serves as a central place for other repositories to consume assets?
ilverify is in the same category as ilasm or ildasm. It is a generally applicable tool, not tied to .NET product engineering infrastructure. .NET Framework SDK includes equivalent tool called peverify. ilverify is the replacement for peverify.
Also, 90% of the ilverify code is shared with other components in CoreCLR. If we were to build it somewhere else, we would need to setup a source mirroring for this.
Activity
jkotas commentedon Dec 9, 2019
Use case: dotnet/corert#7905 (comment)
Entomy commentedon Dec 23, 2019
As mentioned in dotnet/corert#7923, there's a use case for ILVerify in ILSupport and demand.
ILSupport is an extension for VisualStudio providing... IL support. As far as I know, it's the only IL syntax classifier, and also provides project templates. The use case here is obvious, as verification should be done as part of the build process.
I happen to do language R&D, and there's an obvious use case there as well, in making sure I've got valid IL coming out of a compiler.
am11 commentedon Feb 4, 2020
Another use-case - dotnet/roslyn#41166 (comment) - is to unit test compiler's output in roslyn repo against netcoreapp: https://github.com/dotnet/roslyn/blob/2ed60699f9961a451f60d560da8bd4788c0182fc/src/Test/Utilities/Portable/Platform/CoreClr/CoreCLRRuntimeEnvironment.cs#L104-L114.
GSPP commentedon Feb 23, 2020
Another use case is verifying custom generated DLLs as a debugging aid. Invalid IL can be hard to detect and diagnose from just execution alone.
ViktorHofer commentedon May 29, 2020
Would it make more sense to move the sources into the Arcade repository which allows easier packaging and serves as a central place for other repositories to consume assets?
jkotas commentedon May 29, 2020
ilverify is in the same category as ilasm or ildasm. It is a generally applicable tool, not tied to .NET product engineering infrastructure. .NET Framework SDK includes equivalent tool called peverify. ilverify is the replacement for peverify.
Also, 90% of the ilverify code is shared with other components in CoreCLR. If we were to build it somewhere else, we would need to setup a source mirroring for this.
ViktorHofer commentedon May 29, 2020
I see, then it makes sense to live in dotnet/runtime. Thanks for clarifying.
BruceForstall commentedon Jun 3, 2020
@agocke @jkotas After #35038, is this complete (can be closed)?
jkotas commentedon Jun 3, 2020
Yes, this can be closed. I have verified that the package is produced by the official build.