How to view source code of dll files?
+9
A:
The process of going from dll to Source Code is known as decompilation. It is a technology specific to the source language. Can you give us more information on the source language so we can point you to a given technology?
EDIT Update
If C# is the language of choice then the best way to see the source is using Reflector.exe. Note this will not give you back the 100% original source. It is instead an estimation of what the original source was. It can and will produce in accurate output in certain circumstances.
JaredPar
2010-01-30 17:51:40
i use c# dll in VS2008
S.Mehdi
2010-01-30 17:57:52
@S.Mehdi, updated my answer
JaredPar
2010-01-30 18:02:09
@JaredPar thanks, I give vote for you.
S.Mehdi
2010-01-30 18:11:50
where is Reflector.exe?
S.Mehdi
2010-01-30 18:18:45
@S.Mehdi - Red Gate's .NET Reflector http://www.red-gate.com/products/reflector/
Carlos Gutiérrez
2010-01-30 18:30:43
A:
The same way with any other compiled binary.
You either look at the original source, or you use a decompiler.
Joe
2010-01-30 17:52:09
+1
A:
Maybe use .NET Reflector or Introspector but as @JaredPar said depends on what technology
David
2010-01-30 17:53:19
+16
A:
You can make hamburgers with a cow, but you can't make a cow with hamburgers.
Carlos Gutiérrez
2010-01-30 18:00:54
@DMKing - FWIW the question wasn't tagged C# when posted, and I sent S.Mehdi the link to .NET Reflector in the comments of the next answer.
Carlos Gutiérrez
2010-02-02 19:50:39
@DMKing: It is funny. It may not be useful, but it's accurate in many cases. Nor can the Universe make everybody happy here: there's people who want to see the source code, and people who want to hide it.
David Thornley
2010-02-02 20:32:56
+1
A:
Since you've said you're using C#.Net then you can use .NET Reflector to decompile the DLL into, for example, C# code. As others have said, you will get a fair representation of the original code, but probably not the exact original C# code.
There is an exception to this - some companies apply an obfuscator like Salamander .NET Obfuscator to their assemblies before shipping them. The result of this process is that the decompiled code is difficult to comprehend than if the obfuscator had not been used. Some companies go as far as encrypting assemblies. Obfuscation and encryption protect intellectual property from casual attack but can not prevent a significant, well-crafted reverse-engineering effort. Given that reality, not all companies even go to the effort of obfuscation, much less encryption.
You don't say where the the dlls came from, but if you bought them, Reflector will not help you much if the vendor doesn't want you looking inside. And finally, keep in mind that if you purchased the software, decompiling it (whether or not the dlls are obfuscated) may be in violation of the software license agreement.
JeffH
2010-02-02 20:27:02