Displaying 1 to 20 from 36 results

NSwag - The Swagger/OpenAPI toolchain for .NET, Web API and TypeScript.

  •    CSharp

NSwag is a Swagger/OpenAPI 2.0 and 3.0 toolchain for .NET, .NET Core, Web API, ASP.NET Core, TypeScript (jQuery, AngularJS, Angular 2+, Aurelia, KnockoutJS, and more) and other platforms, written in C#. The Swagger specification uses JSON and JSON Schema to describe a RESTful web API. The NSwag project provides tools to generate Swagger specifications from existing ASP.NET Web API controllers and client code from these Swagger specifications. The project combines the functionality of Swashbuckle (Swagger generation) and AutoRest (client generation) in one toolchain. This way a lot of incompatibilites can be avoided and features which are not well described by the Swagger specification or JSON Schema are better supported (e.g. inheritance, enum and reference handling). The NSwag project heavily uses NJsonSchema for .NET for JSON Schema handling and C#/TypeScript class/interface generation.

aspnet-api-versioning - Provides a set of libraries which add service API versioning to ASP

  •    CSharp

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.

Weapsy - ASP.NET Core CMS

  •    CSharp

Weapsy is an ASP.NET Core CMS based on DDD and CQRS. Please create issues to report bugs, suggest new functionalities, ask questions or just share your thoughts about the project. I will really appreciate your contribution, thanks.




Audit.NET - An extensible framework to audit executing operations in .NET and .NET Core.

  •    CSharp

An extensible framework to audit executing operations in .NET including support for .NET Framework ≥ 4.5 and NetCore ≥ 1.0 (NetStandard 1.3). Generate audit logs with evidence for reconstruction and examination of activities that have affected specific operations or procedures.

MyTested.WebApi - Fluent testing framework for ASP.NET Web API 2.

  •    CSharp

MyTested.WebApi is a unit testing library providing easy fluent interface to test the ASP.NET Web API 2 framework. It is testing framework agnostic, so you can combine it with a test runner of your choice (e.g. NUnit, xUnit, etc.). Inspired by ChaiJS. Please see the documentation for full list of available features. Everything listed in the documentation is 100% covered by more than 800 unit tests and should work correctly. Almost all items in the issues page are expected future features and enhancements.

Jason

  •    

Jason is an infrastructure framework to easly put the "Command" part of CQRS on top of WCF

Sample Security Application

  •    

A sample security application that uses Microsoft Account (Identity Provider), WebAPI (Service Layer) and EntityFramework (Data Access Layer).


ABP-ASP

  •    CSharp

这也是算是一种学习的方法和态度吧,经常去学习和总结,写下一点对于ABP(ABP是“ASP.NET Boilerplate Project (ASP.NET样板项目)”的简称)框架的理解和运用.

platform-status - Project Platform Status

  •    Javascript

Platform Status gives developers a cross-platform and cross-browser roadmap for browser features, from standardization and development to release. Not only a channel to raise awareness, it can also drive adoption and improve the vital feedback loop Firefox's platform needs to have with web developers. For most developers it will be a reference to discover and learn, but it has the potential to provide the entry points for radical participation on Mozilla's platform development.Existing web compatibility references, like caniuse focus on cross-browser compatibility but don't cover un-released features and lag behind on features that already shipped. Major browser vendors (Edge, Chrome, Webkit) are publicising their own platform status with references to their bug tracking and bug owners. Similar to Platform Status' goal, Chrome tracks consensus/enthusiasm from other browsers using sources that range from bugs, to IRC logs to tweets.

dotnet-fake-json-server - Fake REST API for prototyping or as a CRUD backend

  •    CSharp

Fake JSON Server is a Fake REST API that can be used as a Back End for prototyping or as a template for a CRUD Back End. Fake JSON Server also has an an experimental GraphQL query and mutation support.If you don't have .NET installed, you can run the server with Docker.

hapi-webapi - Implements abstraction for Hapi in TypeScript that makes it similar to ASP

  •    TypeScript

Implements an abstraction for Hapi using TypeScript, that provides a similar pattern to the ASP.NET WebApi framework for implementing Apis on Hapi. To get started quickly, you can clone the 'hapi-webapi-seed' repository, which includes all files needed to get started with TypeScript and the hapi-webapi.

saule - JSON API library for ASP.Net Web API 2.

  •    CSharp

Deserialization works just like in normal Web API; you don't need to do anything special to make this work.

javascript-conference-2017-nodejs-typescript - Repository with the code sample for the talk "Modern Web APIs with Node

  •    TypeScript

Run npm i to install all necessary packages. Run npm start to start the application. Please take a look at both controllers for all available routes.

webapi.link - Web API links with short urls

  •    

This page contains short url links of Web APIs and link to documents for web developers.

webapi-router - create restful api with the same feeling of Asp.Net WebApi based on Koa

  •    TypeScript

Dont need write the annoying koa.use(...). Instead, webapi-router will auto use the controller file path for router path. Also, use decorator @GET(path) can indicate the router path directly.