Unfortunately, caching is not built into ASP.NET Web API. Check this out to get you on track: http://www.strathweb.com/2012/05/output-caching-in-asp-net-web-api/ An updated resource here: https://github.com/filipw/AspNetWebApi-OutputCache EDIT: As of 2020-02-03, even though this answer is quite old, it’s still valid. Both of the URL’s above lead to the same project, ASP.NET Web API CacheOutput by Filip W
You might want to take a look at this blog post. It’s using Unity but it should end-up being the same. Basically, use the WebAPI Dependency Resolver. Make sure that everything is mapped properly and it should be fine. If after setting up your DI you still have problem with your OAuth token, let me … Read more
I figured it out. I was using a bad example I found in the past of how to map query string to the method parameters. In case anyone else needs it, in order to have optional parameters in a query string such as: ~/api/products/filter?apc=AA&xpc=BB ~/api/products/filter?sku=7199123 you would use: [Route(“products/filter/{apc?}/{xpc?}/{sku?}”)] public IHttpActionResult Get(string apc = null, … Read more
First off, stack traces don’t do what most people think they do. They can be useful during debugging, but are not intended for runtime use, particularly on ASP.NET. Also, the stack trace is technically about where the code is returning to, not where the code came from. With simple (synchronous) code, the two are the … Read more
You shouldn’t return a System.Drawing.Image, unless you also add a formatter which knows how to convert that into the appropriate bytes doesn’t serialize itself as the image bytes as you’d expect. One possible solution is to return an HttpResponseMessage with the image stored in its content (as shown below). Remember that if you want the … Read more
By default you don’t need to use neither [Serializable] nor [DataContract] to work with Web API. Just leave your model as is, and Web API would serialize all the public properties for you. Only if you want to have more control about what’s included, you then decorate your class with [DataContract] and the properties to … Read more
By design the body content in ASP.NET Web API is treated as forward-only stream that can be read only once. The first read in your case is being done when Web API is binding your model, after that the Request.Content will not return anything. You can remove the contact from your action parameters, get the … Read more
When debugging I was using the debug config (Which I had generated XmlComments for: Properties -> build tab -> Output -> XML Documentation File) I had not done this for my release configuration (duh…) – now everything works
After a long struggle, I found the solution. Solution: Add a reference to System.Net.Http.Formatting.dll. This assembly is also available in the C:\Program Files\Microsoft ASP.NET\ASP.NET MVC 4\Assemblies folder. The method ReadAsAsync is an extension method declared in the class HttpContentExtensions, which is in the namespace System.Net.Http in the library System.Net.Http.Formatting. Reflector came to rescue!
I am not very sure whether it will make any difference in performance of my API. Bear in mind that the primary benefit of asynchronous code on the server side is scalability. It won’t magically make your requests run faster. I cover several “should I use async” considerations in my article on async ASP.NET. I … Read more