RESTServices.Framework 1.5.2

dotnet add package RESTServices.Framework --version 1.5.2
NuGet\Install-Package RESTServices.Framework -Version 1.5.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="RESTServices.Framework" Version="1.5.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add RESTServices.Framework --version 1.5.2
#r "nuget: RESTServices.Framework, 1.5.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install RESTServices.Framework as a Cake Addin
#addin nuget:?package=RESTServices.Framework&version=1.5.2

// Install RESTServices.Framework as a Cake Tool
#tool nuget:?package=RESTServices.Framework&version=1.5.2

REST-service component is a server-side framework that allows easy creation and working with HTTP and REST services within any ASP.NET application, including capability to work with backend server-side .NET code via REST or HTTP services from client-side javascript or other types of client code. Once a REST-service is defined it can be consumed via regular URL, or using client-side javascript call that resembles the standard C# style function call that is expected to be used within server-side code calling the same method. The REST-service can return any type of data, such as string, byte array, reference to a file that should be sent to a client as a call response, etc. In addition HTML templates functionality can be utilized by building an ascx file template (like regular web user controls) and data model that REST-service method is supposed to return – the framework will process ASCX template by applying data model to it and returning its result to the client. The REST-service framework also provides control over security, and has built-in configuration that is 100% controlled by a developer, including ability to use class alias instead of real class to hide the internal namespaces and classes’ structure used by the server code backend.

Disclaimer: The main purpose of building this framework was to allow the creation of HTTP or REST services in such a way that is easy to use, easy to setup, to not be limited by returned type of data, and making sure that the internal application code can be reused for service purposes. Although a number of measures were taken, it was not the goal to achieve 100% compatibility with the RESTful architecture.

Product Compatible and additional computed target framework versions.
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.5.2 4,676 3/23/2013
1.4.0 2,265 9/9/2012

Before using component: register *.REST extension at IIS by adding script map as described in the documentation.
v.1.5.2 now has support for the route registration via special at class or method level. It also provides ability to set filter priority enabling control of the order in which filters would be applied to incoming request.