Restier is an API development framework for building standardized, OData V4 based RESTful services on .NET.

Restier is the spiritual successor to WCF Data Services. Instead of generating endless boilerplate code with the current Web API + OData toolchain, RESTier helps you boostrap a standardized, queryable HTTP-based REST interface in literally minutes. And that's just the beginning.

Like WCF Data Services before it, Restier provides simple and straightforward ways to shape queries and intercept submissions before and after they hit the database. And like Web API + OData, you still have the flexibility to add your own custom queries and actions with techniques you're already familiar with.

OData stands for the Open Data Protocol. OData enables the creation and consumption of RESTful APIs, which allow resources, defined in a data model and identified by using URLs, to be published and edited by Web clients using simple HTTP requests.

OData was originally designed by Microsoft to be a framework for exposing Entity Framework objects over REST services. The first concepts shipped as "Project Astoria" in 2007. By 2009, the concept had evolved enough for Microsoft to announce OData, along with a larger effort to push the format as an industry standard.

Work on the current version of the protocol (V4) began in April 2012, and was ratified by OASIS as an industry standard in Feb 2014.

Now that the project has restarted, we have a new location for our Continuous Integration builds. We've simplified the NuGet packages as well, so now you can just reference Microsoft.Restier.AspNet or Microsoft.Restier.AspNetCore (coming soon) packages, and we'll take care of the rest.

Coming Soon!

Restier 1.0 currently ships with support for Classic ASP.NET 5.2.7 and later. Support for .NET 5 and later is coming in the second half of 2021.

The Classic ASP.NET flavor of Restier is made up of the following components:

• Microsoft.Restier.AspNet: Plugs into the OData/WebApi processing pipeline and provides query interception capabilities.
• Microsoft.Restier.Core: The base library that contains the core convention-based interception framework.
• Microsoft.Restier.EntityFramework: Translates intercepted queries down to the database level to be executed.
• Microsoft.Restier.Breakdance: Unit test Restier services and components in-memory without spnning up a separate IIS instance.

Restier is used in solutions from:

• BurnRate.io
• CloudNimble, Inc.
• Florida Agency for Health Care Administration
• Miller's Ale House

There is also a growing set of tools to support Restier-based development

• Breakdance.Restier: Convention-based name troubleshooting and integration test support.

After a couple years in statis, Restier is in active development once again. The project is lead by Robert McLaws and Mike Pizzo.

The core development team meets twice a month on Microsoft Teams to discuss pressing items and work through the issues list. A history of those meetings can be found in the Wiki.

If you'd like to help out with the project, our Contributor's Handbook is also located in the Wiki.

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter. You can also find these instructions in this repo's SECURITY.md.

Special thanks to everyone involved in making RESTier the best API development platform for .NET. The following people have made various contributions to the codebase: