Hi,

Thanks for sharing this issue. I'm afraid my knowledge of postsharp is fairly limited, but I'll do my best to try and help figure out where this is clashing. Are you making use of any features in the newly introduced PostSharp version?

I think the best plan is to try placing NCrunch in compatibility mode to see if this has any effect on the build. Being a post-build manipulation tool, PostSharp may be expecting a certain project or solution structure when it attempts to adjust your code after NCrunch has built it - and it's entirely possible that modifications in the new version have introduced new assumptions that don't hold true in the NCrunch environment. Using compatibility mode can help to bring the NCrunch build closer to that of a normal build, and may help us to deductively figure out where the problem is.

Don't worry about caching. Every time you restart the NCrunch engine, any kind of build caching or workspacing is thrown away. NCrunch will store code coverage and test results, but none of this will make any difference to the build process.