Thus the reason why we remain using VB6 (the other reason is the insanely
large .net framework). If you don't want your work decompiled (like every
other company selling code for profit), stick with VB6, move to C++
(unmanaged), or I suppose Delphi would also be a good choice in this regard,
although I am not familiar with it (I hear it is nice though). If you
absolutely have to use .NET, pick the best obfuscation tool money can buy,
or, try to keep your project an ASP.net (server-side) project.
- Anthony
"Jobs" wrote:
[color=blue]
>
>
> How to prevent my .NET DLL to be decompiled?
>
> By design .NET embeds rich Meta data inside the executable code using
> MSIL.Any one can easily decompile your DLL back using tools like ILDASM
> ( owned by Microsoft) or Reflector for .NET which is a third party.
> Secondly there are many third party tools which make this decompiling
> process a click away. So any one can easily look in to your assemblies
> and reverse engineer them back in to actual source code and understand
> some real good logic which can make easy to crack your application.
>
> The process by which you can stop this reverse engineering is using
> "obfuscation". It's a technique which will foil the decompilers.
> There are many third parties (XenoCode, Demeanor for .NET) which
> provide .NET obfuscation solution. Microsoft includes one that is
> Dotfuscator Community Edition with Visual Studio.NET.
>
> Full Interview Questions for .NET and SQL Server
>
http://www.geocities.com/dotnetinterviews/
> Help the community to make job search easier mail your questions to
>
jobatyourdoorstep@yahoo.co.in
> Looking for a onsite job mail your resumes at
>
jobatyourdoorstep@yahoo.co.in
>
>[/color]
Interview Questions Feb 20, 2006
