Geeks With Blogs

News kaleidoscope 1817, lit. "observer of beautiful forms," coined by its inventor, Sir David Brewster (1781-1868), from Gk. kalos "beautiful" + eidos "shape" (see -oid) + -scope, on model of telescope, etc. Figurative meaning "constantly changing pattern" is first attested 1819 in Lord Byron, whose publisher had sent him one.

Kaleidoscope Everything under the sun, ending in .Net



Explore and analyze compiled .NET assemblies, viewing them in C#, Visual Basic, and IL.

Code written in a .NET language like C# is referred to as managed code. That is, it is not compiled into machine-specific instructions. Instead, .NET compiles into MSIL (Microsoft intermediate language). MSIL is a machine-independent instruction set that is compiled at runtime by the .NET CLR (common language runtime). This extra compilation step is the key to .NET's success. Code executes in a protected sandbox, the managed environment of the CLR. It can provide greater security, stability, and it can run on any piece of hardware that the CLR supports, which may someday include non-Microsoft platforms. With executable programs produced by traditional languages, it can be very difficult to analyze the original source code. This can be a good thing when it comes to code protection, but being able to view source can be of tremendous value; for example, when it becomes necessary to analyze logic in a .dll whose source code has been lost. The .NET Reflector Tool provides .NET developers an easy way to analyze .NET assemblies.


Feature list

  • Full support for .NET 1.0, 1.1, 2.0, 3.0, 3.5, and 4.0
  • Decompiles any .NET assembly to C#, VB.NET, and IL
  • Find usages of classes and methods, including virtual method overrides
Technorati Tags: ,
Posted on Sunday, March 28, 2010 5:42 PM | Back to top

Comments on this post: .NET Reflector

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © kaleidoscope | Powered by: