Obfuscating with Dotfuscator

[Y S]

Hi,

We are t-r-y-i-n-g to use the Obfuscator accompanying DevStudio.

Before we can utilize it, we need to know what it does when you have more
than a single project, both sharing a common library. Assuming that *both*
are *fully* obfuscated, then what happens when one of them is being built?
will the obfuscation process of the second one obfuscate the common library
in the same manner it did when obfuscated the first project, or will it
create a different version? If the obfuscation process is non-deterministic
(meaning, if it is run consequently, you get different results, i.e.
different obfuscated names), then this tool is worthless for large
projects... when you obfuscate a project, you'd have to obfuscate all other
projects using the same common library (and then ship them all again...). Of
course, a naive solution would be to leave public members out of the
obfuscation process, but what about *protected* members? it seems as if
Dotfuscator treats these like they are private (which breaks inheritance of
objects from a shared library, in the aforementioned scenario).

Thanks for any suggestion

YS

[remotesoft]

Wonder if you want to try our obfuscator, which I think is much easy to use
than Dotfuscator. We also offer a protector that provides the best
protection on the market.

You can download a trial version here:

http://www.remotesoft.com/salamander.../download.html
http://www.remotesoft.com/salamander/protector.html

Huihong

"Y S" <ya***********@hotmail.com> wrote in message
news:eY**************@TK2MSFTNGP11.phx.gbl...

Hi,

We are t-r-y-i-n-g to use the Obfuscator accompanying DevStudio.

Before we can utilize it, we need to know what it does when you have more
than a single project, both sharing a common library. Assuming that *both*
are *fully* obfuscated, then what happens when one of them is being built?
will the obfuscation process of the second one obfuscate the common library in the same manner it did when obfuscated the first project, or will it
create a different version? If the obfuscation process is non-deterministic (meaning, if it is run consequently, you get different results, i.e.
different obfuscated names), then this tool is worthless for large
projects... when you obfuscate a project, you'd have to obfuscate all other projects using the same common library (and then ship them all again...). Of course, a naive solution would be to leave public members out of the
obfuscation process, but what about *protected* members? it seems as if
Dotfuscator treats these like they are private (which breaks inheritance of objects from a shared library, in the aforementioned scenario).

Thanks for any suggestion

YS