Debugging a code with a DLL copy
So I have a solution with two .NET Core 3.1 apps.
One of the apps builds to a certain directory such as:
"D:\Repos\XXX\build\Latest\Test\bin\netcoreapp3.1\Test.dll"
and that directory is specified in Compile/OutputPath of the project.
I then copy over the DLL to a different destination such as:
"D:\Repos\XXX\build\Latest\Test\bin\testData\Test.dll"
This testData folder contains DLLs that are loaded by a different app, on which the Test app actually depends.
Now I am trying to attach the debugger to the existing IIS Process (w3wp), and I get a message
"Didn't find the associated module for the breakpoint ..."
When using VS I can actually debug the solution and application code, and it hits the breakpoint, but I don't seem to be able to hit the breakpoints with Rider. I have Rider and the Repo in the same folder (as I have seen that this has been an issue on some tickets).
Could someone possibly help me with this case as I am not able to debug the code at all?
Please sign in to leave a comment.
Same. I'm trying to attach to remote debugger. Guys, workaround very needed, may be any previous version does work?
So I actually managed to partially find a workaround and the reason for the bug:
As I mentioned earlier the app is running on IIS, so I was wondering whether the issue is only related to the case when I am using IIS. So I ran `dotnet exec` with the file, and in that scenario, it successfully hit the breakpoint and I was able to debug the app.
So it seems to me that the issue is actually related to Rider not being able to debug the case when IIS is being used.
Hello guys, I am very sorry to hear you faced such issue. Would it be possible to grab logs with Debugger traces(Help | Diagnostic Tools | Choose Trace scenarios) right after issue reproduced and attach it with a new issue on our tracker so would could take a closer look at it? Thanks in advance!