Sign In  Sign Up Live-Chat

Aspose.Obfuscator

Last post 06-15-2006, 4:59 PM by ElekTroN. 2 replies.
Sort Posts: Previous Next
  •  05-08-2006, 7:59 AM 47649

    Aspose.Obfuscator

    Hi Aspose,

    It is rather Sad [:(] that you have (had) this Smile [:)] utility: Aspose.Obfuscator which is no further developed - but retired.

    It would have been even Big Smile [:D] if the project where published as an open-source project in a community like sourceforge.net... I'm sure that a lot of people (including me) would gladly administer an open-source project like that.

    vinken

     
  •  05-08-2006, 3:13 PM 47675 in reply to 47649

    Re: Aspose.Obfuscator

    Dear vinken,

    Thank you for considering Aspose.Obfuscator.

    It was discontinued mainly because it was not coded well, at least not at the best practice. So if we open its source code, we're concerned if it will dishonour our brand. If some one like you is willing to polish it before post the source to the general public, open source can be an option. But I would say the workload is huge because I found a single method may have thousands of lines of code. Rewriting such code in an acceptable way may be very time consuming.

    Also I have a question for you. Dotfuscator Community Edition is freely included in Visual Studio 2003/2005. Why would you try to use it instead of Aspose.Obfuscator?  


    Ben Li
    Team Leader, Aspose Sydney Team
    About Us, Contact Us
     
  •  06-15-2006, 4:59 PM 50572 in reply to 47675

    Re: Aspose.Obfuscator

    Hello there,

    I was thinking of posting a similar suggestion to vinken's when I found this post. I can't promise you much but if I could get access to the code with some time I might be able to make it good enough for open source or at the very least I can patch it up a bit and fix some bugs to make it just useful...

    As for Dotfuscator, I've been using it for a while now, but on this specific project, it causes the application to consume 100% cpu resources when some sections of the app are accessed, I can't tell why, but I've spent many hours going through the IL and eventually gave up on it.

    The only problem I've had with yours, is  that is a bit too "rename-happy", for  example if I got a class with these two methods:

    public void method1() { /*do something */ }
    public void method2() { ExternalAssembly.method1(); }

    after obfuscating it would look like:

    public void a() { /* do something */ }
    public void b() { ExternalAssembly.a(); }

    As you can see, the method1() call to the external assembly got renamed to the new name for the local method1(), needless to say this is a big issue, that would be the first thing I'd fix (if it doesn't take rewritting the whole thing) if you allow me, and depending on how the code looks I  might clean it up with time until is good enough to publish..., but if not  at least it'll be useful for something...

     
View as RSS news feed in XML