Re: Obfuscation & unit testing

Michael Reppy wrote:
> Given the relatively easy decompiling of .Net assemblies, we have  
> some interest in applying obfustication to our commercially released  
> assemblies using a product like Dotfuscator.  I'm just poking around  
> at the issues and whatnot involved, but it seems like obfuscation and  
> unit testing are somewhat orthogonal to each other.  I was just  
> wondering what others in the community had done or if there was more  
> info.  Sourceforge wouldn't let me search the archives of the mailing  
> list and I couldn't find much of anything on Google.

Hi Mikey,

Typically obsfucation is done just before the product releases, after 
the unit testing has been done. Personally, my job involved flying 
onsite to customers when systems go wrong, and debugging third-party 
systems, and obsfucation ends up just delaying us getting the systems 
online. I curse at SharePoint everytime we have to dig into it (yes, 
aa() is calling into b() and it's call to zhfrtt() is taking 38 seconds).

I guess the question is, are you looking to run your unit tests after 
obsfucation, or use obsfucated binaries?

-- 
Cory Foy
http://www.cornetdesign.com


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/