On 11/06/2006, at 12:33 PM, Bryan Lund wrote:
I know that we've held of releasing a number of new classes and controls (and a few updates) until it's fixed. Otherwise we may need to move to a system where we don't provide the classes themselves for evaluation by a potential developer customer... but instead just make built demo apps available ...
I've been trying to work out the business case for a source code obfuscation product and how it can achieve its technical goals at the same time as allowing someone to release a demo of a library.
The more of your interface you expose, the less obfuscation can take place, although some of the techniques I have in mind would still work.
If you're selling something fairly monolithic, like say a report- writer that is customised "around the edges" then that is a good candidate.
If you just want to encrypt a couple of key classes but have the user able to see the rest of a framework, I don't think there's a realistic solution.
Andy _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
