Hi,
I'm facing this issue that seems very common and seems to be hard to overcome.
I have all projects in the same solution running under Visual Studio 2012 (with Update 3 installed), all running in the same framework (4.0):
- A class library with entities;
- A WCF service (using wsHttpBinding)
- A test application
The WCF Service, although is part of the solution, is hosted in IIS with a specific app pool (with a specific identity that I'm passing on client calls, running in 4.0 framework and not allowing 32bit).
What happens is, when I try to step into the service (by using right click or pressing 'F11' key, it returns me the following error:
"Unable to automatically step into the server. Unable to determine a stopping location. Verify symbols are loaded."
Here is a list of things that I've tried to do:
- Disable "Just my code" option in Visual Studio;
- Checking if any assembly was on GAC (just in case, and no one was);
- Delete manually files in bin and obj folders, delete files in temp folder in .Net Framework 4.0 64 bit, delete files in AppData asembly folder, and build the projects in solution one by one.
- Doublechecked and re-checked the target frameworks in projects
- Doublechecked flag "ASP.Net" is checked in "Web" section in project's properties;
- Doublechecked solution configuration if is correct;
- Doublechecked if debug flag is defined in <System.Web> section
- Restarted machine;
- Repaired .Net framework installation (no issues found);
- Repaired Visual Studio 2012 installation;
- Deleted "suo" file
- Ensured that all assemblies and pdb files are in "bin" folder of the WCF service and on the test application.
I honestly believe that I've tried every solution I found on the Web!
There was no major change (such as changing target framework, adding a project or even adding a file) that could lead to this situation. When I try to step into the service it prompts me with an "attach securty warning" as usual and in output window writes "Auto-attach to process '[xxxx] w3wp.exe on machine YYYYYY succeeded".
One thing that makes me wonder is in the following picture, relies on the fact that is not telling "Managed (v4.0.30319), x64. It is appearing with type as "x64" only.
Is there any step or logic attempt that I've should made to overcome this issue? It's blocking my work two days until now...