FxCop integration with Visual Studio 2005 Professional Edition

[Water Cooler v2]

I am trying to add FxCop to work inside Visual Studio 2005
Professional Edition. I believe there are two approaches. The first is
outlined in this short article:

http://www.c-sharpcorner.com/UploadF...f-11aabf430ee7

However, in my IDE, there is no checkbox with the caption 'Enable
FxCop' in my copy of VS 2005 Pro as the article suggests. In fact, I
do not even see any 'Property Pages' for the project. I see the old
'Project Properties' dialog instead with items such as ' Application',
'Build', 'Build Events', 'Debug' and such.

The second way of integrating FxCop into the project is to add it in
the Tools menu of the IDE using External Tools and then pointing it to
the FxCop command line executable with the arguments /console and /
project, if one has a pre-defined project file. However, I do not have
a pre-defined project file. So, I am simply using the following
arguments:

/console /f:$(TargetName)

But even that doesn't work. I get an error message saying I have not
specified any targets. Please help.

[Water Cooler v2]

On Oct 19, 8:25*pm, Water Cooler v2 <wtr_...@yahoo. comwrote:

I am trying to add FxCop to work inside Visual Studio 2005
Professional Edition. I believe there are two approaches. The first is
outlined in this short article:

http://www.c-sharpcorner.com/UploadF...ojectPropertoe...

However, in my IDE, there is no checkbox with the caption 'Enable
FxCop' in my copy of VS 2005 Pro as the article suggests. In fact, I
do not even see any 'Property Pages' for the project. I see the old
'Project Properties' dialog instead with items such as ' Application',
'Build', 'Build Events', 'Debug' and such.

The second way of integrating FxCop into the project is to add it in
the Tools menu of the IDE using External Tools and then pointing it to
the FxCop command line executable with the arguments /console and /
project, if one has a pre-defined project file. However, I do not have
a pre-defined project file. So, I am simply using the following
arguments:

/console /f:$(TargetName)

But even that doesn't work. I get an error message saying I have not
specified any targets. Please help.

I found a resolution for the second method by supplying the $
(TargetPath) variable to the /f argument instead of the $(TargetName)
variable.

I am still interested in why my copy of VS 2005 does not display the
Property Pages as suggested by that article that discusses the first
method.