Why doesn't remote debugging work for WCF service hosted by IIS?

Question

I have a simple WCF service hosted by IIS and am running into the classic problem of not being able to load symbols or hit a breakpoint when remotely debugging, although I believe I am doing everything correctly. Here is a simple sequence of screen snapshots of the steps I'm following; could someone with a sharp eye please point out what I'm missing?

1. The dll for the app rests in the indicated directory here, with its own app pool as shown:

2. And that folder, containing the dll and pdb for debugging info, looks like this:

3. I start the Visual Studio remote debugging monitor (as an admin) on the remote machine:

4. On my local machine, where my code exists, I go to Tools | Attach To Process, and navigate to the remote machine, and pick the w3wp.exe process for the service pool hosting my application:

5. Back on the remote machine, the VS debugging monitor shows I'm connected:

6. But on my local machine, no debugging information is available. And yes, I am absolutely positive the code that has been built locally was a debug build and exactly matches what was moved to the remote machine:

Answer 1

NODOTS had the answer to the problem in his/her comment. I'm not sure how to mark that comment as the correct answer and show a screen snapshot, so I'll do that here.

I needed to have "Managed (v4.5, v4.0) code" selected as shown, circled in red, in the following screen snapshot. Many thanks to NODOTS for the solution.