Dotnet is not building

[AfandiM]

Using commit a434b57, I cannot build the dotnet agent:

=> ERROR [build 7/8] RUN dotnet publish "DotNet.Backchannel.Master.csproj" -c Release -o /app/publish                                                                                                                      2.3s
------
 > [build 7/8] RUN dotnet publish "DotNet.Backchannel.Master.csproj" -c Release -o /app/publish:
#0 0.683 Microsoft (R) Build Engine version 16.7.3+2f374e28e for .NET
#0 0.683 Copyright (C) Microsoft Corporation. All rights reserved.
#0 0.683 
#0 0.950   Determining projects to restore...
#0 1.476   All projects are up-to-date for restore.
#0 2.249 Features/BasicMessage/DefaultBasicMessageService.cs(9,50): error CS1514: { expected [/aries-framework-dotnet/src/Hyperledger.Aries/Hyperledger.Aries.csproj]
#0 2.249 Features/BasicMessage/DefaultBasicMessageService.cs(52,2): error CS1513: } expected [/aries-framework-dotnet/src/Hyperledger.Aries/Hyperledger.Aries.csproj]
#0 2.249 Features/BasicMessage/IBasicMessageService.cs(4,50): error CS1514: { expected [/aries-framework-dotnet/src/Hyperledger.Aries/Hyperledger.Aries.csproj]
#0 2.249 Features/BasicMessage/IBasicMessageService.cs(19,2): error CS1513: } expected [/aries-framework-dotnet/src/Hyperledger.Aries/Hyperledger.Aries.csproj]
------
Dockerfile.dotnet:39
--------------------
  37 |     
  38 |     COPY dotnet/server .
  39 | >>> RUN dotnet publish "DotNet.Backchannel.Master.csproj" -c Release -o /app/publish
  40 |     
  41 |     FROM base AS final
--------------------
ERROR: failed to solve: process "/bin/sh -c dotnet publish \"DotNet.Backchannel.Master.csproj\" -c Release -o /app/publish" did not complete successfully: exit code: 1
Docker image build failed.

Please advise

@swcurran Concerning the EDX course lab Lab: Aries Agent Test Harness

[swcurran]

Thanks. I noticed the other day that the ReadMe references the .NET Backchannel, and it is now longer operational. I’ll be updating the ReadMe to remove it. The other backchannels are still operational and maintained, and AATH remains a going concern. I appreciate the reminder.