Issue I remember from ASP.NET Web API that it’s sufficient to prefix Web API REST method names with HTTP commands (e.g. GetList() => HTTP GET, Delete() => HTTP DELETE) to have incoming calls appropriately routed. I also remember that in
Continue readingTag: asp.net-web-api-routing
[SOLVED] Issue after deploying ASP.NET Web API to production
Issue I tested ASP.NET Web API in local environment with IIS Express and on other server with full IIS. At both places, token api and post api is working fine. I am using System.Web.Http namespace as suggested. However, after deploying
Continue reading[SOLVED] Issue after deploying ASP.NET Web API to production
Issue I tested ASP.NET Web API in local environment with IIS Express and on other server with full IIS. At both places, token api and post api is working fine. I am using System.Web.Http namespace as suggested. However, after deploying
Continue reading[SOLVED] HttpGetAttribute name property not working for routing
Issue I have a WebAPI controller named WeatherForecast with one operation. The operation method looks like follow: [HttpGet(Name = "GetWeatherForecast")] public IEnumerable<WeatherForecast> Get() { return Enumerable.Range(1, 5).Select(index => new WeatherForecast { Date = DateTime.Now.AddDays(index), TemperatureC = Random.Shared.Next(-20, 55), Summary =
Continue reading