Does Dotfuscator Communit Edition work with CF 2.0? If so, what is
the secret to getting it to work? My VB.NET compiled app works fine.
But after I obfuscate, all I get is an 2 second hourglass on the
device, then nothing. Thanks for any insight you have.

It should work with CF2 as long as you are using the version that comes with
VS2005. I have never got it work work even the latest versions tough.

I recomend looking at other products...

Have you tried Mangler once recommended to me:
http://www.dotnetthis.com/Samples/Mangler.htm

Also see if this link helps, contains lots of usful information and many
alternative products:
http://www.howtoselectguides.com/dotnet/obfuscators/

Simon.

"RxRick" wrote:

> Does Dotfuscator Communit Edition work with CF 2.0? If so, what is
> the secret to getting it to work? My VB.NET compiled app works fine.
> But after I obfuscate, all I get is an 2 second hourglass on the
> device, then nothing. Thanks for any insight you have.
>
>

I've had poor luck with it, plus it's too hamstrung (unable to use it on
signed assemblies at all). We use Xenocode internally.


--
Chris Tacke - Embedded MVP
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--


"RxRick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Does Dotfuscator Communit Edition work with CF 2.0? If so, what is
> the secret to getting it to work? My VB.NET compiled app works fine.
> But after I obfuscate, all I get is an 2 second hourglass on the
> device, then nothing. Thanks for any insight you have.
>

Thanks. I messed up then, because I installed their "highly
recommended" update.

> It should work with CF2 as long as you are using the version that comes with
> VS2005. I have never got it work work even the latest versions though

This is something from a colleage of mine who works with obfuscation ...
evidently it is a known issue w/ dotfuscator and signed assemblies so there
is a documented process to unsign/obfuscate/ and then re-sign.

-arnie

....

Dotfuscator does "unsign" the assembly by default. You can tell it where to
find the key and tell it to auto-re-strongname after it's done but I found
that it didn't always find the key. So we manually re-strong name
everything after obfuscation, via a command in hte BuildConfig script.

This is fairly well documented in Dotfuscator - how to tell it to
auto-re-strongname...


"<ctacke/>" <ctacke[@]opennetcf[dot]com> wrote in message
news:(E-Mail Removed)...
> I've had poor luck with it, plus it's too hamstrung (unable to use it on
> signed assemblies at all). We use Xenocode internally.
>
>
> --
> Chris Tacke - Embedded MVP
> OpenNETCF Consulting
> Managed Code in the Embedded World
> www.opennetcf.com
> --
>
>
> "RxRick" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Does Dotfuscator Communit Edition work with CF 2.0? If so, what is
>> the secret to getting it to work? My VB.NET compiled app works fine.
>> But after I obfuscate, all I get is an 2 second hourglass on the
>> device, then nothing. Thanks for any insight you have.
>>
>
>

[LogicNP]

As an alternative, consider Crypto Obfuscator which supports all versions of the Compact Framework and has many settings for protection and obfuscation of CF assemblies.