google-cloud-dotnet VS ILSpy

There are several libraries in dotnet for google apis which cover most of the GCP usage, but we will focus in Google Cloud Functions for dotnet.

Recently I had to debug Google's Storage SDK. Apparently the natural way to do it in today's OSS world is to simply clone the repo, build it locally and debug what you want. You wish! The codebase is in my opinion so convoluted and mostly autogenerated, that it's completely useless for a programmer and completely pointless to start understanding it. In addition to that, the code simply doesn't build locally. One probably has to employ some internal Google tools and scripts to do that (maybe Google developers never heard of .NET/C#?) maybe in a similar way you build Google Chrome. It also could be a pay pack for someone asking to opensource the code? This coding style is another way of encryption - yeah you can read it but it's garbage and so is useless.

First, go grab this: https://github.com/icsharpcode/ILSpy. It's a decompiler that will break Rust down. Hope you like C#.

If its a C#/.NET exe you can use ILSpy to get the source code https://github.com/icsharpcode/ILSpy

Well, it might not be exactly what you're asking for, but ILSpy lets you choose what version of C# you wish to decompile an assembly to. This is great for learning how a specific feature used to be coded in C# prior to some new syntax/compiler feature being added.

You will thoroughly enjoy this, then.

I've only used their GUI frontend myself, but ILSpy is also available as a library and command line tool.

As you can see IL code is not exactly human readable, and it's also quite verbose. If you want to have an idea of how your code looks like in IL you can use a decompiler tool such as JustDecompile or ILSpy.

Take a random piece of C# software, run it through ILSpy, and be amazed at the results.