Didn't find the associated module for the breakpoint - When attaching to IIS - VS 2022 works good

Hi,
I have a project that for reasons that are not important in this post, needs to be run in local IIS.

There are multiple projects with different technologies. None work.
.NET 4.8, .NET Core 3.1, .NET Core 5, .NET Core 6

I build in debug mode with full PDB symbol files. I run Rider as Administrator.
When I attach Rider debugger to the w3wp process that runs my AppPool with the application I want to debug, all breakpoints turn grey with the message: "Didn't find the associated module for the breakpoint."

When I do precisely the same from Visual Studio 2022, it triggers perfectly, and I can debug code normally. (It works even without rebuilding the solution in VS.

I tried File->Invalidate cache option, but it didn't help.
I read that having a solution on the same drive as Rider helps. I have just one partition on my PC, so everything is under C:\ drive.
I tried first hitting my endpoint and only after that attaching a debugger. It didn't help.

This is a deal-breaker for me. I changed jobs, and the whole codebase is like that. If I can't debug in Rider, then I see no point in having it.

What do you suggest to check and verify to fix the issue?

11 comments
Comment actions Permalink

Hello MAciej,

Thank you for contacting Rider support! Apologies for not responding earlier.

We are sorry to hear that you encountered this issue. Would you mind sharing the additional information as described below?

  • Enable the trace scenario for Debugger in Help | Diagnostic tools | Choose Trace Scenarios
  • Reproduce the issue
  • Collect all Rider logs via Help | Collect logs
  • Disable tracing in Help | Diagnostic tools | Choose Trace Scenarios and attach collected data
  • Upload the archive generated to the Upload Service and let me know the Upload ID.
  • Share a project that reproduces the issue if possible.

Thank you in advance and have a nice day!

0
Comment actions Permalink

Hi Dmitry Kazantsev

Here is upload ID: Upload id: 2022_07_20_27aU3g4gPfwk8ZXuUsGKnF (file: rider-logs-20220720-11312212148115707643390693.zip)

I can't share the project. But I can provide you all the data you would need to check this issue.

Little bit more data:
The project is Built using all  DEBUG settings. DLL files and PDB files are outputted to "bin" directory.
IIS application is configured to run from that "bin" directory.

When attached from Rider it greys out all breakpoints.
When attached from Visual Studio, it works properly.

Thank you for your help.

0
Comment actions Permalink

Hello Maciej,

Thank you for the details shared.

Would you mind trying to scroll the list of processes to attach down and check if there is another w3wp process and selecting it if there is such.
Please let me know if it doesn't help.

0
Comment actions Permalink

Dmitry Kazantsev
Hello Dmitry,

Multiple w3wp processes are running at the same time. I'm 100% sure that I attach to correct one. I verify the ApplicationPool parameter of the process. I also did a check where I attached via Visual Studio, note down PID, and then double check PID in Rider.

0
Comment actions Permalink

Dmitry Kazantsev

Did you found something in my logs?

Do you need me to provide more details?

0
Comment actions Permalink

I have the same issue

 

........JsonSettingsProcessor.cs is not found among the loaded symbol document

0
Comment actions Permalink

Hello Maciej, Hz1220,

Apologies for not responding earlier.

Please take a look at the screenshot attached. As you can see, there are several w3wp processes that have the same pid. Would you mind ensuring that you launch Rider as administrator and ensuring that you select the process under `.NET Core processes` section?

Please let me know if it doesn't help.

0
Comment actions Permalink

Dmitry Kazantsev

There is only 1 process with given PID.
I think that this process is shown in multiple "categories" in the rider as it internally hosts .NET, .NET Core and is a native process. It is IIS worker after all.

But yes, I did try to attach to this process from all 3 places.

0
Comment actions Permalink

Hello Maciej,

Thank you for keeping me posted. Would you mind confirming that selecting the w3wp process under `.NET Core processes` section doesn't resolve the issue?

As per logs you sent us earlier, it seems like you at that time you selected the .NET process, but not .Net Core process. Would you mind reproducing the issue ensuring that breakpoints are not being hit with .NET Core process selected and sharing logs again (with Debugger traces again, as I described earlier)?

Thank you in advance!

0
Comment actions Permalink

I have the same problem. Using framework 4.8. I remember it working correctly at another point in time. Tried using the newest and version 2021.3.4 of rider, but still getting "Didn't find the associated module for the breakpoint"

0
Comment actions Permalink

Hello Matiasreidem,

Do you mean you have .Net framework  ASP.NET application running in IIS and can't hit breakpoint after attaching to w3wp process under the .NET process section?

Would you mind sharing the additional information as described below?

  • Enable the trace scenario for Debugger in `Help | Diagnostic tools | Choose Trace Scenarios`;
  • Reproduce the issue;
  • Collect all Rider logs via `Help | Collect logs`;
  • Disable tracing in `Help | Diagnostic tools | Choose Trace Scenarios`;
  • Upload the archive generated to the Upload Service and let me know the Upload ID.
  • Share a project that reproduces the issue if possible.

Thank you in advance and have a nice day!

0

Please sign in to leave a comment.