2

I need some clarification on API versioning in .Net Core framework.

My client want the version to be handled in Router level. Like

[Route("1/[controller]")]
public class SampleController : Controller
{
    [HttpGet("version")]
    public IActionResult GetVersion()
    {
        return Ok({"Message": "API Version 1"});
    }
}

I access this using, https://www.somedomain.com/api/1/sample/version

In IIS, I will create an application called 'api' (The path 'api' in my URL will be taken care here) under default web site and host my code here.

In order to do API versioning, what is the better way that I can follow here.

  1. Can I do this?

    [ApiVersion("1")]
[Route("{version:apiVersion}/[controller]")]
public class SampleController : Controller
{
    [HttpGet("version")]
    public IActionResult GetVersion()
    {
       return Ok({"Message": "API Version 1"});
    }

    [HttpGet("version"), MapToApiVersion("2" )]
    public IActionResult GetVersion()
    {
        return Ok({"Message": "API Version 2"});
    }
}

  2. Is it possible to create an application under an application in IIS. Like,

Default Web Site - > api -> 1 -> Code without API version mentioned

Default Web Site - > api -> 2 -> Updated Code without API version mentioned

  1. Or can I create the versions as application in IIS and deploy the code under each applciation version. Like,

Default Web Site - > 1 -> Code without API version mentioned

Default Web Site - > 2 -> Updated Code without API version mentioned

This will end up in changing my API URL, which i don't prefer. I still want to go with the same URI.
I access this using, https://www.somedomain.com/api/1/sample/version

Please advise the best approach that I can follow here.

Improve this question
2
  • Do you have different projects for different versions of your api or do you have them in the same project? Commented Jan 4, 2017 at 10:13
  • I am still on version 1 of the API. I prefer to have same project. Commented Jan 4, 2017 at 10:17

4 Answers 4

Reset to default
1

Here is a popular repository that provides a set of libraries for adding API versioning to ASP.NET Web API, OData with ASP.NET Web API, and ASP.NET Core applications.

For ASP.NET Core applications, you can install this repository's ASP.NET Core API Versioning by running the following command in the Package Manager Console:

Install-Package Microsoft.AspNetCore.Mvc.Versioning
Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

Perhaps the Map extension method of ApplicationBuilder suits your needs : 

app.Map( "/1", myVersion1MappingFunction)

in the Configure method of Startup let myVersion1MappingFunction configure a separate middleware pipeline: 

private static void myVersion1MappingFunction( IApplicationBuilder app)
{
   // start your special middleware for version 1
   app.UseMvc( routes =>
   {
       routes.MapRoute( ... );
   }
}

On using Map extension the fragment ("/1") is removed from HttpRequest.Path

Improve this answer

Comments

0

If I understand you correctly are wanting to use URL Path Segment Versioning for ASP.NET Core. With that said in your examples you will NOT have separate website deployed. You have one website deployed and you do NOT create multiple applications for versioning under your default website.

With URL path segment versioning you have one web application and that application manages all routes using the ApiVersion convention. You will need to maintain the code in such a way that it can deliver old functionality with new functionality and manage all dependencies.

I would recommend reading what Microsoft has to say about this here and doing a simple proof of concept that makes sense for your implementation.

I hope this helps clear up your confusion about deploying the application multiple times for versioning.

Improve this answer

1 Comment

Small point of order. This is generally true, but you can split your application into multiple applications. To make that work, you'll almost certainly need a gateway to route to the correct application endpoint. To ensure that reporting API versions still works, you'll need to advertise the API versions from all applications. This is lightly discussed in this wiki topic. How you advertise your API versions or implement a gateway can vary greatly.
0

In your case the best method would be to employ the versioning from the web server level so you can have different deployments and a folder per version without specifying a version in the application routing itself. (your option 2/3?)

However since IIS merely proxies requests to kestrel with .net core unlike asp.net, you'll have to setup the reverse proxy by URL/URL Re-write with ARR to different versions of the deployment.

So you could have:

  1. /root/V1/
  2. /root/V2/
  3. etc... like you explain.

Each deployment would be running kestrel with different ports numbers and IIS would re-verse proxy to them by URL.

Here is an article on how to setup ARR with url-write. it's written with asp.net in mind, but it's the same principal:

          Reverse Proxy with URL Rewrite v2 and Application Request Routing

Improve this answer

1 Comment

In the realm of APIs, this is dangerous assumption. There is no guarantee, explicit or implied, that two API versions are compatible. Many service authors assume that if things are backward compatible to them that clients will be fine. That is simply not true. A server cannot guarantee that the client uses a tolerant reader or is otherwise backward compatible. Simply changing /api from /api/v1 to /api/v2 is likely to break clients. This behavior is fine UIs and browsers because they all to understand application/html.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.