office-file-api-in-web-api-app
ApiEndpoints
| office-file-api-in-web-api-app | ApiEndpoints | |
|---|---|---|
| 1 | 22 | |
| 1 | 2,996 | |
| - | - | |
| 6.1 | 4.3 | |
| 6 months ago | about 2 months ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | 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.
office-file-api-in-web-api-app
-
Create a Web API Application with our Office File API (Powered by the platform-agnostic DevExpress.Drawing Graphics Engine)
To help illustrate what's possible, I created an Office File API in Web API apps sample solution. Please refer to the following link for more information: Office File API - Use DevExpress Office File API Libraries (at the backend) for your Web-API Applications
ApiEndpoints
- Web apis with controllers but whats the other way
-
Does anyone like minimal API?
I personally prefer the API Endponts project that doesn’t get the love it deserves. It’s really the best of both worlds. It breaks each endpoint up into one file to make it easier to manage and prevents ginormous Controllers.
-
Are minimal APIs meant to be used for lightweight projects or do they offer something controllers don't?
I personally think it feels "cleaner" when using the controllers instead because they provide more out of the box features. Having one endpoint per file is a nice thing so I'm thinking about using the ApiEndpoints ( https://github.com/ardalis/ApiEndpoints ) package.
-
Need help for refactoring my Controller
You can follow a "controller per endpoint" strategy. One good way to do it is with Steve Smith ApiEndpoints: https://github.com/ardalis/ApiEndpoints
- Need help understanding the purpose of MediatR in vertical slices architecture.
-
Thick or thin API controllers?
I'm not disputing the benefits of thin controllers but there are other ways to make the controllers thinner. For example, I could use libraries such as ApiEndpoints which allows me to have one handler class per REST endpoint. Basically, MediatR pattern but at the ASP.net level.
The only think I would suggest is to break endpoints into separate files via smth like this https://github.com/ardalis/ApiEndpoints
-
FastEndpoints v3.0 released with easy api versioning support!
You really should compare against https://github.com/ardalis/ApiEndpoints
-
FastEndpoints alternatives - ApiEndpoints and Carter
3 projects | 20 Jan 2022
- ASP.NET Core 6: Autenticación JWT y Identity Core
What are some alternatives?
JsonApiDotNetCore - A framework for building JSON:API compliant REST APIs using ASP.NET and Entity Framework Core.
FastEndpoints - A light-weight REST API development framework for ASP.NET 6 and newer.
StoreCleanArchitecture-NET - This is a basic project to demonstrate an introduction about the implementation of Clean Architecture on .NET
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
eisk.webapi - Project based on latest .NET (v6.0) technologies for building scalable web api, along with clean architecture patterns.
MediatR - Simple, unambitious mediator implementation in .NET
PeakLimsApiSample - 🧬 A complex DDD based web API to model the accessioning workflow within a LIMS.
IdentityServer4 - OpenID Connect and OAuth 2.0 Framework for ASP.NET Core
Carter - Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
AutoMapper - A convention-based object-object mapper in .NET.
Paket - A dependency manager for .NET with support for NuGet packages and Git repositories.