Skip to content

MVrest

MVrest publishes your MV BASIC subroutines as REST services, with full control over the data structures they return.

MVrest is architected differently from the MVsharp REST interface. The REST interface is a generic REST interface that lets you call subroutines, but its output cannot be tailored to complex object types. MVrest gives you full control to return complex data structures from a REST call.

The deployment mechanism is also different. MVrest is deployed on .NET Core 3.1 with an internally hosted HTTP pipeline, so no web server needs to be configured: the entire REST server is hosted in the application.

MVrest also generates a complete .NET Core 3.1 project with full source, so modifications can be made when specific requirements are not met by the generic REST interface.

Source changes are overwritten

If you modify the generated source code, all changes will be lost when you redeploy the services.

Quick start Create a REST service

Start here

  1. Follow the quick start
    Publish an example subroutine as a REST service from start to finish in the fewest steps.

  2. Check the prerequisites
    Install .NET Core 3.1, MVsharp and the MVrest Administrator, and learn which files MVrest creates in your account.

  3. Create your REST services
    Define classes that map to your data, define REST methods for your subroutines, and deploy the REST application.

  4. Manage the server
    Start and stop the server, reset connections and check connection status.

Explore the documentation

  • Get started


    A quick start that publishes an example subroutine end to end, plus prerequisites and the MvClasses and MvRestServices files.

    Quick start · Before you start

  • Creating REST services


    Classes, REST methods and deployment, with a worked invoice example.

    Creating REST services

  • Managing the server


    Start, stop, reset and monitor the MVrest server.

    Managing the server

Works with MVsharp

MVrest requires MVsharp 4.0.8.0 or later. See the MVsharp documentation.