By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,215 Members | 1,922 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,215 IT Pros & Developers. It's quick & easy.

Dotfuscator Questions

P: n/a
I am using Dotfuscator Community Edition to obfuscate an application for
Pocket PC written in C#. When I made the first pass with Dotfuscator, the
app threw a MissingManifestResourceException. Of course, since the app has
been obfuscated, the only information I got about what caused the error
pointed to resource aq.

The Dotfuscator listing window had WARNINGs about all the forms in my app,
so I excluded them on the 'Rename' tab and reran Dotfuscator. This time the
app came up and ran on the Pocket PC, however, I noticed some custom
controls did not behave correctly. I continued to exclude controls and
methods in the controls until I got the app to run on a device running
Pocket PC 2002. When I tried the app on a device running Pocket PC 2003,
more of the custom controls exhibited problems, so I began the process of
excluding controls and methods again.

The decisions about what to exclude is very hit-and-miss but I am
speculating that to solve the problems, all event handler methods, like
OnPaint(), need to be excluded. Is that correct?

Is there any documentation available about how to decide what to exclude so
Dotfuscator does not break your application?

Thanks,
Tom
Nov 15 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hi Tom,

Thanks for your post. I will ask one who expertise on this issue to look at
and reply this thread.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 15 '05 #2

P: n/a
Perhaps don't bother with dotfuscator? In my opinion, obfuscation is a
silly contention that many people use "because their code is like no-other"
and it's a farse. The obfuscation techniques lead to code that is still
readable but much more difficult to diagnose and debug for the component
designer.

Fact is, when I see obfuscated controls in an Exception stack walk, I as a
fellow developer cannot even begin to try to help you the component designer
to track down why I got the exception.

--
Eric Newton
C#/ASP Application Developer
http://ensoft-software.com/
er**@cc.ensoft-software.com [remove the first "CC."]

"Tom Bean" <tb***@t-a-c.com> wrote in message
news:u4**************@TK2MSFTNGP11.phx.gbl...
I am using Dotfuscator Community Edition to obfuscate an application for
Pocket PC written in C#. When I made the first pass with Dotfuscator, the
app threw a MissingManifestResourceException. Of course, since the app has been obfuscated, the only information I got about what caused the error
pointed to resource aq.

The Dotfuscator listing window had WARNINGs about all the forms in my app,
so I excluded them on the 'Rename' tab and reran Dotfuscator. This time the app came up and ran on the Pocket PC, however, I noticed some custom
controls did not behave correctly. I continued to exclude controls and
methods in the controls until I got the app to run on a device running
Pocket PC 2002. When I tried the app on a device running Pocket PC 2003,
more of the custom controls exhibited problems, so I began the process of
excluding controls and methods again.

The decisions about what to exclude is very hit-and-miss but I am
speculating that to solve the problems, all event handler methods, like
OnPaint(), need to be excluded. Is that correct?

Is there any documentation available about how to decide what to exclude so Dotfuscator does not break your application?

Thanks,
Tom

Nov 15 '05 #3

P: n/a
Hi Tom,

You need to direct this post to the microsoft.public.dotnet.framework.compactframework newsgroup since this is a compact framework
issue and there may be a larger pool of respondants in that newsgroup who may have had and resolved similar issues.
Scot Rose, MCSD
Microsoft Visual Basic Developer Support
Email : sc***@online.microsoft.com <Remove word online. from address>

This posting is provided “AS IS”, with no warranties, and confers no rights.

Get Secure!
http://www.microsoft.com/security
http://www.microsoft.com/protect
--------------------
From: "Tom Bean" <tb***@t-a-c.com>
Subject: Dotfuscator Questions
Date: Tue, 18 Nov 2003 08:08:43 -0600
Lines: 26
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <u4**************@TK2MSFTNGP11.phx.gbl>
Newsgroups: microsoft.public.dotnet.languages.csharp,microsoft .public.vsnet.general
NNTP-Posting-Host: bdsl.66.12.179.178.gte.net 66.12.179.178
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP11.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.general:14657 microsoft.public.dotnet.languages.csharp:200141
X-Tomcat-NG: microsoft.public.dotnet.languages.csharp

I am using Dotfuscator Community Edition to obfuscate an application for
Pocket PC written in C#. When I made the first pass with Dotfuscator, the
app threw a MissingManifestResourceException. Of course, since the app has
been obfuscated, the only information I got about what caused the error
pointed to resource aq.

The Dotfuscator listing window had WARNINGs about all the forms in my app,
so I excluded them on the 'Rename' tab and reran Dotfuscator. This time the
app came up and ran on the Pocket PC, however, I noticed some custom
controls did not behave correctly. I continued to exclude controls and
methods in the controls until I got the app to run on a device running
Pocket PC 2002. When I tried the app on a device running Pocket PC 2003,
more of the custom controls exhibited problems, so I began the process of
excluding controls and methods again.

The decisions about what to exclude is very hit-and-miss but I am
speculating that to solve the problems, all event handler methods, like
OnPaint(), need to be excluded. Is that correct?

Is there any documentation available about how to decide what to exclude so
Dotfuscator does not break your application?

Thanks,
Tom

Nov 15 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.