Big Posted October 23, 2003 Posted October 23, 2003 Hi, Is their anybody who knows if their exists a decompiler for dll from VB?? Quote
AndreRyan Posted October 23, 2003 Posted October 23, 2003 You can decompile any managed application using ILDASM: C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\Bin\ildasm.exe If you don't own the rights to the software then this is illegal. ILDASM returns MSIL (Microsoft Intermediate Language) not actual VB or C# code though it can be translated into either. Obfuscators effectively prevent reading of the code by making it impossible to understand effectively. Quote .Net allows software to be written for any version of Windows and not break like Unmanaged applications unless using Unmanaged procedures like APIs. If your program uses large amounts of memory but releases it when something else needs it, then what's the problem?
pjv Posted October 23, 2003 Posted October 23, 2003 Reflector (search for it on google) will allow you to view inside assemblies (dll or exe) and decompile to c# or vb (or IL if you really want). The code does not recompile.. but you can look. I'm uncertain as to whether or not it's legal.. surely if you own the program (i.e. you paid for it) then you can do what you like with it (from the comfort of your own home, without involving others or selling a competitive product, etc)? Quote
AndreRyan Posted October 23, 2003 Posted October 23, 2003 Part of the EULA in every commercial program(unless it was not thought through properly) bans the user from, in anyway, decompiling/disassembling an application/library to view its contents. The reason this is prohibited is because you could come up with some wonderful compression algorythm and someone could decompile it and steal it unless you patent it which still doesn't apply in some countries. But like I said, an obfuscator makes code almost impossible to understand and the really good ones can format the code so it can't be reassembled, at least easily. Quote .Net allows software to be written for any version of Windows and not break like Unmanaged applications unless using Unmanaged procedures like APIs. If your program uses large amounts of memory but releases it when something else needs it, then what's the problem?
Big Posted October 23, 2003 Author Posted October 23, 2003 Thx guys, and it is an old dll from myself but i lost the code. And now i can find it again. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.