It's quite scary how exact it is too, it requires no effort to read at all.Most people don't realize that .NET compiles to an intermediate language (IL) that is extremely easy to reverse engineer.
Junk code doesn't have to degrade performance does it? The only performance hit that I've read of is encryption, and even that's minor.What do you want it to do then? Insert random ****s of code that do nothing, but degrade performace, so that someone will be less likely to figure out your code?
Well it's better than the decompiled original code but still definitely possible to re-engineer, yes. You can improve it with string encryption and I would imagine with more severe control flow obfuscation. You can also choose to compile it properly I think, but that restricts it to a specific architecture.That isn't as obfuscated as I would have hoped???
I have a £10m pa software team that'd disagree with you.VB.Net does not need obfuscation, as nobody in their right mind would ever want to look at it
Nothing wrong with VB.NET. In fact, if you started .NET developement with VS 2001/2003, the IDE features available for VB were superior to C#. But since 2005 C# has caught up and even passed VB with 2008.