2. Default API<\/i> version without url path versioning<\/h3>\n
Let’s start with the initial setup of API<\/i> versioning which will work for every type of versioning apart from url path versioning. All you have to do is to assign an ApiVersionSelector<\/i> and set the AssumeDefaultVersionWhenUnspecified<\/i> property to true.<\/p>\n Now when the user will try to access the endpoint without specifying version explicitly the ApiVersionSelector<\/i> will select proper version – in this case highest available version. <\/p>\n Running the same configuration against controllers which are versioned via url path (not query string)<\/p>\n will result with 404<\/i> status code, as routing is not able to match the url. attribute to versioned controllers. From now on we can access our API<\/i> without specifying version as well as with version specified. If you don\u2019t want to specify default route manually for every controller, you can do it via application model convention. The interesting thing about it is the fact that apart from changing existing values of application model we can also add new items to it. This means that we can add additional SelectorModel<\/i> with our default route to Selectors’<\/i> collection<\/p>\n Now we can get rid of [Route(“[controller]”)]<\/i> attribute from our versioned controllers and just rely on convention which can be added as follows<\/p>\n\r\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n \/\/ Add framework services.\r\n services.AddApiVersioning(options =>\r\n {\r\n options.ApiVersionReader = new QueryStringApiVersionReader();\r\n options.AssumeDefaultVersionWhenUnspecified = true;\r\n options.ApiVersionSelector = new CurrentImplementationApiVersionSelector(options);\r\n });\r\n}\r\n<\/pre>\n3. Default Api version with URL path versioning<\/h3>\n
\r\nnamespace AspNetCoreDefaultApiVersionAndRoutePrefix.Controllers.V1\r\n{\r\n [Route(\"v{version:apiVersion}\/[controller]\")]\r\n [ApiVersion(\"1\")]\r\n public class ValuesController : Controller\r\n {\r\n \/\/ GET api\/values\r\n [HttpGet]\r\n public IEnumerable
\n![\"404\"](\"\/\/tpodolak.com\/blog\/wp-content\/uploads\/2017\/05\/asp-net-core-default-api-version-with-url-path-versioning\/404.png\")
<\/a>
\nFortunately, unlike the ASP.NET Web API<\/i>, ASP.NET Core<\/i> allows us to have multiple route attributes applied to given controller, so in order to fix the issue we just have to add <\/p>\n\r\n[Route(\"[controller]\")]\r\n<\/pre>\n
\n![\"after\"](\"\/\/tpodolak.com\/blog\/wp-content\/uploads\/2017\/05\/asp-net-core-default-api-version-with-url-path-versioning\/after.png\")
<\/a><\/p>\n4. Adding default route with convention<\/h3>\n
\r\npublic class DefaultRoutePrefixConvention : IApplicationModelConvention\r\n{\r\n public void Apply(ApplicationModel application)\r\n {\r\n foreach (var applicationController in application.Controllers)\r\n {\r\n applicationController.Selectors.Add(new SelectorModel\r\n {\r\n AttributeRouteModel = new AttributeRouteModel\r\n {\r\n Template = \"[controller]\"\r\n }\r\n });\r\n }\r\n }\r\n}\r\n<\/pre>\n\r\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n \/\/ rest of the code omitted for brevity \r\n services.AddMvc(mvc =>\r\n {\r\n mvc.Conventions.Add(new DefaultRoutePrefixConvention());\r\n });\r\n}\r\n<\/pre>\n