Execution of the NCoverExplorer action fails when executed with /report:1 (ModuleSummary) for Could not write to file
CommandLine: F:\Builds\Phoenix\PhoenixTrunkIntegrationBuild\*.tempCoverage.xml /project
Execution of the NCoverExplorer action fails when executed with /report:1 (ModuleSummary) for Could not write to file
CommandLine: F:\Builds\Phoenix\PhoenixTrunkIntegrationBuild\*.tempCoverage.xml /project
Hi Lee,
I believe the issue here is that the path to the file, ‘Lsr.Phoenix.DocumentManagement.Mappers.Functions.AddressFunctions.html’, is longer then 255 characters and this is why NCover is failing to write the file out. You’ll need to contact NCover support for this issue.
Regards,
Paul.
Paul,
It is the likely culprit, however that is not a path I am setting. In fact, I cannot find where to set that path. when I output any of the other reports, the path is correct, just not this one.
Hi Lee,
I’ve just pinged the NCover guys as to whether this is a bug, I’ll post back when I know more about the issue.
Regards,
Paul.
Lee,
I'm an engineer on the NCover team. I wanted to let you know that updating to the latest version of NCover 2 (http://www.ncover.com/download/version2), or to NCover 3 (http://www.ncover.com/download/current) should resolve your issue. We changed our scheme for the html report file names so that they would not pass the 255 character limit that Windows imposes.
Please don't hesitate to contact us through our support form at http://www.ncover.com/support if you have any other questions.
Thanks for using NCover!
Alan
Thanks for responding Alan
Thank you for the response. I will upgrade our systems when we have the opportunity, in the meantime I found a workaround by using the execute program task (rather than the NCover task), which does just what I want and does not produced the same error.