MSIL

[Aaron]

I know when you compile a .NET app c# or vb the code is converted to MSIL. I
was just wondering is it 100% reversible? If so, does that mean someone can
steal all your source code just by decopiling the dll or exe?

Aaron

[Peter Rilling]

It will never be 100% reversible since each compiler may perform different
optimizations and therefore the original high language source cannot be
determined, but in general there are tool which will decompile MSIL code.
There are tools that will allow you to obfuscate the compiled code to make
it more difficult to know what you code is doing.

"Aaron" <ku*****@yahoo.com> wrote in message
news:ur**************@TK2MSFTNGP11.phx.gbl...

I know when you compile a .NET app c# or vb the code is converted to MSIL. I was just wondering is it 100% reversible? If so, does that mean someone can steal all your source code just by decopiling the dll or exe?

Aaron

[Nicholas Paldino [.NET/C# MVP]]

Aaron,

Well, it won't be reversible to the point where you can see the variable
names that you used, but it can be reversed to a great degree. Check out
Reflector by Lutz Roeder for a good example of what is possible.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Aaron" <ku*****@yahoo.com> wrote in message
news:ur**************@TK2MSFTNGP11.phx.gbl...

I know when you compile a .NET app c# or vb the code is converted to MSIL. I was just wondering is it 100% reversible? If so, does that mean someone can steal all your source code just by decopiling the dll or exe?

Aaron

[Jonathan Pierce]

The local variable names are available in the pdb file if you have
access to it. Our Decompiler.NET product generates code that looks
almost identitical to your original source code including local
variable names when you have the symbol file present with the DLL. You
can download and try it out for FREE from
http://www.junglecreatures.com/

Jonathan Pierce
President
Jungle Creatures, Inc.
http://www.junglecreatures.com/
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:<en**************@TK2MSFTNGP12.phx.gbl>...

Aaron,

Well, it won't be reversible to the point where you can see the variable
names that you used, but it can be reversed to a great degree. Check out
Reflector by Lutz Roeder for a good example of what is possible.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Aaron" <ku*****@yahoo.com> wrote in message
news:ur**************@TK2MSFTNGP11.phx.gbl...

I know when you compile a .NET app c# or vb the code is converted to MSIL.

I

was just wondering is it 100% reversible? If so, does that mean someone

can

steal all your source code just by decopiling the dll or exe?

Aaron

[Alan Morgan]

thanks nicholas. i've just started using Reflector and it works really nice
:-). unfortunately Reflector itself does create files but this add-in does:
http://www.denisbauer.com/NETTools/F...assembler.aspx

jonathan, I tried your tool but PDB file option did not work. how do i find
PDB files? also, to my big disappointment I noticed that your tool is not
free as you mentioned :-(. it wrote strange messages about buying commercial
version in most of the decompiled files and the code does not compile as it
says.
"Jonathan Pierce" <jp*****@nyc.rr.com> wrote in message
llnews:3d**************************@posting.google .com...

The local variable names are available in the pdb file if you have
access to it. Our Decompiler.NET product generates code that looks
almost identitical to your original source code including local
variable names when you have the symbol file present with the DLL. You
can download and try it out for FREE from
http://www.junglecreatures.com/

Jonathan Pierce
President
Jungle Creatures, Inc.
http://www.junglecreatures.com/
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote

in message news:<en**************@TK2MSFTNGP12.phx.gbl>...

Aaron,

Well, it won't be reversible to the point where you can see the variable names that you used, but it can be reversed to a great degree. Check out Reflector by Lutz Roeder for a good example of what is possible.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Aaron" <ku*****@yahoo.com> wrote in message
news:ur**************@TK2MSFTNGP11.phx.gbl...

I know when you compile a .NET app c# or vb the code is converted to

MSIL. I

was just wondering is it 100% reversible? If so, does that mean

someone can

steal all your source code just by decopiling the dll or exe?

Aaron

[Jonathan Pierce]

Hi Alan,

The pdb file is created when you compile your assembly with debugging
information. It will be created in your bin directory alongside your
dll or exe and is needed to debug assemblies at the source code level.
Our Decompiler.NET product will read these symbol files if present in
order to retain your local variable names in the decompiled code.
Local variable names are not present in the assembly file itself, so
Decompiler.NET generates local variable names based on their type if
the symbol file is not available with the assembly.

The Decompiler.NET product is not free but the evaluation version can
be downloaded for free in order for you to evaluate the product's
capabilities.

The product is priced very low considering that it produces higher
level and more accurate code than the competitors, we provide better
support with free updates, and the product includes full obfuscation
capabilities.

Please make sure that you check often for updated versions of the
product since they are posted often to the web site.

The eval version should still produce code that compiles 100% since it
generates stubs for methods that are being disabled and returns value
values and out parameter values.

If you have an example of output that does not compile, please send it
to me at su*****@junglecreatures.com and I'll address the issue
immediately.

I look forward to your experience evaluating the product.

Jonathan

"Alan Morgan" <no*****@no.spam.com> wrote in message news:<#k**************@TK2MSFTNGP12.phx.gbl>...

thanks nicholas. i've just started using Reflector and it works really nice
:-). unfortunately Reflector itself does create files but this add-in does:
http://www.denisbauer.com/NETTools/F...assembler.aspx

jonathan, I tried your tool but PDB file option did not work. how do i find
PDB files? also, to my big disappointment I noticed that your tool is not
free as you mentioned :-(. it wrote strange messages about buying commercial
version in most of the decompiled files and the code does not compile as it
says.
"Jonathan Pierce" <jp*****@nyc.rr.com> wrote in message
llnews:3d**************************@posting.google .com...

The local variable names are available in the pdb file if you have
access to it. Our Decompiler.NET product generates code that looks
almost identitical to your original source code including local
variable names when you have the symbol file present with the DLL. You
can download and try it out for FREE from
http://www.junglecreatures.com/

Jonathan Pierce
President
Jungle Creatures, Inc.
http://www.junglecreatures.com/
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote

in message news:<en**************@TK2MSFTNGP12.phx.gbl>...

Aaron,

Well, it won't be reversible to the point where you can see the variable names that you used, but it can be reversed to a great degree. Check out Reflector by Lutz Roeder for a good example of what is possible.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Aaron" <ku*****@yahoo.com> wrote in message
news:ur**************@TK2MSFTNGP11.phx.gbl...
> I know when you compile a .NET app c# or vb the code is converted to MSIL.
I > was just wondering is it 100% reversible? If so, does that mean someone
can > steal all your source code just by decopiling the dll or exe?
>
> Aaron
>
>

[Alan Morgan]

> The pdb file is created when you compile your assembly with debugging

information. It will be created in your bin directory alongside your
dll or exe and is needed to debug assemblies at the source code level.
i can't find any PDB files. sucks.
The product is priced very low considering that it produces higher
it is bad that you reverse-engineer full source code and make money with it
:-(
The eval version should still produce code that compiles 100% since it
generates stubs for methods that are being disabled and returns value
values and out parameter values.

the compiler was reporting error with arrays not being valid. unfortunately
i already deleted assembly and uninstalled decompiler.net so i can't tell
what the error was.

[Jonathan Pierce]

"Alan Morgan" <no*****@no.spam.com> wrote in message news:<O8**************@TK2MSFTNGP11.phx.gbl>...

The pdb file is created when you compile your assembly with debugging
information. It will be created in your bin directory alongside your
dll or exe and is needed to debug assemblies at the source code level.
i can't find any PDB files. sucks.

Are you compiling your own code, or trying to decompile someone elses
assembly? People do not normally ship debugging symbol files with the
release version of their product, but you will get a pdb file if you
compile with debugging.
it is bad that you reverse-engineer full source code and make money with it
:-(
Why? There are may uses for the tool, including obfuscating your own
code, optimizing your code, translating your code across languages,
learning about other implementations, etc. The product serves a
valuable need not filled by the Microsoft provided tools. Believe me,
I have spent over two years developing the product and the income
derived from it does not justify the development effort. I priced it
low intentionally to make it accessible to small developers who need
it, and to encourage customers to consider the other products that we
developing that have not yet been released.
the compiler was reporting error with arrays not being valid. unfortunately
i already deleted assembly and uninstalled decompiler.net so i can't tell
what the error was.

Why did you delete your test assembly? If you send it to me or tell me
where you got it, I'll be able to reproduce your error. Did you
compile it yourself? What compiler or language was used? Was the
assembly already obfuscated? Obfuscators often deliberately attempt to
prevent code from decompiling with various tricks and overloading
techniques.

Jonathan

[Jonathan Pierce]

Alan,

I was able to figure out the issue from your mention of arrays. Thanks
for reporting this. Decompiler.NET generates empty default values for
return values and out parameters in methods where the eval version is
replacing the method body with an empty stub. This allows the stub
methods to still compile correctly. There was a bug that didn't
generate a valid array value for these returned stub method values, so
you were getting errors on stub methods that returned arrays. This has
been fixed in the latest posted version. Please take another look at
the product when you have time and report any issues that you
encounter. We always fix any bugs reported to us as soon as we can
reproduce them and post updated versions immediately. In this case,
you provided enough information to reproduce the issue and the fix was
trivial. We fully test the application each time we ship it but we
don't usually test in evaluation mode so this bug slipped through the
cracks.

Thanks again for reporting it.

Jonathan Pierce
President
Jungle Creatures, Inc.
http://www.junglecreatures.com/
"Alan Morgan" <no*****@no.spam.com> wrote in message news:<O8**************@TK2MSFTNGP11.phx.gbl>...

The pdb file is created when you compile your assembly with debugging
information. It will be created in your bin directory alongside your
dll or exe and is needed to debug assemblies at the source code level.

i can't find any PDB files. sucks.

The product is priced very low considering that it produces higher

it is bad that you reverse-engineer full source code and make money with it
:-(

The eval version should still produce code that compiles 100% since it
generates stubs for methods that are being disabled and returns value
values and out parameter values.

the compiler was reporting error with arrays not being valid. unfortunately
i already deleted assembly and uninstalled decompiler.net so i can't tell
what the error was.