GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → microsoft → Aspnet Api Versioning

microsoft / Aspnet Api Versioning

Licence: mit
Provides a set of libraries which add service API versioning to ASP.NET Web API, OData with ASP.NET Web API, and ASP.NET Core.

Programming Languages

C#
18002 projects

Labels

aspnetcoreversioningwebapiaspnetodataversioning-semantics

Projects that are alternatives of or similar to Aspnet Api Versioning

aspnet-api-versioning
Provides a set of libraries which add service API versioning to ASP.NET Web API, OData with ASP.NET Web API, and ASP.NET Core.
Stars: ✭ 2,396 (+11.23%)
Mutual labels:  aspnetcore, aspnet, versioning, webapi, odata, versioning-semantics
Nswag
The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
Stars: ✭ 4,825 (+124%)
Mutual labels:  webapi, aspnetcore, aspnet
Awesome Microservices Netcore
💎 A collection of awesome training series, articles, videos, books, courses, sample projects, and tools for Microservices in .NET Core
Stars: ✭ 865 (-59.84%)
Mutual labels:  aspnetcore, aspnet
Aspnetcore Vue
Sample setup on using asp.net core 2.1 + vue cli 3 in one project. This sample is deprecated and rolled into https://github.com/soukoku/AspNetCore.SpaServices.VueCli
Stars: ✭ 31 (-98.56%)
Mutual labels:  aspnetcore, aspnet
Aspnetcore.docs
Documentation for ASP.NET Core
Stars: ✭ 9,940 (+361.47%)
Mutual labels:  aspnetcore, aspnet
Nopcommerce
The most popular open-source eCommerce shopping cart solution based on ASP.NET Core
Stars: ✭ 6,827 (+216.95%)
Mutual labels:  aspnetcore, aspnet
Weapsy
ASP.NET Core CMS
Stars: ✭ 748 (-65.27%)
Mutual labels:  webapi, aspnetcore
Aspnetcore Vue Starter
*NEW* Asp.net Core & Vue.js (ES6) SPA Starter kit - Vuex, webpack, Web API, Docker, and more! By @TrilonIO
Stars: ✭ 1,182 (-45.13%)
Mutual labels:  aspnetcore, aspnet
Aspnet Core 3 Jwt Authentication Api
ASP.NET Core 3.1 JWT Authentication API
Stars: ✭ 443 (-79.43%)
Mutual labels:  aspnetcore, aspnet
Simple aspnet auth
Simple ASP.NET Authorisation boilerplate project. No EF, no database, no IdentityServer4 just a basic logging in system for both cookies and JWT and a controller with a set of examples.
Stars: ✭ 105 (-95.13%)
Mutual labels:  aspnetcore, aspnet
Aspnetboilerplate
ASP.NET Boilerplate - Web Application Framework
Stars: ✭ 10,061 (+367.08%)
Mutual labels:  aspnetcore, aspnet
Raygun4net
Raygun provider for .NET
Stars: ✭ 107 (-95.03%)
Mutual labels:  webapi, aspnet
Cleanarchitecture.webapi
An implementation of Clean Architecture for ASP.NET Core 3.1 WebAPI. Built with loosely coupled architecture and clean-code practices in mind.
Stars: ✭ 615 (-71.45%)
Mutual labels:  webapi, aspnetcore
Dotvvm
Open source MVVM framework for Web Apps
Stars: ✭ 523 (-75.72%)
Mutual labels:  aspnetcore, aspnet
Csla
A home for your business logic in any .NET application.
Stars: ✭ 865 (-59.84%)
Mutual labels:  aspnetcore, aspnet
Server
The core infrastructure backend (API, database, Docker, etc).
Stars: ✭ 8,797 (+308.4%)
Mutual labels:  aspnetcore, aspnet
Huxley
JSON proxy for the UK National Rail Live Departure Board SOAP API
Stars: ✭ 123 (-94.29%)
Mutual labels:  webapi, aspnet
Aspnetcore Webapi Sample
This is a sample ASP.NET Core WebAPI
Stars: ✭ 310 (-85.61%)
Mutual labels:  webapi, aspnetcore
Aspnetcore Webapi Course
Professional REST API design with ASP.NET Core 3.1 WebAPI
Stars: ✭ 323 (-85%)
Mutual labels:  webapi, versioning
Aspnetcore Ddd
Full ASP.NET Core 3.1 LTS application with DDD, CQRS and Event Sourcing
Stars: ✭ 88 (-95.91%)
Mutual labels:  webapi, aspnetcore
View All Similar Projects ➔

Build status

ASP.NET API Versioning

ASP.NET API versioning gives you a powerful, but easy-to-use method for adding API versioning semantics to your new and existing REST services built with ASP.NET. The API versioning extensions define simple metadata attributes and conventions that you use to describe which API versions are implemented by your services. You don't need to learn any new routing concepts or change the way you implement your services in ASP.NET today.

The default API versioning configuration is compliant with the versioning semantics outlined by the Microsoft REST Guidelines. There are also a number of customization and extension points available to support transitioning services that may not have supported API versioning in the past or supported API versioning with semantics that are different from the Microsoft REST versioning guidelines.

The supported flavors of ASP.NET are:

  • ASP.NET Web API ( nuget | quick start | samples )
    Adds service API versioning to your Web API applications

  • ASP.NET Web API and OData ( nuget | quick start | samples )
    Adds service API versioning to your Web API applications using OData v4.0

  • ASP.NET Core ( nuget | quick start | samples )
    Adds service API versioning to your ASP.NET Core applications

  • ASP.NET Core and OData ( nuget | quick start | samples )
    Adds service API versioning to your ASP.NET Core applications using OData v4.0

This is also the home of the ASP.NET API versioning API explorers that you can use to easily document your REST APIs with Swagger:

  • ASP.NET Web API Versioned API Explorer ( nuget | quick start | samples )
    Replaces the default API explorer in your Web API applications

  • ASP.NET Web API with OData API Explorer ( nuget | quick start | samples )
    Adds an API explorer to your Web API applications using OData v4.0

  • ASP.NET Core Versioned API Explorer ( nuget | quick start | samples )
    Adds additional API explorer support to your ASP.NET Core applications

  • ASP.NET Core with OData API Explorer ( nuget | quick start | samples )
    Adds additional API explorer support to your ASP.NET Core applications using OData v4.0

You can find additional samples, documentation, and getting started instructions in the wiki.

Discussion

Have a general question, suggestion, or other feedback? Check out how you can contribute.

Reporting security issues and bugs

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

If you are an existing user, please makes sure you review the release notes between all major and minor package releases.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].