Error in VSTS:
3 error(s), 1 warning(s)
Phase 1 - 3 error(s), 1 warning(s)
Version in "/opt/vsts/work/1/s/docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
/usr/local/bin/docker-compose failed with return code: 1

Remove explicitly copied dependencies, copy entire solution
into the conainter and depends on the cache to reduce build
time.

Addd temporary solution file which does not contains the
dcproj file to work around the issue that the dotnet cli
cannot handle dcproj.

Also some config tweaking on windows

Removing docker-compose.windows.override (not needed as is identical to docker-compose.override)

Use current branch as tag

Redis and rabbitmq images now are not created when executing built. We force to  pull them  from docker hub.

Redis and rabbitmq images now are not created when executing built. We force to  pull them  from docker hub.

docker-use-platform creates mark file

Fixes #51

Until adding these, the project would not build correctly on a Mac.

script working for SPA

Add execute permissions to build-bits.sh on macOS

fix a rebase / automatic merge issue.

Somehow, the MVC image got in there twice.

update content nodes

Bug workaround for for the CLI. It turns out that the CLI does not
handle content nodes that have multiple paths. Instead, multiple nodes
are needed.

use the standard names for the web docker images.

fix a typo and update the csproj content listings.

Also, execute nom install as part of publishing  the spa application.

Solves #47

with Retry with Exponential Backoff

Everything works as exepcted except SPA version which need further adjustments

SQL databases with the same prefix for services
Move application tier to api tier in ordering api

Orders: Detail Query, new field in OrderDetail..
Identity: Validations in Register View, ensure all claims are returned in user end point..