[ArkPhaze]

@NiTrOwow - You aren't even using the Win32 function for VB.net and C#, you're using the methods wrapped in the System.Diagnostics.Process class, so why put them in the thread?

I have not wrote those functions. A friend did.
VB.NET is crap for such things and don't know about C#.

VB.NET is the same as C# (and vice versa if you want to word that differently). How is VB.NET crap? It's better than VB6. I have yet to see someone have a good reason for saying VB6 is better than VB.NET (most likely because unfortunately there is none). Less dependencies is not a good reason either, because it's really invalid if people really think about that.

VB.NET is crap same for VB6. If you look from the way i do VB6 is better, because it is a bit harder to crack and not only that. .NET can be decompiled, vb6/vba too but not as nice as .NET

End of story, Delphi, C++, Assembly = the way to go.

And seriously, don't threat me as a fucking newbie.
You guys don't even know me, and how many times do i have to repeat, i'm not a stupid foolish guy.

Fine for you that you found a 1337 fault in my 1366 c/p .NET code.
I DO NOT CARE! This is a fucking easy example or poc or whatever u would like to call it. I did not even dear to look at it i have posted this on another shit forum, and c/p it here too. Because it might be helpful to others?

Not being able to decompile code in the way you can decompile .NET does not make VB6 a better language. It's missing lots of features and is pretty much obsolete as a whole. No polymorphism/inheritance, encapsulation, operation overloading, parameterized constructors, class-level attributes, etc...

If you rely on the idea of decompiling between VB6 and VB.net is the security, then that's poor; anybody who really wants to crack or see what you're application does will do it eventually. There's ways to make compiled VB.net/C# programs harder to read when an attempt is made for decompilation. Assuming that someone doesn't know how to debug properly with IDA or Olly is not going to make your application any better because it can't be reversed as easily as .NET.

Delphi though? Why Delphi? And Assembly? explain your choices.. I'm not insulting you here either, so no need to post with such anger, that's a childish response...

I'd like to see your views instead of only talking about your views. "Harder to crack" is entirely dependent on the programmer who writing the program too, not the language being used in this case. You can toughen up a VB.net program and make it more time consuming to crack than just a straight application written in VB6, I guarantee it.