Getting info about local variables.

Warning: this rules development API is likely to change in a future version of FxCop.

Currently, the locals of a method are stored in a pseudo-instruction in the method InstructionList. We plan to change this in a future version of the tool, the locals should hang directly off the method.

Here's a sample code pattern:

LocalList locals = null; if (method.Instructions.Length > 0) { locals = method.Instructions[0].Value as LocalList; } if (locals != null) { foreach(Local local in locals) { // do something } }

MichaelFanning-MS at 2007-9-9 >

The mechanism for checking locals is the same, what's the problem you're seeing?

As long as you stick with 1.35, your rules debugging should be valid between the two. There's always the possibility, though, that we've fixed an issue in 1.35 or made some other change that alters behavior.

To debug your rules within the IDE, you would have to configure a reg key (AEDebug) that specifies the debugger should be launched anytime FxCopCmd.exe is invoked. Here's a link providing some information.

http://support.microsoft.com/default.aspx?scid=kb;en-us;103861&sd=tech

MichaelFanning-MS at 2007-9-9 >

Thanks Michael & David,

As it happens I am actually using VB - not that that should make any difference - and I am already using a For ... Next loop rather than a For Each ... Next loop as shown below:

Dim memberMethod As Method = CType(member, Method) Dim methodLocalsList As LocalList = CType(memberMethod.Instructions(0).Value, LocalList) Dim methodLocal As Local ' check each local in the list For i As Int32 = 0 To methodLocalsList.Length - 1 methodLocal = methodLocalsList.Item(i) ' perform check here Next

The problem that I'm seeing is that when I run the test in stand-alone FxCop I see the rule failure messages I expected to see, since I've purposefully added local variables to a method which fail the rule to test it, and when I run the exact same rule in the Studio integrated version I don't see any failure messages.

I am performing the rule check within a Check(member) override and I'm specifically looking for a NodeType of Method before attempting to retrieve the locals - if this information helps.

I'll have a look at the debugging information and see if that can get me any further too, thanks :)

PS

Once I have this issue licked, is there any way I can tell if a local is a constant or not since that's another item I need to be able to check.

Sara_H at 2007-9-9 >

"To debug your rules within the IDE, you would have to configure a reg key (AEDebug) that specifies the debugger should be launched anytime FxCopCmd.exe is invoked. Here's a link providing some information."

Can you please explain the procedure in detail?

Thanks a lot.

mahendra_nath at 2007-9-9 >

Is there a way to debug custom rules in vs2005 without using the stand-alone fxcop?

Following is the comment from Michael in this thread -

"To debug your rules within the IDE, you would have to configure a reg key (AEDebug) that specifies the debugger should be launched anytime FxCopCmd.exe is invoked. Here's a link providing some information."

I would appreciate if any one can explain this procedure in detail?

Thanks in advance.

mahendra_nath at 2007-9-9 >

See my post -

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1090172&SiteID=1

-Mahendra.

mahendra_nath at 2007-9-9 >