Followup question about VB.NETs weakness when it somes to protecting the algorithms of the primary code structure
This is a followup question concerning need for "obfuscation" of the code because someone can 'easily' get into and look at the primary code algorithms.
My application deals with highly classified encryption of data and if VB.NET opens up to the whole world what the algorithm is then there is a great problem.
This seems like a VERY GREAT WEAKNESS. I remember now that a few years ago I had decided that this problem was so serious that it kept me from converting to VB.NET. I thought by now that MS would have done something to fix it. Apprently not.
Has anyone run into this problem and does anyone have some sort of solution.