.Net Obfuscation

VS.NET 2003 ships with an obfuscator. Other than that, I believe there are both commercial and free MSIL obfuscators out there.

--
AnkhSVN - A Visual Studio .NET Addin for the Subversion version control system.
[Project site] [Blog] [RSS] [Browse the source] [IRC channel]

"VS.NET 2003 ships with an obfuscator"

Does that affect performance?

I think everyone who is intrested in programming games or other speed of execution programs in C# or .NET in general needs to consider running their final code through an Obfuscation process.

While you do gain the benefit of making it harder for someone to read your code if they de-compile, you also speed up execution.

Theres a number of articles on it to prove this. Also its not hard to actually see for yourself.

Main reasons are that some code can be cut(dead-end and dead code)

also variable names take cache space... so a var named LONGLONGNAME takes more room than A.

quote:

---

Original post by Abbacabba also variable names take cache space... so a var named LONGLONGNAME takes more room than A.

---

Uhm, there are no variable names around at runtime. Local variables aren''t even present in the IL. At best you can hope to lower the JIT time slightly.

try this : http://www.remotesoft.com/salamander/

You should never let your fears become the boundaries of your dreams.

quote:

---

Original post by Anonymous Poster
It is not ''that'' hard to read the spaghetti code it produces. Albeit I would think you need to come from a spaghetti coding background (like me) cbm vic20 -> c64 -> amiga -> pc. Without the scene background I would imagine most have trouble reading it ;-) *just have a look on the samples included in the manual for the bulked obfuscator to see for yourself*

---

teh juarez

James Simmons
MindEngine Development
http://medev.sourceforge.net