dll security
-
hello friends!! I have made a library for my c# project by combining 3 libraries (using ilmerge). I wanted to know, is it possible for someone to decompile my new library or view the code? if yes, how do i protect it? or is there any other way of merging the library with my project?
-
hello friends!! I have made a library for my c# project by combining 3 libraries (using ilmerge). I wanted to know, is it possible for someone to decompile my new library or view the code? if yes, how do i protect it? or is there any other way of merging the library with my project?
Use Reflector[^] to see the result. Normally a dll can be protected by Obfuscation.Dotfuscator is a Visual Studio Tool using for obfuscation. :)
Arun Jacob http://codepronet.blogspot.com/
-
Use Reflector[^] to see the result. Normally a dll can be protected by Obfuscation.Dotfuscator is a Visual Studio Tool using for obfuscation. :)
Arun Jacob http://codepronet.blogspot.com/
dotfuscator is good but it does not encrypt the code. also the project shows an error after being linked with the obfuscated library. obviously because it cannot import the namespaces. how do i correct this? do i need to merge my dll with exe?
-
Use Reflector[^] to see the result. Normally a dll can be protected by Obfuscation.Dotfuscator is a Visual Studio Tool using for obfuscation. :)
Arun Jacob http://codepronet.blogspot.com/
-
Arun Jacob wrote:
Use Reflector[^] to see the result.
Wow, awesome tool! Thanks! I wish there was something like that for my VB6 code that I also have to maintain. Of course, there's no time, money, etc to convert my VB6 code to .NET. :-| ________ Joe
hey pal, googled for u. Check out this link http://vbcity.com/forums/topic.asp?tid=115861[^]
-
hey pal, googled for u. Check out this link http://vbcity.com/forums/topic.asp?tid=115861[^]
amitupadhyay007353543543 wrote:
hey pal, googled for u. Check out this link http://vbcity.com/forums/topic.asp?tid=115861\[^\]
Wow, thanks! My desire is for something that will help me find the dependences and code in my VB6 program. By doing a google on VB6 disassembler, I found a bunch of stuff. I always thought that VB6 compiled directly to assembler/machine code. My VB6 program started out as a simple quick interface to some custom hardware. However, over the years, it's become a huge monstrosity. Since the program was never planned to be huge with many diverse support functions, it's become a bunch of added_on/hacked_on functions. I've started the new version in C#. And, I'm and doing the code and functions properly this time to support a complex GUI. :) However, for a few reasons, I'll still need to support the VB6 program for a few more years. I dread every time I have to go back to VB6 and Visual Studio6. However, as long as I'm getting paid, then it's all good. :) Wow, also, I just realized. I have a proprietary calibration routine in my VB6 code. It's part of the overall code base. Now, I just disable/hide that Windows form in the version of code that goes to our customers. However, it seems a VB6 decompiler can expose that routine. Yikes! That's good to know. From now on, I'll strip out that module when I build a customer code version. By the way, I knew to strip out that proprietary calibration module in my C# customer code version. Until I find/see a very good way to protect that C# code, I'll keep doing that. It would be nice to have just one single C# code base. Thanks again!
-
dotfuscator is good but it does not encrypt the code. also the project shows an error after being linked with the obfuscated library. obviously because it cannot import the namespaces. how do i correct this? do i need to merge my dll with exe?
I think you are using dotfuscator in the Visual studio project Dlls.Instead of that use it for dll's and exe in the BIN folder.ie,in the output directory not in the Visual Studio project. While using dotfuscator browse all of your dlls and also your exe from your build output directory.Otherwise this dll won't work with that exe because of the change in method names and private variable names. :)
Arun Jacob http://codepronet.blogspot.com/
-
I think you are using dotfuscator in the Visual studio project Dlls.Instead of that use it for dll's and exe in the BIN folder.ie,in the output directory not in the Visual Studio project. While using dotfuscator browse all of your dlls and also your exe from your build output directory.Otherwise this dll won't work with that exe because of the change in method names and private variable names. :)
Arun Jacob http://codepronet.blogspot.com/
Thanks arun, I was only importing dll and not the exe Now i get the problem. Thanks again.
-
Thanks arun, I was only importing dll and not the exe Now i get the problem. Thanks again.
Its ok buddy. :-D
Arun Jacob http://codepronet.blogspot.com/