NCrunch does not seem to support editorconfig inheritance

Hi! This is a follow-up to this thread from some months ago: https://forum.ncrunch.net/yaf_postst2873_Using-NCrunch--FxCop-Analyzers-and--warnings-as-errors---How-to-configure-warning-severity.aspx

I have this setup: I am using FxCop Analyzers and <WarningsAsErrors/>. In my C# solution I have a global .editorconfig file. In a test project I have an additional .editorconfig that overrides/extends the global one.

Problem: When building the test project, NCrunch only reads the local (overriding) .editorconfig file. It ignores the global .editorconfig. As a result, it reports some errors that I want it to ignore and then fails to compile.

If I didn't have the overriding .editorconfig I could solve it by adding a symlink to the global .editorconfig in each project (as in the thread linked above). Now that I have the overriding one, this trick no longer works.

Is there any way to solve this?

I'm using NCrunch 4.3.0.13, Visual Studio Professional 2019 version 16.4.6., C# 8.

Thanks!

Hi, thanks for posting.

I'm not particularly familiar with the mechanics of these files or their purpose, but is it possible that the global editorconfig file simply needs to be present inside the NCrunch workspace? If so, try adding it to the 'Additional files to include' in your NCrunch solution-level configuration.

Remco wrote:I'm not particularly familiar with the mechanics of these files or their purpose, but is it possible that the global editorconfig file simply needs to be present inside the NCrunch workspace? If so, try adding it to the 'Additional files to include' in your NCrunch solution-level configuration.

Thanks. Where do I set "Additional files to include"? I see no such setting when I go to Extensions -> NCrunch -> Configuration and search.

I solved this in NCrunch Configuration > General Settings > Build Settings > Custom build properties by adding RunAnalyzers = false.

Remco, you may want to do this automatically (unless Allow code analysis is true, presumably).

Documented here: https://docs.microsoft.com/en-us/visualstudio/code-quality/disable-code-analysis?view=vs-2019#net-framework-projects

ejball wrote:I solved this in NCrunch Configuration > General Settings > Build Settings > Custom build properties by adding RunAnalyzers = false.

Remco, you may want to do this automatically (unless Allow code analysis is true, presumably).

Documented here: https://docs.microsoft.com/en-us/visualstudio/code-quality/disable-code-analysis?view=vs-2019#net-framework-projects

Thanks, but this didn't make any difference for me.

ClausAppel3Shape wrote:

Remco wrote:I'm not particularly familiar with the mechanics of these files or their purpose, but is it possible that the global editorconfig file simply needs to be present inside the NCrunch workspace? If so, try adding it to the 'Additional files to include' in your NCrunch solution-level configuration.

Thanks. Where do I set "Additional files to include"? I see no such setting when I go to Extensions -> NCrunch -> Configuration and search.

I figured this out. The setting is not visible nor searchable when "General Settings" is selected. I have to unfold "General Settings" and select either "My Settings" or "Shared Settings". This seems to fix my immediate problem.