I can't see your usings so please make sure that you're using [System.Web.Http.HttpGet] as opposed to System.Web.Mvc.HttpGet.

When you do that this URL should work:

/umbraco/api/MediaApi/GetMediaById/?id=2303

I added my usings to my code above. This is what is inconsistent. The first method in the controller works. Any other one, even if I do a hard coded return doesn't.

This for example:

 public MediaApiModel GetMediaTest(int mediaTypeAlias) {
        return new MediaApiModel { MediaId = 000, MediaUrl = "monkey" };
    }

Should return something but comes up as 404.

So /umbraco/api/MediaApi/GetMediaTest/?mediaTypeAlias=1234 returns a 404?

I'd recommend you put [System.Web.Http.HttpGet] on the GetMediaTest and GetMediaById methods to make sure it's listening for the correct type of HttpGet.

The VS version should not matter at all, it just compiles to the same dll.

Your exact code above works for me when going to /umbraco/api/MediaApi/GetMediaTest/?mediaTypeAlias=1234 so there must be something strange going on in your solution. I am out of suggestions though.. No idea what that could be I'm afraid.

Here's my test solution, maybe you can find something that's different from yours: https://dl.dropboxusercontent.com/u/3006713/WebApplication30.zip

Hey Sebastiaan,

Thanks for the sample project. So what I noticed in this zip file is that it appears that when the controllers are created, they are somehow "registered" with the application. I'm saying registered since I don't know how else to explain it. They are identified in some way where they can be accessed later.

Simply taking your sample, adding a new method to the controller, rebuilding, it comes up 404. The previous methods still work but the new one is unknown. Between your project and mine, I'm not seeing any major differences in the web.config or package.config files that would make this not work for me. I don't know where else to look I'm spot checking around and I'm not seeing anything.

So I guess where to go from here is when a controller is created, where do its methods get "registered" with the application? How does it know that this controller should be accessible? Is there a way to edit the list of methods the controller has accessible? Like a config file or dll associated with the controller? I really don't know since whatever it is, it seems to be created automatically for everyone else but in my project(s) it is not.

Umbraco takes care of that.. And it works by writing : UmbracoApiController

So you're saying that you added a file in the controllers folder in my sample project with a class that inherits from UmbracoApiController and you can not use it?

Are you sure you don't have any code in your site that alters the routing table?

Also, can you list all the content of the file you added to the project here please?

I'm not doing anything to change the default routing.

So just working in the sample project I added a new controller into the controllers folder.

using System.Web.Http;
using Umbraco.Web.WebApi;

namespace WebApplication30.Controllers
{
    public class MediaGetterController : UmbracoApiController
    {
        [HttpGet]
        public MediaApiModel GetMediaTest2(int id)
        {
            return new MediaApiModel { MediaId = 000, MediaUrl = "monkey" };
        }

        public class MediaApiModel
        {
            public int MediaId;
            public string MediaUrl;
        }
    }
}

This returns a 404.

Going back to the original controller "MediaApiController" I changed an argument in the "GetMediaTest" method from "mediaTypeAlias" to "id". This doesn't update when I rebuild and run the site. It only works if I use the old argument in the query string which doesn't even appear in the controller.

using System.Web.Http;
using Umbraco.Web.WebApi;

namespace WebApplication30.Controllers
{
    public class MediaApiController : UmbracoApiController
    {
        [HttpGet]
        public MediaApiModel GetMediaById(int id)
        {
            var media = Umbraco.TypedMedia(id);
            return new MediaApiModel
            {
                MediaId = media.Id,
                MediaUrl = media.Url
            };
        }

        [HttpGet]
        public MediaApiModel GetMediaTest(int id)
        {
            return new MediaApiModel { MediaId = 000, MediaUrl = "monkey" };
        }

        public class MediaApiModel
        {
            public int MediaId;
            public string MediaUrl;
        }
    }
}

I did notice that the sample project has a dll of the same name as the project. None of my other attempts create that. If I delete that dll from the bin folder, it does not get recreated and the original controller ceases operation.

Ok, I figured it out. Reinstalled VS, created a new application using the sample project, and its good ad gold now.

Thanks!

is working on a reply...