Upgrading ncrunch console tool broke content files copy to output folder

May be related to http://forum.ncrunch.net/yaf_postst5_content-files-set-to-copy-to-output-folder-not-copied-to-temp-runner-directory.aspx

After upgrading console tool to 2.26.01 from 2.19.04 some integration tests which relay on content files being copied to output folder stopped working.

With the previous version everything worked, and inspecting the folder structure, we can see the files put in xxx/bin/Debug/Web as they should.

With the new version they are put in xxx/bin/Web (missing the Debug) part.

This happens with one and the same code base, we just change the console tool version. When we downgrade, tests are restored.

What else would you need in order to investigate this problem?

Hi, thanks for sharing this issue.

I believe this is the same problem as described by Mike Ward here - http://forum.ncrunch.net/yaf_postst1939_Haven-t-been-able-to-upgrade-since-2-23-2.aspx.

Recently, the resource copy behaviour was changed to try and better align it with MSBuild. Microsoft have recently been building various extensions into the resource copying workflow and NCrunch needed to be aligned with these changes. Unfortunately, something seems to be wrong with the new copy behaviour. There is an edge case here where it doesn't work as expected.

The problem is that every on angle that I've found to test the new behaviour, it seems to work correctly. I'm in desperate need of someone that can provide me with a sample solution that demonstrates the problem so that I can properly analyse the edge case and resolve NCrunch's handling of it. Is this something you can provide me with?