断点已设置但尚未在 Visual Studio 中绑定

Question

Running Visual Studio Community 2017. Created a WebAPI project, have a controller class in there, with some basic stuff, but when I go to run in debug mode, I get the following error on my breakpoints, and I haven't the foggiest idea why.

The breakpoint will not currently be hit. Breakpoints set but not yet bound.

I've seen a few answers here and there, but they don't help, or they're about Visual Studio Code, which I am definitely not using.

I found this , but it doesn't tell me what to do about my problem. How do I fix this issue?

Answer 1

Change your Project mode from Release to Debug in your Visual Studio.

Answer 2

尝试将您的 web 项目设置为默认Startup Project 。

Answer 3

If you are using Multiple projects, you need to make sure the step below, let project debug normally

1. Confirm the project which you want to debug is a default project, otherwise setting it as startup project
2. Confirm your project mode is Debug instead of Release
3. Clean your solution or projects and rebuild your projects
4. Restart & Running your Current project.

Answer 4

只需清除解决方案并重新启动 Visual Studio。

Answer 5

Clean the solution:

Build -> Clean [solution name]

Answer 6

Select Debug instead of Release...And it might work..

Answer 7

Usually it can happen even if all the configurations in project are OK, so do the following.

Right Click to Solution and under Configuration change Release to Debug

Answer 8

This helped me

1). Build > Clean Solution and then restart Visual Studio and rebuild your project, after that debug again.

https://learn.microsoft.com/en-us/answers/questions/265772/visual-studio-debugging-breakpoint-set-but-yet-bou.html

Answer 9

It worked for me:

1.Clean the Solution 2.Set Startup Project 3.Restart the Visual Studio

Answer 10

如果您的 Web API 项目在 IIS 中运行，并且/或者在终端上启动（例如，如果您使用的是 .net Core），并且您需要将调试器附加到已经运行的进程，请确保 Visual Studio 以管理员身份运行，除非它不允许附加到进程。

Answer 11

If you have a typo in your Javascript, the breakpoint will not work. I used "<>" instead of "!=" and when I fixed it, the breakpoint worked again.

Answer 12

当您在解决方案运行时尝试在“javascript”文件中放置断点时，将显示“断点不会被命中”警告。对此的解决方案是，停止调试并在 javascript 中放置断点并再次运行项目

Answer 13

Please try following steps to troubleshoot:

1). Build > Clean Solution and then restart Visual Studio and rebuild your project, after that debug again.

2). Please go to your solution folder and delete(or rename) the “obj”, “bin” and the hidden “.vs” folder, restart Visual Studio and then rebuild your solution.

3). Check if you have chosen the “Debug” mode and if you have many other projects in this solution, make sure you have set the “Set as Startup Project” for the corresponding project.

Answer 14

Need to set the Solution Configuration to Debug mode. If it is release mode, the breakpoints will not be hit

Answer 15

I had exactly the same message even though I tried most of the suggestions here. What worked in the end was to change the "Project Url" under "Properties" of the website project. In my scenario I changed it from http://localhost/productname.web to http://localhost:56260 .

Answer 16

做了一切，但问题仍然存在，当我清除浏览器的缓存和 Windows/Microsoft .NET/Framework 和 Framework64 中的临时 ASP .Net Files 文件夹时，终于解决了。

Answer 17

如果任何最重要的答案对您来说都失败，请重新启动计算机，然后在调试模式下再次运行。

Answer 18

My team was able to resolve this issue today and I wanted to share the solution because it is unique from everything else I have read online. I hope it helps someone out there.

Here's our situation for some context: We have an ASP.NET solution in Visual Studio that has two projects: one for the API and one for the website. It's got a mix of jQuery, JavaScript, and C# code. We were able to debug JavaScript & jQuery code, but NOT the C# code. That is when we were getting the dreadful "Breakpoints set but not yet bound in Visual Studio" error. To make a long story short, we had to update a web.config file to point to the correct localhost port on my machine instead of the server.

This is what we had to do to get it working:

1. Open an instance (we will call this "the first instance") of Visual Studio (we will call it VS from now on) with the website project set as the Startup Project.
2. Open a second instance of Visual Studio with the API project set as the Startup Project. Click the Start button to open the web browser. You may get a server error (I did) but that's okay. Copy the full address in the address bar (for example http://localhost:12345/).
3. Back to the first instance of VS, we had to edit the web.config file for the website project to point to the address we copied above. This value was in the configuration section under appSettings. There was a key in there that looked like this once we changed it:

    <add key="WebAPI_Address" value="http://localhost:12345/" />

4. Once this information is saved, we had to Start the API project in the second instance of VS, and then go to the first instance of VS and Start the website project there.

I hope I didn't leave anything out. One thing to note is, the website localhost address is different for us compared to the localhost address when the API project was launched. One of our developers got the same port number for both. To resolve that issue, he had to Start the API project using a different browser, and then he got a unique port number. I don't know why, maybe it depends on the environment.

Answer 19

vs might be in release mode. just change it to debug mode

Answer 20

If your breakpoint is in a different project and only this one is not reachable, check if "Enable Just My Code" is activated under Tools > Options > Debugging > General.

Answer 21

On an ASP.NET web project, this message appeared when trying to set a breakpoint on a script that was apparently cached - the browser wasn't loading the updated version of the script (originally embedded in the HTML, then moved to a separate file).

Clearing the cache resolved it.

Answer 22

Ran into this issue when creating a custom web.config template on an ASP.NET MVC Application. Issue was inside the *.csproj, had to set the following PropertyGroup.

 <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Your_Custom_Configuration|AnyCPU' "> <DebugSymbols>true</DebugSymbols> <DebugType>full</DebugType> <Optimize>false</Optimize> <OutputPath>bin\</OutputPath> <DefineConstants>DEBUG;TRACE</DefineConstants> <ErrorReport>prompt</ErrorReport> <WarningLevel>4</WarningLevel> </PropertyGroup>