kinar

ok, firstly, I realise that anything can be reverse engineered. And I realise that I used 2 taboo words in a single post here (security and decompile). However, I currently maintain a couple systems where we dont want to publish our protocol used in our client/server communication. And once again, while I will agree that anyone with a trial of ethereal can figure it out with a bit of work, it is an entirely different subject than if we were to publish it in a word doc on our website. which, as I understand it (and have tested briefly) distributing anything in .NET is essentially doing just that. Anyone with a free copy of reflector can output the entire source of our app. In using VC++, I can "hide" parts of this in unmanaged code but in VB I have not found a way todo the same. And for the last time (in this post) I realise that it is only literally "hiding" it, but that is much better (in our case) than publishing it. kinda like using a condom...Its protection, not a cure as for... I did find a couple of these (remotesoft / thinstall) but unfortunately paying thousands of dollars is not an option. A search for a free (or lowcost) solution did not return any results. I may just have to stick with VS6 for these projects where protection matters. Unless anyone else has some suggestions.

copied from xtremevbtalk.net after I noticed this site Hello, I tried searching on this but was unable to find anything useful I am fairly new to .NET but not at all new to programming (VC++, VB, primarily). The biggest concern I have with .NET is that applications and forms can be decompiled using applications such as Reflector. I know that in VC++ using .NET you can "protect" your code from this so that they are compiled to Native code rather than CLR. Is this also possible with VB? Do I need to write all of my critical code in c++ dlls and link them in? a simple list of "Suggested reading" would be greatly appreciated.