ASP.NET Web API

Announcement: This forum has been replaced by Visual Studio Developer Community to provide you one convenient and responsive system for all feedback. You can now suggest new ideas, browse and vote on existing ideas in the Visual Studio Developer Community.

We’d like your suggestions and ideas to help us continuously improve future releases of ASP.NET, so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

We look forward to hearing from you!
- The ASP.NET Team

Feedback on ASP.NET Web API

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

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".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Add ASP.NET MVC view generation features to ASP.NET Web API

    I think maintaining and working with ASP.NET MVC and ASP.NET Web API side by side in the same project is a drain on development resources and support cost.
    I would like to use ASP.NET Web API to generate Razor views via an additional NuGet package rather then relying on ASP.NET MVC.

    59 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Daniel Roth responded

    We plan to do work to better align ASP.NET MVC and Web API in our next release

  2. 48 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add a fluent OData query configuration API

    In the current release of OData Web API, security for queries is applied via the Queryable attribute or via ODataQueryOptions. The current system lacks any built-in method for restricting which fields can be used with the $filter query option. Implementing a trivial list of fields that support $filter is difficult, given that it can apply to relations.

    Instead, consider adding a "fluent" configuration API that captures this information at the entity level and allows orderby & filter to be "entity model aware" (for lack of a better term).

    For example,
    var settingsBuilder = ODataConventionSettingsBuilder();
    settingsBuilder.Entity<Order>().OrderByProperties("Id");
    settingsBuilder.Entity<Order>()
    .OrderByProperties({ "Id", "Name" }) …

    20 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  4. Make ApiDescription.ResponseDescription setter public

    It is impossible to provide a custom implementation of IApiExplorer because the setter for ApiDescription.ResponseDescription is internal. Please either make the setter public (or make the interface internal).

    16 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add System.Web.Http.ModelBinding.HttpPostedFileBaseModelBinder to mirror the System.Web.Mvc.HttpPostedFileBaseModelBinder

    The System.Web.Mvc.HttpPostedFileBaseModelBinder class works well.

    Can it be mirrored for the Web API

    15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide a way to easily Mock HttpRequestMessage for an ApiController

    Currently it is not easy to Mock or use a DI Container to inject HttpRequestMessage into an ApiController constructor. Therefore, if you are attempting to leverage any common functionality throughout the ApiController class (such as reading common Request Headers), you cannot accomplish this today because HttpRequestMessage is only available at the Method level and not at the time the class is constructed/instantiated. Being able to use DI and Mocking of HttpRequestMessage for an ApiController constructor would be tremendously useful and helpful.

    13 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support web.config transformations on build

    It appears that WebAPI projects do not automatically transform web.config files on build. After getting used to this for other .NET project types, it's difficult to make the exception in the case of WebAPI projects.

    7 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  8. Web API XML Serialization of DateTimeOffset in ISO 8601 format

    Web API 2 serialize DateTimeOffset as two different values:

    Datetime
    OffSetMinutes

    It should be serialized as a singlue value and in ISO 8601 format just like JsonMediaTypeFormatter does. There's a work around to have string property for every datetimeoffset property that you have in your model and would like to have as single value and in ISO 8601 format. It would be good if it is out of box support just like JsonMediaTypeFormatter.

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  9. Provide LowercaseUrls property for ASP.NET Web API

    In ASP.NET MVC, I am able to use the following line of code: routes.LowercaseUrls = true;

    However, this option is not available to me while using ASP.NET Web API. A similar option should be made available in ASP.NET Web API as well.

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  10. ApiExplorer - ApiDescriptions

    Make an option to set comparison (ApiDescriptionComparer) to fixing ambiguous route for versioning purpose (different namespace)

    /api/products
    /api/products

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Provide a native RouteVersion attribute

    Provide a native RouteVersion attribute for ASP.NET Web API that can be used to version ASP.NET Web API Controllers similar to what is outlined in this article: https://visualstudiomagazine.com/articles/2014/10/28/asp-net-mvc-5-1-new.aspx

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →

ASP.NET Web API

Feedback and Knowledge Base