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 <[email protected]> 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 >
