C# code analyser...

[Guest]

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

 

[Guest]

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.

 

[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 (e-mail address removed)
Falafel Software http://www.falafelsoft.co.uk
_______________________________________________

 

[Stu Smith]

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

 

[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.