Currently, it is not possible to preserve our custom code analysis settings in the Visual Studio exporter within the Projucer.
ie: nothing from the Code Analysis section of project settings is preserved –
This is unfortunate, since the defaults aren’t even close to as thorough as clang-tidy or Xcode’s default static analysis warnings. This makes cleaning up desired warnings in a professional development environment very painstaking, and means that having more or less consistent warnings across developer environments is not possible.
We do have options in Projucer to “treat warnings as errors” and to set the warning level, however – that’s of pretty limited use – when one cannot actually configure which warnings are indeed enabled or not.
Does there exist a way to set this stuff up so it’s preserved by the Projucer exporter?