Hi,
I need a program which invisible my source code to others. if i covert into .EXE or .DLL, others crack my program by using vbdecomplier.
Mainly i dont allow others to see my program in visual basic 6.
Regards
selva
Printable View
Hi,
I need a program which invisible my source code to others. if i covert into .EXE or .DLL, others crack my program by using vbdecomplier.
Mainly i dont allow others to see my program in visual basic 6.
Regards
selva
Do you even know what you're trying? Doubles store high-precision floating point values, and dates store dates. The two values are incompatible. You can, however, convert dates to strings and vice versa, if the formatting is accurate.
I'm not sure if this is serious thread or not, considering where this is, but I'll go with a serious reply anyway :PBitwise everything stays the same in both dtmDate and dblDate. It is just how they are handled when coercing to strings that makes the real difference.Code:Dim dtmDate As Date, dblDate As Double
dtmDate = Now
Debug.Print dtmDate
dblDate = dtmDate
Debug.Print CDate(dblDate)
It seems the original post has been edited severly since the two posts, because they don't make any sense... :confused:Quote:
Originally Posted by selvakumarmvs
To answer the question:
Visual Studio.NET comes with obfuscator software, which makes it harder to decompile software, but not impossible.
I don't know of any software for Visual Basic 6.
Just coding in visual studio.NET makes it harder already...
(Visual Studio.NET Express Editions are free)
VB6 executables can't be decompiled, only disassembled. And the disassembled code is even less useful than I am. :afrog:
OK, thanks for making the first two posters like idiots, I'm sure they appreciate it. Lastly, a word of advice, there is no such thing as being 100% "Hidden" .... if some one is determined to get to your code, they will find a away. That said, in VB6, once the code is compiled, it's pretty much obfuscated... even with a decompiler, they can't get back to the exact original code.... it'll be a jumble of code that may or may not do what the code did, but, there's not a lot you can do about it. If some one is determined to get to it, they will find a way.Quote:
Originally Posted by selvakumarmvs
-tg
Not sure what this statement means, but it is actually HARDER to decompile VB6 compiled code than .NET compiled code, even if the .NET code is obfuscated.Quote:
Originally Posted by vbcode1980
The truth is, is that if someone wants to reverse engineer your program, they can do it without the source code. Once compiled, the original source code; user space variable and function names and class names will be gone. The logic flow of the code will also likely change to include optimizations, linking code etc.Quote:
Originally Posted by selvakumarmvs
Once you have "decompiled" code it will resemble only a slightly more readable form than the machine code which formed the executable. That said, it is possible to copy a program and its functionality with no source code at all. That means any efforts to obfuscate your code will only deter the amateurs. The pro's, if they want to copy it WILL.
Think of it like a steering wheel lock.
You really need to weigh how long it would take someone to crack your program, versus how long it would take someone who COULD crack your program, to simply write a program to do the same thing your app does.
And this beauty goes straight into my signature. :wave:Quote:
Originally Posted by crptcblade
Moving to VB6 forum.
All I can say is that if your program were copied without proper authorization from you, then that I can say that is stealing. Have the others tried asking your permission for the code or the program? The only solution I can see here is to hide your program...Quote:
Originally Posted by selvakumarmvs
But if they did ask your permission for the program or the code and you rejected them, surely that is being selfish and they're gonna steal your codes away from you...
Just choose from the two options which you will feel better... :wave:
:bigyello:Quote:
Originally Posted by crptcblade
Actually, the guys from VB-Decompiler claim they can get pretty usefull stuff out of your VB application.
http://www.vb-decompiler.org/
Really? Damn, my professor lied to me! :mad:Quote:
Originally Posted by kleinma
If you use a compression tool to compress your .exe with UPX or PECompact for example, then vb-decompiler cant even open the .exe and that also makes your file size very small which is always usefull. : )
There is a software named VB AntiCrack. It will make changes to your project by converting all the strings into an unreadable:) form which we will not be able to see the direct strings when we decompile the program using VBDecompiler..:)
But unfortunately, when I used that thing, my program doesn't worked..:)
Your VB.NET code gets compiled to IL, which is in between human readable syntax, and machine code (IL = Intermediate Language). Many people can read and follow IL code without too much problem. It is still structured in a way that you can read it. Also there are many apps that convert IL back to high level syntax.Quote:
Originally Posted by vbcode1980
VB6 code is compiled natively. Both compile strings directly into the exe, so an app from either language could be opened in something like notepad, and you could find strings like connection strings to a database with password perhaps, etc..
There are some obfuscators for both VB6 and .NET that do things like string encryption. Of course you could also implement your own encryption and not store your sensitive strings in plain text in the application.
Bottom line is it is important to evaluate just how badly you need to protect you app, and in which way. I personally was more worried about creating custom controls and librarys as DLLs to include with my exe, only to know that the DLLs could just be referenced by any other .NET exe and used. I spent my time developing a way to stop that from happening, versus worrying about making my app copy proof. As I said before, unless your app is revolutionary, anyone with the skills to decompile it and steal your code, could probably just write the app (better) themselves in less time...