The download is quick and accessible without registration. Who does not like give his/her data out of the hands or who is just too much effort, I recommend IL Spy. However you must register (for free) on Teleriks website to use the software. My personal favorite is „Just Decompile“ from Telerik. The differences are more in the simplicity of use and their visual appearance. NET decompilers: ILSpy (by SharpDevelop)Īll four tools worked very well in my tests.
It can be used to effectively convert source code between C# and Visual Basic. It is even possible to cross-navigate related documentation (xmldoc), searching for specific types, members and references. It will pick up the same documentation or comments that are stored in xml files alongside their associated assemblies that are used to drive IntelliSense inside Visual Studio. There is a call tree and inheritance-browser. It can also be used to find assembly dependencies, and even windows DLL dependencies, by using the Analyzer option. NET Reflector can be used to track down performance problems and bugs, browse classes, and maintain or help become familiar with code bases. There are a large number of add-ins for Reflector. NET developers to understand the inner workings of code libraries, to show the differences between two versions of the same assembly, and how the various parts of a CLI application interact with each other. It will show the metadata, resources and XML documentation.NET Reflector can be used by. Reflector also includes a „Call Tree“ that can be used to drill down into intermediate language methods to see what other methods they call. NET, Common Intermediate Language and F# (alpha version).
By default Reflector allows decompilation of CLI assemblies into C#, Visual Basic. It can be used to inspect, navigate, search, analyze, and browse the contents of a CLI component such as an assembly and translates the binary information to a human-readable form. NET Reflector was the first CLI assembly browser. All the other can read on below the following paragraphs. The following parenthesis is for those who don’t know what’s meant by the term. Former I frequently used this tool, but since it costs money and there are good and useful free alternatives, this is no longer between my fingers.
NET development was in a professional context for my employer, so it's not like I couldn't get the tools due to cost issues, but the massive culture gap left an impression on me.Today I want to briefly highlight a few alternatives to Redgates. NET that go a long way towards explaining why I'm not a. The story just sparked some memories of my time in. It's a bit disappointing, because this mentality seems like it really does a lot to stifle hobbyist exploration of the platform when it's doing cost you $48 in assorted widgets to build the toolset you need to try out an idea.Įdit: I should clarify that I don't think this is a bad thing, and I absolutely feel that Reflector justifies the price tag. Reflector was a shining example of a great free tool in a sea of pay-for dreck, and it's quite sad to see that example die. NET world that everyone in every step of the chain has to make a buck. I don't mind paying for good tools (and I would absolutely class Reflector as one), but there seem(s/ed) to be this very top-down mentality in the. I don't remember the last time I saw the source for an assembly on GitHub et al.
Libraries and tools that I could get for free with C++ or Ruby or Python seemed to all have price tags associated with them in. NET community was that it seemed like everyone wanted their $5, $10, $50 for everything. NET was about six years ago, but my biggest turnoff with the. I'll preface this my saying that the last time I touched.