NancyFx
JsonApiDotNetCore
Our great sponsors
NancyFx | JsonApiDotNetCore | |
---|---|---|
5 | 7 | |
7,141 | 652 | |
- | 2.1% | |
1.3 | 9.2 | |
almost 4 years ago | 7 days ago | |
C# | C# | |
Common Development and Distribution License 1.1 | 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.
NancyFx
-
Ask HN: Examples of Top C# Code?
Nancyfx - sadly dead in the water now but well worth a read of both the code and docs https://github.com/NancyFx/Nancy/tree/master/
-
what do you guys think about nancy
2-3 years ago Nancy added a large banner at the top of https://github.com/NancyFx/Nancy -
-
Microsoft, please open-source Web Forms 🚫⬇️🚌
Being open source doesn't change the support model. It allows willing contributors to step up and fork in the event of total abandonment. As a comparison, nobody forked NancyFx to extend support or keep it alive.
-
C# web framework without .net??
It sounds like you are talking about asp.net? If you don't want to bother with controllers and attributes and all that you can just use the Microsoft.AspNetCore.Http and Microsoft.AspNetCore.Routing namespaces. As someone that really liked Nancy I felt that this was close enough.
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?
ServiceStack - Thoughtfully architected, obscenely fast, thoroughly enjoyable web services for all
AutoMapper - A convention-based object-object mapper in .NET.
FFImageLoading - Fast & Furious Image Loading - Image loading, caching & transforming library for Xamarin and Windows
GraphQL for .NET - GraphQL for .NET
Nelibur - Message based webservice framework on the pure WCF
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.
EmbedIO - A tiny, cross-platform, module based web server for .NET
Breeze - Breeze for C#, F#, and VB.NET client applications
Mobius: C# API for Spark - C# and F# language binding and extensions to Apache Spark
eisk.webapi - Project based on latest .NET (v6.0) technologies for building scalable web api, along with clean architecture patterns.