office-file-api-in-web-api-app
JsonApiDotNetCore
| office-file-api-in-web-api-app | JsonApiDotNetCore | |
|---|---|---|
| 1 | 7 | |
| 1 | 658 | |
| - | 2.0% | |
| 6.1 | 9.2 | |
| 6 months ago | 3 days 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
JsonApiDotNetCore
-
Ask HN: Nested Resources in REST/HTTP API URLs?
Well, that might be true when implementing from the scratch, but using a standard often also means, that someone has implemented a well known library to get rid of the boilerplate and basic decisions.
I personally often use jsonapi.net[1], a C# implementation of JSONAPI. This supports OpenAPI/Swagger with swashbuckle, has a very good filtering implementation and together with Orbit.js[2] it is pretty much without having to decide many things...
[1]: https://www.jsonapi.net/
- Ask HN: What's is your go to toolset for simple front end development?
- Recommendation reading (books/blogs) for best practices while designing REST APIs
-
Composing and nesting with JsonApiDotNetCore
It's so powerful that it even allows you to establish relationships between operations within a single request, using something called local IDs. Work is progressing quickly on the atomic-operations branch. Check it out on Github if you want to follow along.
-
Relationships
In our previous post we setup a basic JSON:API compliant API with the 4.0 release of the JsonApiDotNetCore framework. You can find the code we wrote under the part-1 branch on Github.
What are some alternatives?
StoreCleanArchitecture-NET - This is a basic project to demonstrate an introduction about the implementation of Clean Architecture on .NET
ServiceStack - Thoughtfully architected, obscenely fast, thoroughly enjoyable web services for all
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
FFImageLoading - Fast & Furious Image Loading - Image loading, caching & transforming library for Xamarin and Windows
eisk.webapi - Project based on latest .NET (v6.0) technologies for building scalable web api, along with clean architecture patterns.
NancyFx - Lightweight, low-ceremony, framework for building HTTP based services on .Net and Mono. Note: This project is no longer maintained and has been archived.
PeakLimsApiSample - 🧬 A complex DDD based web API to model the accessioning workflow within a LIMS.
GraphQL for .NET - GraphQL for .NET
Hot Chocolate - Welcome to the home of the Hot Chocolate GraphQL server for .NET, the Strawberry Shake GraphQL client for .NET and Banana Cake Pop the awesome Monaco based GraphQL IDE.
Breeze - Breeze for C#, F#, and VB.NET client applications
X.Web.Sitemap - Simple sitemap generator for .NET and .NET Core