vs有断点就卡死,更新到vs2017.3后,不会遇到断点

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

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".

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.

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

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值