Note two things: The IL code might be obfuscted, meaning, you won't
understand it at all without heavy brain activity. Plus, while you can
decompile, it doesn't mean that it is legal to decompile the code.
You can say so, the code might not look the same though, like method
variables, etc they might have different names.
Also there is a process to "obfuscate" the code, the code is transformed and
made more difficult to reverse engineer.
Note two things: The IL code might be obfuscted, meaning, you won't
understand it at all without heavy brain activity. Plus, while you can
decompile, it doesn't mean that it is legal to decompile the code.
Also, you can not generate an exact same assembly, nor an assembly different
by only some code changes. You would need the private key, with wich the
assemblies where strong named
There is a tool called .NET Reflector that can be used to decompile .NET
assemblies. However some assemblies are obfuscated which is the code is made
hard to read and understand. Further more I know from experience that some
of the obfuscators scramble the code in a way that it crashes the reflector
tool so it is not even possible to decompile it.
There is a tool called .NET Reflector that can be used to decompile .NET
assemblies. However some assemblies are obfuscated which is the code is
made hard to read and understand. Further more I know from experience that
some of the obfuscators scramble the code in a way that it crashes the
reflector tool so it is not even possible to decompile it.
Also, you can not generate an exact same assembly, nor an assembly
different by only some code changes. You would need the private key, with
wich the assemblies where strong named
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
