Proposal: Integrate ILDasm Directly into .NET SDK for Linux Distributions

[dariogriffo]

Propose to include the IL Disassembler (ILDasm) directly within the .NET SDK for Linux distributions.

Currently, Linux users need to install ILDasm separately via a NuGet package [runtime.linux-x64.Microsoft.NETCore.ILDAsm]. Bundling it with the SDK would make this essential tool readily available for developers.

ILDasm is a vital tool, letting us inspect the Intermediate Language (IL) of assemblies. On Linux, this is especially helpful for:

• Debugging & Diagnostics: Quickly understanding how code translates to IL helps fix bugs and performance issues.
• Learning & Education: It's a great way for new .NET developers on Linux to understand how things work under the hood.

Benefits

• Better Developer Experience: Instant access to a key diagnostic tool on Linux.
• Less Setup Friction: Reduces an extra step, for linux users who want to get started with .NET
• Increased Productivity: Faster debugging and analysis for Linux-targeted apps.

Things to Consider

• Maintenance: The .NET SDK team would handle its distribution, potentially simplifying updates for Linux users.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT
See info in area-owners.md if you want to be subscribed.

[huoyaoyuan]

This is not specific to Linux. The ildasm from .NET Framework SDK on Windows is outdated and doesn't understand new constructs.

[dariogriffo]

This is not specific to Linux. The ildasm from .NET Framework SDK on Windows is outdated and doesn't understand new constructs.

Probably both can be addressed together, but as of today the linux sdk does not have the ildasm at all

[reflectronic]

For the overwhelming majority of .NET developers who don't need these tools, putting ilasm and ildasm into the SDK directly is wasted disk space.

Publishing the Microsoft ilasm and ildasm as .NET tools (#13823) is a less complicated way of making them accessible. It would require some work in the SDK, since .NET tools currently must be .NET programs, and ilasm and ildasm are written in C++. But, it seems like they are planning to lift this limitation (dotnet/sdk#40931).

[Washi1337]

I agree ilasm/ildasm are tools that can be incredibly useful. However, as someone that mains Linux and has worked for many years on a daily basis with .NET binaries on many levels of abstraction (from raw PE to .NET metadata and CIL), I don't think they have been vital for my developer's workflow. While I acknowledge my experiences are purely anecdotal, I hardly ever use or need them and I would guess the average C# developer cares even less about viewing their CIL. In the rare event that I do need something like ildasm, there are options available in dotnet tool or third parties like ILSpy / CSharpRepl / sharplab / godbolt.

An updated .NET tool installable via dotnet tool install would be nice to have though (the current one under the name dotnet-ildasm afaik is not maintained by MS / the dotnet team).

[amanasifkhalid]

I agree with @reflectronic's points. @dariogriffo would having a .NET tool be a sufficient improvement over your current workflow?

[dariogriffo]

I agree with @reflectronic's points. @dariogriffo would having a .NET tool be a sufficient improvement over your current workflow?

I think a dotnet tool should suffice, it is important then to make sure this comes as first result on searches and in the docs.
Since at the moment there is non official tool suggested when doing Google search or in any LLM