All geek questions in one place

TeamCity FxCop Commander: Specifying Assemblies

My first thought is that it would be bad practice to list each dll separately. I want to avoid having to reconfigure my PC every time someone creates a new project / dll.

Although with the traditional directory structure, I can not find a reasonable template template.

Directory structure

  • Decision
    • Container
      • Ben
        • Debug
    • Main
      • Ben
        • Debug
    • Web
      • Ben
        • Debug
    • ...

Any wildcard pattern (for example, **\bin\**.dll ) will map the same DLLs several times.

How do you guys indicate which builds to check with FxCop in TeamCity?

+4
source share
2 answers

I have a unit test project that references all other projects in my solution. The DLL generated by other projects is copied locally when the unit test project is built, so I run all of my analysis in this folder with one bean.

+2
source

The most convenient way for me is the FxCop project file checked in the repository. Therefore, I have the same report on the developer's machine and on the build server.

+1
source

Source: https://habr.com/ru/post/1443757/

More articles:


All Articles