Hi Markus,
Thanks for posting!
Is the error consistently reporting the XML file using an absolute path to your C drive as you've shown above? Or is it referencing inside the NCrunch workspaces directory? If the XML file is being
referenced absolutely, then probably it's a point of crossover between NCrunch and your foreground solution. This is a bad thing as it means that NCrunch is unable to generate or work with these XML files in isolation - you'll get interference between processes along with file locking and data related errors.
If this is indeed the case, the solution is to change the way the XML files are being generated and referenced so that this happens only using a relative file path.
NCrunch workspaces are arranged entirely using relative paths, so doing this means that NCrunch will have its own separate copies of the XML files and there won't be any interference with your foreground solution.
If this documentation is only being generated and it isn't being used by your test code, you could also disable the build step using
conditional build behaviour. This would likely improve your NCrunch performance too.
