更新到vs2017.3之后，断点将不会被命中 [英] After updating to vs2017.3, the breakpoints will not be hit

问题描述

我们有一个运行在Vs2017.3(从2017.2更新)上的asp.net核心2.0项目(从1.x迁移).

We have an asp.net core 2.0 project (migrated from 1.x) running on Vs2017.3 (updated from 2017.2).

更新后，断点不再出现. Vs报告断点当前不会被击中.源代码与原始版本不同".

After the update, breakpoints stop being hit. Vs reports that "The breakpoint will not currently be hit. The source code is different from the original version".

在进行更新和迁移之前，一切正常.在更新到2017.3之后并迁移到asp.net core 2.0之前，可以看到此问题.

Things were normal before updating and migration. The problem can be seen after updating to 2017.3 and before migrating to asp.net core 2.0.

我知道解决方法:即使源代码不同，也可以右键单击并强制击中断点.我需要解决方案.

I know about the workaround: To right-click and force the breakpoint to be hit even when the source codes are different. I need a solution.

清理重建无效.该问题发生在多台计算机上.

Clean-rebuild has no effect. The problem occurs on multiple computers.

推荐答案

尝试从调试"菜单中清除/删除所有断点，选择

Try to clear/delete all breakpoints from the Debug menu, choose Delete All Breakpoints.

注意:原因是它刷新了项目的Visual Studio设置文件.

Note: The reason is that it refreshes your Visual Studio setting file of your project.

这篇关于更新到vs2017.3之后，断点将不会被命中的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！