bitplatform
aspnet-api-versioning
| bitplatform | aspnet-api-versioning | |
|---|---|---|
| 3 | 12 | |
| 1,019 | 2,992 | |
| 1.8% | 1.2% | |
| 9.9 | 8.7 | |
| 4 days ago | 11 days ago | |
| C# | C# | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bitplatform
- bit platform’s 104th release (v6.0.0)
-
Dotnet.World.News(Wednesday, September, 20, 2023)
🔴🔥 [Blazor] BitPlatform version 5.6.0 is here! See what's new, [BitPlatform Github] 😎
-
Having both Web and App form a single codebase!!!
Did you know you can have a true cross-platform Blazor app (Web, Android, iOS, MacCatalyst, MacCocoa, Tizen, WinUI, WPF and Linux) with high-performance components using BitPlatform?
aspnet-api-versioning
-
Web API Versioning - 'apiVersion' constraint
Here is a code example
- Best way to version a CQRS-oriented REST api
- How do you handle API versioning? And naming.
- Is this a common way to version REST apis
-
Angular, ASP.NET core web api, and DTOs
- The DTOs on the server should generally not change without warning. A deprecation cycle should ideally be in place so consumers can keep up over time and front end development doesn't have to be lock-step with the services the consume. Ideally some period of time between service v1 being deprecated and service v2 being required to allow consumers to react ( in this case, you're the consumer, so be kind to yourself ). Deets: https://github.com/dotnet/aspnet-api-versioning
-
8 quick tips to improve your .NET API
This API versioning can be parameterized with some options, including the default version or even how the versioning will be done, whether by URL, header or media type. For more details, you can access the official documentation.
-
Entity Changes and API Versioning - Looking for best practice
https://github.com/dotnet/aspnet-api-versioning/tree/master/samples/aspnetcore/BasicSample/Controllers something like this
-
API version control (route name error)
Could you not achieve what you want by using ASP.NET API versioning - there's a by namespace example here
-
.NET Core — API Versioning
A lista completa pode ser vista aqui: https://github.com/microsoft/aspnet-api-versioning/wiki/Version-Format
-
Web API in 5 Hours (2021)
You don't have to use attributes. You can use conventions. See here.
What are some alternatives?
Ididit - C# .NET 7 Blazor habit tracker application. Works on Web, Windows, Linux, Android, iOS and macOS.
api-guidelines - Microsoft REST API Guidelines
TheLastTime - C# .NET 5 Blazor WebAssembly Progressive Web Application that tracks when was the last time you did something
CleanArchitecture - Clean Architecture Solution Template for ASP.NET Core
Mapster - A fast, fun and stimulating object to object Mapper
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
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. [Moved to: https://github.com/dotnet/aspnet-api-versioning]
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
dotnet-podcasts - .NET reference application shown at .NET Conf featuring ASP.NET Core, Blazor, .NET MAUI, Microservices, Orleans, Playwright, and more!
ApiVersioningSwagger - Api Versioning Swagger example
Blazor-WASM-Identity-gRPC - Blazor WASM, IdentityServer4 with Multiple Roles, Additional User Claim(s) & gRPC Roles Authorization
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework