Re: Debugging Web API
If my memory serves me correctly, I believe you can run the Web API solution and call the API from Fiddler. Any breakpoints you set will be hit. I am pretty sure that this has worked for me. I'll try that, and I have to install a fresh Fiddler on my new system anyway. I remember last time I had to jump through hoops to get Fiddler to work with localhost, but maybe that's easier now -- Greg
RE: Debugging Web API
Hi Greg, The book mentioned the issue re fiddler with supporting localhost (with IE) – but the latest version worked for me straight out of the box. It’s interesting to watch what packets are going on your machine (more like scary). *Regards,* *Steven Parish* *Software Architect | BusinessCraft Pty Ltd | www.businesscraft.com www.businesscraft.com* Tel: (02) 4965 | Mob: 0417 688 599 | Fax: (02) 4965 5333 | Level 1, 270 Turton Road, New Lambton, NSW 2305 -- *Disclaimer* The information contained in this and associated e-mails and any attachments are confidential and were only intended solely for the use of the addressee. If you have received this e-mail in error, please notify the identified sender by return e-mail and then delete all copies of this and associated emails and their attachments from your computer and or your computers system. Opinions, conclusions and other information in this message that do not relate to the business of BusinessCraft Pty Ltd shall be understood as neither given nor endorsed by it. It is your responsibility to check the message and any attachments for any viruses before use. BusinessCraft does not accept liability for any loss or damage that may result, directly or indirectly from your receipt of this message or any attachments contained within it. *From:* ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Greg Keogh *Sent:* Tuesday, 24 December 2013 5:56 AM *To:* ozDotNet *Subject:* Re: Debugging Web API If my memory serves me correctly, I believe you can run the Web API solution and call the API from Fiddler. Any breakpoints you set will be hit. I am pretty sure that this has worked for me. I'll try that, and I have to install a fresh Fiddler on my new system anyway. I remember last time I had to jump through hoops to get Fiddler to work with localhost, but maybe that's easier now -- Greg
Re: Debugging Web API
The book mentioned the issue re fiddler with supporting localhost (with IE) – but the latest version worked for me straight out of the box. It’s interesting to watch what packets are going on your machine (more like scary). Indeed .. in praise of Fiddler I must say I haven't used it for a year or so and that time it was just to check the response headers of a service. I took some time to look at all the tabs and features in the latest version and I'm really impressed. It's great to be able to drag a session into the Composer tab and play with it, and to see https traffic, and decode various formats. I was shocked by the amount of traffic from Gmail and Bing, the latter caused by IE address bar suggestions which I have no use for and deactivated. I can see the requests and responses to my Web API, but I don't know how to get VS2013 to break. I tried attaching to the Fiddler and IE process but it doesn't work. Is there a trick to run the VS2013 project? There is no Start Page like in a Web Forms, WCF or ASMX project. Greg
Re: Debugging Web API
Hi Greg, I am using VS2012. I just tested this and it works for me, but maybe there is some voodoo setting that I have forgotten about. In my VS solution my WebAPI project is set as the startup project. I run it with debugging and it just sits there running. When I make a call to the api via Fiddler, it breaks on the breakpoints that I have set. What is happening for you? At which point does it not seem to work? Cheers Dave On 24 December 2013 11:36, Greg Keogh g...@mira.net wrote: The book mentioned the issue re fiddler with supporting localhost (with IE) – but the latest version worked for me straight out of the box. It’s interesting to watch what packets are going on your machine (more like scary). Indeed .. in praise of Fiddler I must say I haven't used it for a year or so and that time it was just to check the response headers of a service. I took some time to look at all the tabs and features in the latest version and I'm really impressed. It's great to be able to drag a session into the Composer tab and play with it, and to see https traffic, and decode various formats. I was shocked by the amount of traffic from Gmail and Bing, the latter caused by IE address bar suggestions which I have no use for and deactivated. I can see the requests and responses to my Web API, but I don't know how to get VS2013 to break. I tried attaching to the Fiddler and IE process but it doesn't work. Is there a trick to run the VS2013 project? There is no Start Page like in a Web Forms, WCF or ASMX project. Greg
