Skip to main content

Build and Run the application

The API generated consists of configuration to be run locally or on a docker container.

Build and run locally

Move to the <PROJECT-NAME>/src/api folder and run the next commands in Command Prompt or Powershell

dotnet build
# Note that the template engine will rename your paths, so change the command accordingly
dotnet run --project xxAMIDOxx.xxSTACKSxx.API/xxAMIDOxx.xxSTACKSxx.API.csproj
Potential issue on some Windows installations

Depending on how deep your folder structure is you might encounter a problem where you cannot build the project. This happens because of our dependency on Pact for our contract tests.

The error looks something like this

Error MSB3491 Path: File exceeds the OS max path limit. The fully qualified file name must be less than 260 characters.

There are two fixes possible so far:

  • You must enable long file paths on Windows by following the instructions here
  • Create your folder on an upper level where the paths won't exceed 260 characters

Build and run in docker container

From the <PROJECT-NAME>/src/api folder, build a Docker image using e.g. the command below:

Build docker image
docker build -t dotnet-api .

This uses the Dockerfile in this folder to generate the Docker image.

After the creation of the Docker image, the Docker container can be run using the command below:

Run docker container
docker run -p 5000:80 --mount type=bind,source=/path/to/PROJECT-NAME/src/api/xxAMIDOxx.xxSTACKSxx.API/appsettings.json,target=/app/config/appsettings.json -e COSMOSDB_KEY=your-key -e SERVICEBUS_CONNECTIONSTRING=your-asb-connection-string -e EVENTHUB_CONNECTIONSTRING=your-aeh-connection-string -e STORAGE_CONNECTIONSTRING=your-aeh-storage-connection-string  dotnet-api:latest`

The COSMOSDB_KEY described in the command above has to be passed when running the container. SERVICEBUS_CONNECTIONSTRING OR EVENTHUB_CONNECTIONSTRING and STORAGE_CONNECTIONSTRING are needed based on the configuration and message service you'll be using. Note that the appsettings.json value is mounted here for running locally, but not if the full project is deployed to Azure, where the build process will perform the substitution.

Verify that the application has started
Relationship between domain and path

Keep in mind that if you've changed the domain (original being Menu), the path will reflect that. If your domain is Foo. Then the path will be ../v1/foo instead of ..v1/menu etc.

Browse to http://localhost:5000/v1/menu. This should return a valid JSON response.

The application configuration uses Swagger/OAS3 to represent the API endpoints. The Swagger UI can be viewed by directing your browser to http://localhost:5000/swagger/index.html.