asp.net-web-api

问题 I have 2 API routes for my API atm, but I want to add more, and the way I am doing it it seems to overwrite each other, so in the code I pasted, only the CreateUser route works. public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapHttpRoute( name: "CreateUser", routeTemplate: "api/{controller}/{cUser}", defaults: new { controller = "User", action = "CreateUser", cUser = RouteParameter.Optional }); routes.MapHttpRoute( name:

问题 What is the best way to create a simple REST API in Visual Studio 2013 using ASP.NET MVC. I just want something with controllers and route config along with any other basic requirements for a HTTP REST API. I don't require any Razor view engine, Javascript or HTML inclusions. How can I create a project without all the unwanted extras, which I usually remove in the past? Thank you. 回答1: It's all in the template you select. In the New Project dialog, select ".NET Framework 4.5" if not already

问题 I'm having problems trying to decide on a route to take on a project I have. I've been reading up on OWIN specs and Katana implementation within .NET. The reason why I'd like to go with the Katana route is because of the owin components associated with ADFS and Token/Cookie generation. I have two projects, one for MVC 5 website, and one for Web API. They may rest of two separate servers in the future, but for now they are on the same. I know I will be using IIS, so the Owin pipeline isn't

问题 I am receiving the following VM on a Web API Post action public class ViewModel { public string Name { get; set; } [Required] public int? Street { get; set; } } When I make a post I get the following error: Property 'Street' on type 'ViewModel' is invalid. Value-typed properties marked as [Required] must also be marked with [DataMember(IsRequired=true)] to be recognized as required. Consider attributing the declaring type with [DataContract] and the property with [DataMember(IsRequired=true)]

问题 I am using AngularJS with ASP.NET Web Api server side. Seems to me like authentication has now become a breeze? Or is this too good to be true? So I'm thinking of using the Web Api's "Individual User Accounts" authentication. And I am thinking that is all I need. As long as every request is authenticated and noone can get any data they shouldn't I shouldn't need to do much more right? Or am I missing some key security fundamentals? 回答1: When it comes to securing the API you have two main

问题 In modern web-projects that use RESTful API's we often see AJAX-calls like the one below littered around our JavaScript-files. $.ajax({ type: "POST", url: myapp.baseUrl + 'Api/Note', data: ko.mapping.toJSON(note), contentType: 'application/json', }).done(function (response) { // do something }).fail(function (jqxhr) { // do something else }); I love WebAPI, I love Knockout and I love tying the two together. However these AJAX-calls are quite verbose and contain all kinds of details that I am

问题 OData endpoint is created using ASP.NET Web API 2.0 Trying to create a Query Interceptor in the ODataController like shown in the below code: public class AVMItemController : ODataController { ADWAppContext sampleADW = new ADWAppContext("Server=XXX;Database=XXX;User ID=XXX;password=xxx;Trusted_Connection=false;Encrypt=true"); // GET: odata/AVM [EnableQuery(PageSize=25)] public IQueryable<ADWAppContext.AVMItem> GetAVMItems() { return sampleADW.AVMItems.AsQueryable<ADWAppContext.AVMItem>(); }

问题 I looked up up the documentation for ASP.NET Web API parameter binding, they seem to have either fromURI and fromBody only. Is it possible to do both? Here is some background info. I'm creating a webhook receiver/handler, where I have control over which URL is the webhook, but I do not have control over what the payload will be like until later stage of the workflow, so I need to take it in as JSON string first. My hope is to be able to set up the route that can take in querystring and also

问题 I looked up up the documentation for ASP.NET Web API parameter binding, they seem to have either fromURI and fromBody only. Is it possible to do both? Here is some background info. I'm creating a webhook receiver/handler, where I have control over which URL is the webhook, but I do not have control over what the payload will be like until later stage of the workflow, so I need to take it in as JSON string first. My hope is to be able to set up the route that can take in querystring and also

问题 Given the following ASP.NET Web API application Target: .NET Framework 4.6.1 Hosted as Azure App Service I wish to restrict the total number of concurrent HTTP requests to the application. I have looked at https://github.com/stefanprodan/WebApiThrottle but that seems to be focused on different use cases. I would like the equivalent of this setting in IIS: https://forums.asp.net/t/1683143.aspx?Max+concurrent+requests 回答1: This is to avoid attacking a backend service in counterproductive ways.