Closed Feature: Separate service location from dependency injection [26]
There is a lot of confusion today about how Web API uses service location vs. dependency injection, caused in no small part by the fact that both activities today are performed against...
View ArticleNew Comment on "Attribute routing in Web API"
"Give a rope to people, they will hang themselves up with it" - anonymous I meant to write this comment weeks before but been busy and I hope it is not too late. Just fresh from finding a big...
View ArticleSource code checked in, #2be7b56a7649eaca40b72258cc6d5a497e938f4d
Incorporate code review feedback for StatusCodeResult.
View ArticleSource code checked in, #923e44ace311afd046d09af659015a6c94c3a347
Add FormattedContentResult class and ApiController factory methods.
View ArticleCommented Issue: Web API with Katana host won't clear Thread.CurrentPrincipal...
The specific problem happens when debugging unit test with Visual Studio. VS unit test will use some VS.Diagnostic.ServiceModelSlim assembly which will host a wcf service on the debugging process to...
View ArticleNew Comment on "CORS support for ASP.NET Web API"
The latest nightlies has parameters on the EnableCorsAttribute. What should I be putting in for origin, headers and methods to make all of them work? (I just want to allow a request from anyone with...
View ArticleNew Post: CORS EnableCorsAttribute parameters to accept all like previous...
Now that it is required to pass the origin, headers and methods, how does one specify that you want to allow all origins, all headers and all methods? Thanks!
View ArticleCommented Unassigned: Weird issue using Web API with OData PageResult and...
Hi there,I tried implementing the code required to enable $inlinecount=allpages to return me the extra metadata in my Web API response required for server side paging including Count and NextPageLink...
View ArticleNew Post: CORS EnableCorsAttribute parameters to accept all like previous...
You can use "*" to allow all origins/headers/methods.[EnableCors("*", "*", "*")] Thanks, Yao
View ArticleEdited Issue: Currently if a HTTP method is not supported Web API returns a...
In the current version of Web API, when the action selector does not find a matching action for a HTTP method it returns a 404 status code even when the resource URI supports other methods (e.g. it...
View ArticleSource code checked in, #6bec1836c73e1e524f795c79594b988c12188670
Codeplex-899 - Razor parser returns incorrect data tree for section Given a section block like the following: @section a {something} The parser ends up creating the following tree: section transtion -...
View ArticleEdited Issue: Currently if a HTTP method is not supported Web API returns a...
In the current version of Web API, when the action selector does not find a matching action for a HTTP method it returns a 404 status code even when the resource URI supports other methods (e.g. it...
View ArticleCommented Unassigned: [WebApiOnOwin]Create a new interface for buffer policy...
Currently Web Api on Owin implementation uses IHostBufferPolicySelector interface defined in System.Web.Http, but I feel we should have a new interface going forward on Owin.When...
View ArticleCreated Unassigned: [WebPages]: Helper namespaces are not sanitized when the...
1) Create a new ASP.NET Web Pages site2) Under ~\App_Code\Bar, create a helper file Foo.cshtml3) Invoke the helper from a page as Bar.Foo.SomeHelperFunction()4) Rename the Bar folder to include a...
View ArticleEdited Issue: Razor parser returns incorrect data tree for @section a...
output returned by Razor parser for “@section a {something}” is as below. tree returned in incorrect.- block {Markup Block at (0:0,0)::33 (Gen:None)} System.Web.Razor.Parser.SyntaxTree.Block+ base...
View ArticleCommented Issue: Razor parser returns incorrect data tree for @section a...
output returned by Razor parser for “@section a {something}” is as below. tree returned in incorrect.- block {Markup Block at (0:0,0)::33 (Gen:None)} System.Web.Razor.Parser.SyntaxTree.Block+ base...
View ArticleSource code checked in, #8b65f6f102b9e336c605f24509bb8cf2d84b9694
Adding support for OData $select and $expand. Only ODataFormatter and Json Formatter work with this $select and $expand implementation. If you have [Queryable], $select and $expand should start working...
View ArticleCreated Unassigned: consider how nulls are represented with IEdmObject. [1014]
IEdmObject right now tracks entity instances only which are not nullable. Once, we add support for IEdmObject with complex types and collections, we have to figure out a way to represent null values as...
View ArticleCreated Unassigned: [OData]EntityInstanceContext.EntityInstance is obsolete....
Consider adding back compat support by trying to lazily initialize this property from EntityInstanceContext.EdmObject.Now that we support $select and $expand, we optimize the query that we generate to...
View Article