TeamCity 和 NCover 集成，排除文件/类型只会给我错误
我正在尝试将 NCover 2 集成到 TeamCity 5.0.1 中，并且由于项目中的一些文件超出了我的控制范围，因此我想从 NCover 统计数据中排除这些文件。
在 TeamCity 构建运行程序设置中，我有一个“附加 NCover 参数”选项，并通过查看页面 描述 NCover 参数，我将以下内容添加到此框中：
//exclude-types "Markdown;Settings;Resources"
运行 teamcity buildstep 时，我在日志中收到此错误，并且构建失败：
NCover has determined that one of the paths in the
//h or //w commands ends with a backslash (\).
Please remove or escape the backslash and run NCover again.
如果我删除此设置，错误就会消失。
有没有人像这样配置 TeamCity 和 NCover 2 并且可以发现我的错误？
I am trying to integrate NCover 2 into TeamCity 5.0.1, and since I have some files in the project that are out of my control, I'd like to exclude those from the NCover statistics.
In the TeamCity build runner setup, I have an option for "Additional NCover arguments", and by looking at the page that describes NCover parameters, I added the following to this box:
//exclude-types "Markdown;Settings;Resources"
When running the teamcity buildstep, I get this error in my log, and the build fails:
NCover has determined that one of the paths in the
//h or //w commands ends with a backslash (\).
Please remove or escape the backslash and run NCover again.
If I remove this setting, the error goes away.
Has anyone configured TeamCity and NCover 2 like this and can spot my mistake?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
当我们从 NAnt 触发 NCover 1.5.8 时，我们也遇到了类似的属性排除问题。这是一个正确引用论点的问题。尽管参数完全符合 NCover 文档，但我们根本无法让它工作。解决方法为我们解决了这个问题： 通过设置文件
We had a similar problem with attribute exclusion when we triggered NCover 1.5.8 from NAnt. It was an issue with proper quotation of the arguments. We simply couldn't get it working although the args exactly complied to the NCover documentation. A workaround solved the problem for us: Passing arguments via a settings file
您发布的命令看起来正确，请检查 teamcity 构建日志的其余部分以查看他们发送到 ncover 的整个命令。他们发送的基本命令+您输入的命令可能会触发错误消息。
the command you posted looks correct, check the rest of the teamcity build log to see the entire command that they're sending to ncover. It's possible that the base command they send + the command you've entered is triggering the error message.