problem in creating dll
-
create dll whose code cannot be decoded by reflector Anuj Kamthan Software Developer Solversa Technologies, Pune - 411007, India. http://www.solversa.com
-
create dll whose code cannot be decoded by reflector Anuj Kamthan Software Developer Solversa Technologies, Pune - 411007, India. http://www.solversa.com
use C++ Christian Graus - Microsoft MVP - C++
-
create dll whose code cannot be decoded by reflector Anuj Kamthan Software Developer Solversa Technologies, Pune - 411007, India. http://www.solversa.com
Christian's right. Any of the Managed Languages, C#, VB.NET, Managed C++, ..., can all be decoded using Reflector. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
Christian's right. Any of the Managed Languages, C#, VB.NET, Managed C++, ..., can all be decoded using Reflector. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
Not 100% true. Some obfuscators generate code that Reflector just refuses to work with. But in general every managed dll can be decompiled to IL easily (reading and understanding IL is another topic :)).
-
Not 100% true. Some obfuscators generate code that Reflector just refuses to work with. But in general every managed dll can be decompiled to IL easily (reading and understanding IL is another topic :)).
Robert Rohde wrote:
Some obfuscators generate code that Reflector just refuses to work with.
That's why those are also to be avoided. If Reflector can't look into the assembly, neither can Reflection, which some classes in the .NET Framework absolutely rely on to work. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
create dll whose code cannot be decoded by reflector Anuj Kamthan Software Developer Solversa Technologies, Pune - 411007, India. http://www.solversa.com
From what I have read, all managed modules contain Metadata which the CLR uses to execute the managed module. It is this Metadata which keeps information about the whole Managed Module. Also , reflection uses this metadata to dig out info about the methods in a managed module or assembly. And the most important part, MetaData is not Optional. It has to be there. So, it is impossible to create an assembly in .NET which reflection cannot access. Because, if reflection cannot access the assembly's metadata, even the CLR will not be able to execute it. Hope this helps. :) --- With best regards, A Manchester United Fan The Genius of a true fool is that he can mess up a foolproof plan!