2

In my MVC4 web app, I need to support multiple APIs. I looked around and apparently in Web API, Controllers with same name in different name spaces is not supported.

What are my options?

Ex: I want to be able to provide to my API consumers links like,

http://domainurl/api/api1/Students...
http://domainurl/api/api2/Students...

A Student Resource in api1 can be totally different from the one in api2. In such cases what is the best approach? I do not want to make it a single api and handle it through url parameters.

Brian
  • 1,337
  • 5
  • 17
  • 34
  • Ok. Looks like this is possible through Areas, as per [THIS POST](http://stackoverflow.com/questions/12025347/why-are-my-area-specific-web-apis-accessible-from-all-other-areas) but not sure how much tweaking is involved in my case. Any simpler solutions, please suggest. – Brian Nov 08 '12 at 21:36

1 Answers1

3

Maybe it might be better to seperate the 2 different APIs in to two different projects and have them worry about their own Apis.

  • MyApi.V1.csproj
  • MyApi.V2.csproj

Then have IIS point to the seperate versions using a virtual application

I think this is more manageable than smashing them into the same project file. Plus this will help each project out with reflection if you decide to use any resolvers.

Max Alexander
  • 5,471
  • 6
  • 38
  • 52
  • I believe that you are missing his point. It's not two version of the same API (for which your solution would make sense), but two different api that might share some (if not all) controller names. The MVC routes actually support that scenario by specifying the namespace in the route. – Sebastien F. Dec 22 '13 at 18:55
  • 1
    Oh. I would still have just branched/forked the next version and left V1's controller signatures unchanged except for bug fixes etc... V2 would be the continuation. (That's just me though...) – Max Alexander Dec 23 '13 at 03:45