![]() ![]() There is also a console decompiler and, interestingly, cross-platform PowerShell cmdlets. You can also integrate ILSpy into Visual Studio 2017 or 2019 with this extension. ILSpy has been around for a while and has multiple front-ends, including ones for Linux/Mac/Windows based on Avalonia in the form of AvaloniaSpy. Those tweets got me thinking though that I need to update my options, so I'm trying out ILSpy and dnSpy. Seriously, though, I use ILDasm - the IL Disassembler - simply because it's already installed. I've used ILDasm for years, but it's old and lame and people tease you for using it because they are cruel. You're basically taking this pre-chewed food and taking it out of your mouth and getting a decent idea of what it was originally. You're not looking at the source, you're seeing a backwards projection of the IL as whatever language you want. Sometimes you'll want to just see the structure of classes, methods, etc, and other times you want to see the IL - or a close representation of the original C#/VB/F#, etc. Often you'll come along a DLL that you want to learn more about. ![]() When you get a DLL/Assembly, it's pre-chewed but not full juiced, to mix my metaphors. NET code (C#, VB, F#, etc) compiles (for the most part) into Intermediate Language (IL) and then makes it way to native code usually by Just-in-time (JIT) compilation on the target machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |