Asp.Net WebAPI and AttributeRouting - no overloaded attribute constructor?

Question

I have just downloaded AttributeRouting NuGet package for WebAPI and having a problem within my controller. I thought the way to use it was to have something like:

 public class InboxController : ApiController
    {
        private IInboxService _inboxService;

        public InboxController(IInboxService inboxService)
        {
            _inboxService = inboxService;            
        }

        public IEnumerable<MessageModel> GetAll()
        {
            return _inboxService.GetAllMessages();
        }

      [HttpGet("Inbox/Count")]
            public int GetInboxCount()
            {
                return _inboxService.GetMessageCount();
            }
}

However I get the following error: Error 2 'System.Web.Http.HttpGetAttribute' does not contain a constructor that takes 1 arguments

I need to get this up and running fairly quickly. Is there any reason why the HttpGet attribute doesn't have an overloaded constructor?

UPDATE

    [GET("Inbox/EnquiryCount")]
    public EnquiryCountModel GetEnquiryCounts()
    {
        var model = new EnquiryCountModel();
        model.EnquiryCount = _inboxService.GetCustomerEnquiriesCount();
        model.EnquiryResponseCount = _inboxService.GetCustomerEnquiryResponseCount();
        return model;
    }

In routes:

routes.MapHttpRoute("InboxEnquiryApi", "api/inbox/{action}", new { Controller = "Inbox" }, null, new WebApiAuthenticationHandler(GlobalConfiguration.Configuration));

When I hit the URL at 'api/inbox/EnquiryCount' I get the this error:

**No HTTP resource was found that matches the request URI 'http://localhost:49597/api/inbox/enquirycount'**

GET works of course;) but am now getting multiple Multiple Actions Were Found that match the request error. I thought this was the whole point of this library. Can they not be mixed? — jaffa
– jaffa, Commented May 9, 2013 at 6:18
You need to understand how the ASP.NET Web API routing works internally. It works with url as a resource in mind. AttributeRouting just add a route, similar to global.asax routes. It cannot change the underlying engine. asp.net/web-api/overview/web-api-routing-and-actions — Imran Qadir Baksh - Baloch
– Imran Qadir Baksh - Baloch, Commented May 9, 2013 at 6:22

Kiran · Accepted Answer · 2013-10-21 17:06:46Z

6

Attribute routing is supported in Web api 2

Here is the details: http://www.asp.net/web-api/overview/web-api-routing-and-actions/attribute-routing-in-web-api-2

answered Oct 21, 2013 at 17:06

Kiran

1111 silver badge5 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

pat capozzi · Accepted Answer · 2014-05-29 02:11:15Z

6

This syntax has been changed in newer versions of the webapi. The [HTTPPOST] is now standalone and there is a new attribute for the route aptly name ROUTE which takes the route url eg.

[Route("GetRes/{month}")]

answered May 29, 2014 at 2:11

pat capozzi

1,4691 gold badge21 silver badges16 bronze badges

Collectives™ on Stack Overflow

Asp.Net WebAPI and AttributeRouting - no overloaded attribute constructor?

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related