ASP.NET Web API
Feedback on ASP.NET Web API
There are two ways to get more votes:
- When an admin closes an idea you've voted on, you'll get your votes back from that idea.
- You can remove your votes from an open idea you support.
- To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
Enter your idea and we'll search to see if someone has already suggested it.
If a similar idea already exists, you can vote and comment on it.
If it doesn't exist, you can post your idea so others can vote on it.
Enter your idea and we'll search to see if someone has already suggested it.
- Hot ideas
- Top ideas
- New ideas
-
Execution Order of Mvc4 WebApi Action Filters
There is no way to forecast the execution order of WebApi Action Filters. It changes randomly each time the code is changed. It would be nice to have an integer property to control the order like in normal Mvc controllers, but also respecting the order they are put on the action method would be acceptable
206 votes4 comments · Flag idea as inappropriate… · Admin →planned · AdminDaniel Roth (Admin, ASP.NET Future Feature Feedback) respondedSupport for filter ordering is tracked on our CodePlex site here: https://aspnetwebstack.codeplex.com/workitem/1065. Please add your vote to the CodePlex issue if you care about this feature!
-
OData V4 service should support DateTime
OData V4 should support DateTime or you should give the developer a way of converting datetime to datetimeoffset when the service is called.
I have several serializable objects that are in 3rd party libraries (even Microsoft core classes) that have datetime properties that will not be exposable through OData V4 services.here is OASIS meeting showing that Edm.DateTime was discussed as adding back but then was "defer this to a future version"?
https://issues.oasis-open.org/browse/ODATA-220https://aspnetwebstack.codeplex.com/workitem/2072
203 votesCheck!invalid email(thinking…)Resetor sign in withForgot password?Create a passwordI agree to the terms of serviceSigned in as (Sign out)CloseCloseYou have left! (?) (thinking…)16 comments · ASP.NET Web API · Flag idea as inappropriate… · Admin → -
Support Nested Routes
MVC has areas, which would work nicely for this. My thoughts behind this are that it's nice to package functionality as modules, and areas serve that purpose well in MVC apps. Of course, it would be nice to be able to host nested areas, as well.
162 votesCheck!invalid email(thinking…)Resetor sign in withForgot password?Create a passwordI agree to the terms of serviceSigned in as (Sign out)CloseCloseYou have left! (?) (thinking…)1 comment · Flag idea as inappropriate… · Admin →under review · AdminDaniel Roth (Admin, ASP.NET Future Feature Feedback) respondedSupport for nested routes/areas is now tracked on our CodePlex site here: https://aspnetwebstack.codeplex.com/workitem/1309. Please vote for this issue on CodePlex if it is important to you! We would also love to hear more about your specific scenarios, so please comment on the CodePlex issue with more details.
-
Support OutputCache on WebAPI calls
In ASP.NET MVC it easy to cache the output of a call by applying the outputcache attribute. A similar feature for WebAPI would help for cacheable resources.
157 votes