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?