ASP.NET

wcf breakpoints no longer getting hit for some reason? RSS

4 replies

Last post May 11, 2012 05:39 PM by dotnetterAMG123

‹ Previous Thread|Next Thread ›

- Reply
dotnetterAMG...

Member

236 Points

520 Posts

wcf breakpoints no longer getting hit for some reason?

May 11, 2012 03:48 PM|LINK

Hello - I'm using jQuery to call WCF services.

My debug breakpoints in my WCF services were getting hit during debug until yesterday afternoon. However, now the breakpoints in my WCF services are not getting hit for some reason. I've tried "Clean Solution", "Rebuild Solution" and restarted my computer.

The WCF services are getting called because I can make changes and the data is returned as expected from the WCF services. However, the breakpoints in the WCF services are still not getting hit.

Any suggestions on additional steps I can take to restore the hit breakpoint functionality in my WCF services?
- Reply
amosCabanban...

Member

441 Points

148 Posts
Re: wcf breakpoints no longer getting hit for some reason?

May 11, 2012 04:55 PM|LINK
Do you have this enabled?
```
<system.web>
  <compilation debug="true" />
</system.web>
```
- Reply
Nazm

Participant

1760 Points

330 Posts

Re: wcf breakpoints no longer getting hit for some reason?

May 11, 2012 05:01 PM|LINK

Have you tried to remove files from Debug source files.

Solution > Property Pages > Common Properties > Debug source files >

Directories containing source code :

C:....

C:...

C: remove any wrong path

Do not look for these source files:

Remove any path here.

while(Experience<∞){foreach(var breath in life.Moments){Experience++; return "Above all science known";}}
- Reply
dotnetterAMG...

Member

236 Points

520 Posts
Re: wcf breakpoints no longer getting hit for some reason?

May 11, 2012 05:10 PM|LINK
amosCabanban86

Do you have this enabled?
```
<system.web>
  <compilation debug="true" />
</system.web>
```
Yes - that's enabled in Web.config....
- Reply
dotnetterAMG...

Member

236 Points

520 Posts

Re: wcf breakpoints no longer getting hit for some reason?

May 11, 2012 05:39 PM|LINK

It's working again as expected. I think it was due to selecting a different website in the sln as startup, selecting an old url from the history dropdown or a combination of these but it's working again as expected now....
- Marked as answer by peter pi - msft on May 15, 2012 01:49 AM