>
> Sorry I haven't got back to you as promised. School holidays and kids have
> gotten in the way. I will get back to you tonight.
>
Don't panic, I return to REST experiments on Friday. For the last week, as
a hobby, I've been writing a T4 template that generates complete CRUD
classes over an Esen
Hi Greg,
Sorry I haven't got back to you as promised. School holidays and kids have
gotten in the way. I will get back to you tonight.
Cheers
Dave
On 27/12/2013 3:40 PM, "Greg Keogh" wrote:
> Sorry Greg, I am out all day. Will have a look tonight and get back to
>> you. What sort of project are y
>
> Sorry Greg, I am out all day. Will have a look tonight and get back to
> you. What sort of project are you using?
>
I think I created an empty ASP.NET project then added the directory
structure for Web API using one of the wizard steps. Then I right-clicked
and added controllers, etc. Details a
Sorry Greg, I am out all day. Will have a look tonight and get back to you.
What sort of project are you using?
Sent from my flux capacitor. Please excuse brevity and any odd autocorrect
errors.
On 27/12/2013 7:37 AM, "Greg Keogh" wrote:
> In my VS solution my WebAPI project is set as the startu
>
> In my VS solution my WebAPI project is set as the startup project. I run
> it with debugging and it just sits there running.
>
Dave, when I do that same I get:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Which is perfectly expected.
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 Fidd
>
> 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 fo
*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
a
>
> 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
>
>
> http://blogs.msdn.com/b/webdev/archive/2013/04/04/debugging-asp-net-web-api-with-route-debugger.aspx
>
I tried following this and adding a Nuget package, but it bloated the tiny
project to a huge size and it wouldn't show the cshtml page when I set it
as the start page. It made such a mess I
This *might* help you...
http://blogs.msdn.com/b/webdev/archive/2013/04/04/debugging-asp-net-web-api-with-route-debugger.aspx
Not sure. Most of the web api playing I've done (nothing yet for real, just
having a look) I also had a normal web app. So I'd run and debug the web
app, and because the w
Folks, I'm writing my first Web API today because I found that a Borland
C++ client can not easily consume a SOAP service. You can run the Borland
wsdl utility on the service, but the .h file it generates doesn't look very
useful. I'm trying a Web API service as an alternative.
I'm running through
12 matches
Mail list logo
