Re: Code audit
- From: Leon <Leon@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 4 Dec 2008 07:11:01 -0800
Hi Patrice,
The overall goal is to performa a statistical analysis on the codebase: how
many calls are made to a given method and by which applications. While
marking methods as obsolete would be a great approach going forward, it
doesn't solve my immediate need to figure out what methods are being called
(I wouldn't know which are actually obsolete).
Regards,
Leon
"Patrice" wrote:
The overall goal is ?.
You could use the obsolete attribute to mark what you don't want to be used
in this framework
(http://msdn.microsoft.com/en-us/library/system.obsoleteattribute.aspx).
Then it will issue a warning (or an error depending on how you configured
the attribute) when you compile something that uses this method...
"Leon" <Leon@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de groupe de
discussion : E495F22A-02E9-4DD9-9F12-A527DB42EC58@xxxxxxxxxxxxxxxx
Hello,
I am currently working on a project with the following layout:
10 applications, each making calls to a common custom framework built on
top
of .Net. Each app consists of a solution with a number of projects
underneath. The framework is referenced by each application through a
project reference, but each app may use different methods inside the
framework (ex. some apps use Transactions, others don't). I need -to
perform
an audit on the applications to figure out which methods in the framework
are
actually used, but I can't seem to come up with an effective way of doing
it.
Since the framwork is referenced in 10 separate solutions, I would like to
avoid having to open each one individually and than finding all the
references for each of the framework methods. Does any one know of a good
tool to do this or can recommend an approach?
Thank you very much,
Leon
- Follow-Ups:
- Re: Code audit
- From: Patrice
- Re: Code audit
- References:
- Code audit
- From: Leon
- Re: Code audit
- From: Patrice
- Code audit
- Prev by Date: Re: Int8 and UInt8 types instead of Byte and SByte
- Next by Date: Re: Code audit
- Previous by thread: Re: Code audit
- Next by thread: Re: Code audit
- Index(es):
Relevant Pages
|