C# code analyser...

[Dev]

Can you please tell me what C# code analyser do you use.
Is devAdvantage the best?

Do you use FxCop as well in conjunction with statis code analyser?
Is it good practise to use Obfuscator?

Your guidence would be apprecited.

Thanks,
Dev

[Rakesh Rajan]

I use FxCop.

If you don't want ppl to pry into your IL, then obfuscate - i don't think
there are any after effects due to obfuscation though...even if there happens
to be some issue (like perf or so), the impact should probably be extremely
low.

"Dev" wrote:

Can you please tell me what C# code analyser do you use.
Is devAdvantage the best?

Do you use FxCop as well in conjunction with statis code analyser?
Is it good practise to use Obfuscator?

Your guidence would be apprecited.

Thanks,
Dev

[Jim Cooper]

even if there happens to be some issue (like perf or so)

Given the level of self-obfuscation that some people's naming
conventions inflict, I don't think you'll see any problems :-)

Cheers,
Jim Cooper

_______________ _______________ _______________ __

Jim Cooper ji*@falafelsoft .com
Falafel Software http://www.falafelsoft.co.uk
_______________ _______________ _______________ __

[Stu Smith]

"Rakesh Rajan" <Ra*********@di scussions.micro soft.com> wrote in message
news:45******** *************** ***********@mic rosoft.com...

I use FxCop.

If you don't want ppl to pry into your IL, then obfuscate - i don't think
there are any after effects due to obfuscation though...even if there happens to be some issue (like perf or so), the impact should probably be extremely low.
There can be an impact for several reasons:

1) Anywhere you use reflection is potentially impacted. Examples include:
a) Enum.Parse
b) Any kind of 'active' configuration files (eg containing names of
classes to instantiate)
c) Serialisation
2) Any public interface you make available to third parties
3) Obfuscators contain bugs -- they can screw up code (although that's rare)

Stu

"Dev" wrote:

Can you please tell me what C# code analyser do you use.
Is devAdvantage the best?

Do you use FxCop as well in conjunction with statis code analyser?
Is it good practise to use Obfuscator?

Your guidence would be apprecited.

Thanks,
Dev

[Ira Baxter]

Obfuscators that work by parsing like the C# compiler does,
don't screw up. At least our doesn't.

Names which might get mangled by an obfuscator,
that are used in some public context (your reflection,
serialization, initialization examples below,
are easily handled: tell the obfuscator not
to touch them.

--
Ira D. Baxter, Ph.D., CTO 512-250-1018
Semantic Designs, Inc. www.semdesigns.com
"Stu Smith" <st*****@nosp am-digita.com> wrote in message
news:eV******** ******@tk2msftn gp13.phx.gbl...

"Rakesh Rajan" <Ra*********@di scussions.micro soft.com> wrote in message
news:45******** *************** ***********@mic rosoft.com...

I use FxCop.

If you don't want ppl to pry into your IL, then obfuscate - i don't think there are any after effects due to obfuscation though...even if there happens

to be some issue (like perf or so), the impact should probably be

extremely

low.

There can be an impact for several reasons:

1) Anywhere you use reflection is potentially impacted. Examples include:
a) Enum.Parse
b) Any kind of 'active' configuration files (eg containing names of
classes to instantiate)
c) Serialisation
2) Any public interface you make available to third parties
3) Obfuscators contain bugs -- they can screw up code (although that's

rare)
Stu

"Dev" wrote:

Can you please tell me what C# code analyser do you use.
Is devAdvantage the best?

Do you use FxCop as well in conjunction with statis code analyser?
Is it good practise to use Obfuscator?

Your guidence would be apprecited.

Thanks,
Dev