R
RedLars
Hi,
Need some advice on debugging the static code analysis (fxcop) service
in vs2005 teamsenter. In our solution any fxcop fault is configured to
result in a compiler error. On all development computers our source
code compiles \ builds without any problem.
However, on the designated building computer when compiling the source
we get roughtly 30 fxcop related errors of type CA1823. Obviously
using vs2005 ts there aswell. Viewing the output window in vs2005 the
commands issued by vs2005 on the two computers are alike.
The source code is obviously the same on the two computer, therefore I
can only assume that it must be an environmentall difference that
causing the problem. Can anyone give any clues to what files \
settings \ registry that the builtin fxcop in vs2005 ts uses when
checking the code?
Appreciate any input on this matter.
Cheers
Need some advice on debugging the static code analysis (fxcop) service
in vs2005 teamsenter. In our solution any fxcop fault is configured to
result in a compiler error. On all development computers our source
code compiles \ builds without any problem.
However, on the designated building computer when compiling the source
we get roughtly 30 fxcop related errors of type CA1823. Obviously
using vs2005 ts there aswell. Viewing the output window in vs2005 the
commands issued by vs2005 on the two computers are alike.
The source code is obviously the same on the two computer, therefore I
can only assume that it must be an environmentall difference that
causing the problem. Can anyone give any clues to what files \
settings \ registry that the builtin fxcop in vs2005 ts uses when
checking the code?
Appreciate any input on this matter.
Cheers