Failed to generate Angular Service Proxy into Azure Pipeline build stage

Question

Failed to generate Angular Service Proxy into Azure Pipeline build stage

Al Amran 356

The deployment of an ASP.NET Core application consists of a backend using the ABP framework and a frontend built with Angular, stored in a single repository on Azure DevOps. A YAML pipeline has been configured to deploy both components to separate Azure Web Apps (Windows). The backend app deploys successfully, but the frontend app fails to build and release correctly.

Key Requirement: Before building the Angular app, the proxy must be generated using the ABP CLI. The pipeline does not generate this proxy during execution, which is essential for type safety and IntelliSense support in Angular when handling API calls.

Below is the YAML script configuration for the pipeline:

# ASP.NET

# Build and test ASP.NET projects.
# Add steps that publish symbols, save build artifacts, deploy, and more:

trigger:
  branches:
    include:
      - develop
variables:
  solution: '**/*.sln'
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release'
  angularDir: 'angular'
  outputDir: 'dist/app'

stages:
- stage: __default
  jobs:
  - job: Job
    pool:
      vmImage: 'windows-latest'
    steps:
    - task: UseDotNet@2
      inputs:
        packageType: 'sdk'
        version: '8.0.x'
        installationPath: $(Agent.ToolsDirectory)/dotnet
      displayName: 'Install .NET 8 SDK'
    - task: NodeTool@0
      inputs:
        versionSpec: '20.x'
      displayName: 'Install Node.js'
    - task: CmdLine@2
      displayName: 'Install Yarn'
      inputs:
        script: |
          npm install -g yarn
        workingDirectory: '$(Build.SourcesDirectory)'
    
    # Run ABP CLI from cmd.exe to generate Angular proxy
    - task: CmdLine@2
      inputs:
        script: |
          cd angular
          echo Installing ABP CLI and generating proxy...
          call dotnet tool install -g Volo.Abp.Cli --version 8.1.2
          abp generate-proxy -t ng -u
      displayName: 'Load ABP Proxy with CLI'
    
    - script: |
        cd angular
        echo "Installing Angular dependencies via npm..."
        ng config -g cli.packageManager yarn
        yarn add @angular/cli
        yarn add install-peers
        ng build --configuration production
      workingDirectory: '$(angularDir)'
      displayName: 'NPM Build Angular App'

      displayName: 'Prepare Artifact for Publishing'
    - task: PublishBuildArtifacts@1
      inputs:
        pathToPublish: '$(Build.ArtifactStagingDirectory)'
        artifactName: 'angular-clientportal'
      displayName: 'Publish Angular Build Artifact'

Durga Reshma Malthi 11,400 Microsoft External Staff Moderator

Hi Al Amran

Use a local installation of the ABP CLI in the Angular project instead of a global one.

- task: CmdLine@2
  inputs:
    script: |
      cd angular
      echo Installing ABP CLI and generating proxy...
      dotnet new tool-manifest
      dotnet tool install Volo.Abp.Cli --version 8.1.2
      dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url>
  displayName: 'Load ABP Proxy with CLI'

Replace <your-backend-url> with your actual backend app URL (including /api if required).

Instead of CmdLine@2 (Windows shell), you can also use PowerShell@2 for consistency:

- task: PowerShell@2
  inputs:
    targetType: 'inline'
    script: |
      cd angular
      dotnet new tool-manifest
      dotnet tool install Volo.Abp.Cli --version 8.1.2
      dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url>
  displayName: 'Generate Angular Proxy using ABP CLI'

Hope this helps!

Please Let me know if you have any queries.

Al Amran 356 Reputation points

2025-07-02T14:27:46.2733333+00:00

Hello @Durga Reshma Malthi

We tried your suggested solution but does not resolved the issue and can't create angular proxy container in the expected destination directory.

If we run from Cmdline, getting below error:

If we run from PowerShell@V2, getting below error:

Thanks for your prompt response.

Regards,
Amran

Durga Reshma Malthi 11,400 Microsoft External Staff Moderator

Hi Al Amran

Make sure your angular.json has a valid "defaultProject" set. If not, the CLI won’t know where to place the generated proxy.

You can also try explicitly passing the target project:

abp generate-proxy -t ng --target YourAngularProjectName

Or use the schematic directly:

ng generate @abp/ng.schematics:proxy-add --target=YourAngularProjectName --source=YourAngularProjectName
```Alternatively, try the below steps:

1. Ensure Node.js and yarn are installed and then add the below step before calling `abp generate-proxy`:

   ```yaml
   - script: |
       cd angular
       echo Installing dependencies for ABP proxy generation...
       yarn install
       yarn add -D @abp/ng.schematics
     displayName: 'Install ABP Angular Schematics'

After this add the below script and try again.

   - task: CmdLine@2
     inputs:
       script: |
         cd angular
         echo Installing ABP CLI and generating proxy...
         dotnet new tool-manifest
         dotnet tool install Volo.Abp.Cli --version 8.1.2
         dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url>
     displayName: 'Load ABP Proxy with CLI'

Hope this helps!

Please Let me know if you have any queries.

Al Amran 356 Reputation points

2025-07-04T06:58:27.3233333+00:00

Hello @Durga Reshma Malthi
Thanks for your continuous response.

We have tried explicitly passing the target project but doesn't resolve the issue. After then we have tried to use the schematic directly and found below error,

After this, we have tried your suggested way to add manifest tool and local insatll of ABP CLI but it didn't help much. Getting below error,

Durga Reshma Malthi 11,400 Microsoft External Staff Moderator

Hi Al Amran

As per the 1st screenshot, those are warnings, you can ignore.

If you're still hitting an issue when executing the schematic or ABP CLI, then

Add This Task (Before Proxy Generation):

- task: CmdLine@2
  inputs:
    script: |
      cd angular
      echo Installing Yarn dependencies...
      call yarn install
      echo Installing ABP Angular schematics...
      call yarn add -D @abp/ng.schematics@8.1.2
      echo Verifying ABP schematic install...
      dir node_modules/@abp/ng.schematics
    workingDirectory: '$(Build.SourcesDirectory)'
  displayName: 'Install ABP Angular Schematics'

Add This Task (To Generate Proxy):

- task: CmdLine@2
  inputs:
    script: |
      cd angular
      echo Creating .NET local tool manifest...
      dotnet new tool-manifest
      echo Installing ABP CLI...
      dotnet tool install Volo.Abp.Cli --version 8.1.2
      echo Running ABP CLI to generate Angular proxy...
      dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url> --no-cache
      echo Proxy generation finished.
    workingDirectory: '$(Build.SourcesDirectory)'
  displayName: 'Generate Angular Proxy via ABP CLI'

After Proxy Step: Build Angular App:

- task: CmdLine@2
  inputs:
    script: |
      cd angular
      echo Building Angular app...
      call yarn build --configuration production
    workingDirectory: '$(Build.SourcesDirectory)'
  displayName: 'Build Angular Frontend'

As per 2nd screenshot, use PowerShell@2 instead of CmdLine@2:

- task: PowerShell@2
  inputs:
    targetType: 'inline'
    script: |
      cd angular
      dotnet new tool-manifest
      dotnet tool install Volo.Abp.Cli --version 8.1.2
      dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url>
    workingDirectory: '$(Build.SourcesDirectory)'
  displayName: 'Generate ABP Proxy with CLI via PowerShell'

Hope this helps!

Please Let me know if you have any queries.

Al Amran 356 Reputation points

2025-07-04T08:45:20.38+00:00

Hello @Durga Reshma Malthi

I have tried your suggested orders tasks according to CmdLine and PowerShell but doesn't resolve the issue. Proxy is not generated as following message,

Thanks for your continuous support.

Accepted answer

0 additional answers

Your answer

Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-07-02T13:40:06.4366667+00:00

Hi Al Amran

Use a local installation of the ABP CLI in the Angular project instead of a global one.

- task: CmdLine@2 inputs: script: | cd angular echo Installing ABP CLI and generating proxy... dotnet new tool-manifest dotnet tool install Volo.Abp.Cli --version 8.1.2 dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url> displayName: 'Load ABP Proxy with CLI'

Replace <your-backend-url> with your actual backend app URL (including /api if required).

Instead of CmdLine@2 (Windows shell), you can also use PowerShell@2 for consistency:

- task: PowerShell@2 inputs: targetType: 'inline' script: | cd angular dotnet new tool-manifest dotnet tool install Volo.Abp.Cli --version 8.1.2 dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url> displayName: 'Generate Angular Proxy using ABP CLI'

Hope this helps!

Please Let me know if you have any queries.
Al Amran 356 Reputation points

2025-07-02T14:27:46.2733333+00:00

Hello @Durga Reshma Malthi

We tried your suggested solution but does not resolved the issue and can't create angular proxy container in the expected destination directory.

If we run from Cmdline, getting below error:

If we run from PowerShell@V2, getting below error:

Thanks for your prompt response.

Regards,
Amran
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-07-03T07:55:17.9033333+00:00

Hi Al Amran

Make sure your angular.json has a valid "defaultProject" set. If not, the CLI won’t know where to place the generated proxy.

You can also try explicitly passing the target project:

abp generate-proxy -t ng --target YourAngularProjectName

Or use the schematic directly:

ng generate @abp/ng.schematics:proxy-add --target=YourAngularProjectName --source=YourAngularProjectName ```Alternatively, try the below steps: 1. Ensure Node.js and yarn are installed and then add the below step before calling `abp generate-proxy`: ```yaml - script: | cd angular echo Installing dependencies for ABP proxy generation... yarn install yarn add -D @abp/ng.schematics displayName: 'Install ABP Angular Schematics'

After this add the below script and try again.
- task: CmdLine@2 inputs: script: | cd angular echo Installing ABP CLI and generating proxy... dotnet new tool-manifest dotnet tool install Volo.Abp.Cli --version 8.1.2 dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url> displayName: 'Load ABP Proxy with CLI'

Hope this helps!

Please Let me know if you have any queries.
Al Amran 356 Reputation points

2025-07-04T06:58:27.3233333+00:00

Hello @Durga Reshma Malthi
Thanks for your continuous response.

We have tried explicitly passing the target project but doesn't resolve the issue. After then we have tried to use the schematic directly and found below error,

After this, we have tried your suggested way to add manifest tool and local insatll of ABP CLI but it didn't help much. Getting below error,
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-07-04T08:03:00.6433333+00:00

Hi Al Amran

As per the 1st screenshot, those are warnings, you can ignore.

If you're still hitting an issue when executing the schematic or ABP CLI, then

Add This Task (Before Proxy Generation):

- task: CmdLine@2 inputs: script: | cd angular echo Installing Yarn dependencies... call yarn install echo Installing ABP Angular schematics... call yarn add -D @abp/ng.schematics@8.1.2 echo Verifying ABP schematic install... dir node_modules/@abp/ng.schematics workingDirectory: '$(Build.SourcesDirectory)' displayName: 'Install ABP Angular Schematics'

Add This Task (To Generate Proxy):

- task: CmdLine@2 inputs: script: | cd angular echo Creating .NET local tool manifest... dotnet new tool-manifest echo Installing ABP CLI... dotnet tool install Volo.Abp.Cli --version 8.1.2 echo Running ABP CLI to generate Angular proxy... dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url> --no-cache echo Proxy generation finished. workingDirectory: '$(Build.SourcesDirectory)' displayName: 'Generate Angular Proxy via ABP CLI'

After Proxy Step: Build Angular App:

- task: CmdLine@2 inputs: script: | cd angular echo Building Angular app... call yarn build --configuration production workingDirectory: '$(Build.SourcesDirectory)' displayName: 'Build Angular Frontend'

As per 2nd screenshot, use PowerShell@2 instead of CmdLine@2:

- task: PowerShell@2 inputs: targetType: 'inline' script: | cd angular dotnet new tool-manifest dotnet tool install Volo.Abp.Cli --version 8.1.2 dotnet tool run abp generate-proxy -t ng --url https://<your-backend-url> workingDirectory: '$(Build.SourcesDirectory)' displayName: 'Generate ABP Proxy with CLI via PowerShell'

Hope this helps!

Please Let me know if you have any queries.
Al Amran 356 Reputation points

2025-07-04T08:45:20.38+00:00

Hello @Durga Reshma Malthi

I have tried your suggested orders tasks according to CmdLine and PowerShell but doesn't resolve the issue. Proxy is not generated as following message,

Thanks for your continuous support.

Answer 1

Durga Reshma Malthi 11,400 Microsoft External Staff Moderator

Hi Al Amran

As we discussed in private message, after trying this script - frontend.txt, ABP proxy was successfully generated.

However, you mentioned: "I can’t see the proxy directory in Azure Repos" "No dist/ClientPortal in the artifact".

This is expected behavior. Azure Pipelines does not commit generated files back to your Git repository unless you explicitly add a step. So, you won’t see the src/app/proxy folder in Azure Repos, unless you commit it manually.

Firstly, Open angular/angular.json and look for defaultProject and check if it is missing or set incorrectly.

Normally it should be like this:

{
  "$schema": "...",
  "defaultProject": "ClientPortal", // <-- Check this
  "projects": {
    "ClientPortal": {
      "architect": {
        "build": {
          "options": {
            "outputPath": "dist/ClientPortal"  // <-- Confirm this matches your YAML

If your angular.json uses:

"defaultProject": "app"

Then adjust the build command to:

call yarn build app --configuration production

then fix in yaml pipeline if needed,

In your pipeline:

variables:
  outputDir: 'dist/ClientPortal'

To confirm angular build path, add this debug step:

- script: |
    echo "Listing Angular build output..."
    dir angular/dist
  displayName: 'Inspect Angular Build Output'

If the folder is angular/dist/client-portal (lowercase or different casing), update your outputDir variable accordingly.

Hope this helps!

Please Let me know if you have any queries.

Al Amran 356 Reputation points

2025-08-20T07:56:08.2366667+00:00
Hello @Durga Reshma Malthi

I hope you are doing good.

Still we are facing challenges to build the angular app. Can we connect Azure SQL DB to execute dotnet run command to run the DBmigrator project using CONNECTION_STRING(adding in variable groups)like below way?

variables: - group: frontend

- task: PowerShell@2 displayName: 'Run migrations' inputs: workingDirectory: '$(System.DefaultWorkingDirectory)/src/myapp.DbMigrator' targetType: 'inline' script: | dotnet run -- "$(CONNECTION_STRING)"

We are getting error,
##[error]Unhandled exception. Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I have checked the MS Docs and found below,

steps:

task: SqlAzureDacpacDeployment@1 inputs: azureSubscription: 'YourServiceConnectionName' # Use your Azure SQL Database service connection serverName: '<your-server-name>.database.windows.net' databaseName: '<your-database-name>' deployType: 'DacpacTask' authenticationType: 'server' sqlUsername: '$(sqlUsername)' sqlPassword: '$(sqlPassword)'

If we add this task like that way, wre don't need any **Database Deployment Task.
**
Please suggest.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-20T15:53:44.0433333+00:00
Hi Al Amran

To connect your Azure SQL Database and run the dotnet run command for your DB migrator project, you need to ensure that your connection string is correctly configured and that your Azure SQL Database allows connections from your Azure DevOps pipeline.

Make sure your connection string is correctly formatted and includes all necessary parameters. Azure SQL Database connection string looks like this:

Server=tcp:<your-server-name>.database.windows.net,1433;Initial Catalog=<your-database-name>;Persist Security Info=False;User ID=<your-username>;Password=<your-password>;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

If you are using variable groups in Azure DevOps, ensure that the CONNECTION_STRING variable is correctly set up in the variable group and is being referenced properly in your YAML file.

CONNECTION_STRING = Server=tcp:your-sql-server.database.windows.net,1433;Initial Catalog=your-db;User ID=$(sqlUsername);Password=$(sqlPassword);Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

Your YAML pipeline should look something like this:

variables: - group: frontend steps: - task: PowerShell@2 displayName: 'Run migrations' inputs: workingDirectory: '$(System.DefaultWorkingDirectory)/src/MAS.FloraFire.ClientPortal.DbMigrator' targetType: 'inline' script: | dotnet run -- "$(CONNECTION_STRING)"

If your Azure SQL DB is behind a private endpoint, your pipeline agent must be running in a self-hosted agent inside the same VNet. Or using Managed DevOps Pools with Private Endpoint support. Otherwise, the hosted agent won’t be able to reach the DB.

If you want to deploy your database schema without running the migrations manually, you can use the SqlAzureDacpacDeployment@1 task as you mentioned. This task can handle the deployment of your database schema directly from a .dacpac file.

steps: - task: SqlAzureDacpacDeployment@1 inputs: azureSubscription: 'YourServiceConnectionName' # Use your Azure SQL Database service connection serverName: '<your-server-name>.database.windows.net' databaseName: '<your-database-name>' deployType: 'DacpacTask' authenticationType: 'server' sqlUsername: '$(sqlUsername)' sqlPassword: '$(sqlPassword)' dacpacFile: '$(System.DefaultWorkingDirectory)/path/to/your.dacpac' # Specify the path to your .dacpac file

Hope this helps!

Please Let me know if you have any queries.
Al Amran 356 Reputation points

2025-08-20T19:12:56.8+00:00
Hello @Durga Reshma Malthi

Please be informed that I am using variable groups in Azure DevOps, ensure that the CONNECTION_STRING variable is correctly set up in the variable group and is being referenced properly in my YAML file.

The connection string is correctly formatted and includes all necessary parameters. Azure SQL Database connection string looks like this:

Server=tcp:<your-server-name>.database.windows.net,1433;Initial Catalog=<your-database-name>;Persist Security Info=False;User ID=<your-username>;Password=<your-password>;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

Azure SQL DB is not configured behind any private endpoint but it's configured with selected Public networks via allowing required site Public IP addresses and enabled below options.

Allow Azure services and resources to access this server: When enabled, other resources within the Azure boundary can access SQL Database. For example, an Azure Virtual Machine can access the SQL Database resources.

We don't want to use SqlAzureDacpacDeployment@1 task. I am just thinking to add this task for connecting the Azure SQL DB without deployment of our database schema.

variables: - group: frontend

steps: - task: SqlAzureDacpacDeployment@1 inputs: azureSubscription: 'YourServiceConnectionName' # Use your Azure SQL Database service connection serverName: '<your-server-name>.database.windows.net' databaseName: '<your-database-name>' deployType: 'DacpacTask' authenticationType: 'server' sqlUsername: '$(sqlUsername)' sqlPassword: '$(sqlPassword)' dacpacFile: '$(System.DefaultWorkingDirectory)/path/to/your.dacpac' # Specify the path to your .dacpac file

If the SqlAzureDacpacDeployment@1 task serves Azure SQL DB connectivity, then I might able to run dotnet run coomand to run DBMigrator project but still getting the same error,

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.

We are using the task as like below but it's not resolved.

variables: - group: frontend - task: SqlAzureDacpacDeployment@1 inputs: azureSubscription: 'Pay-As-You-Go(dd*****-b822-4511-bbff-*********)' serverName: '$(SqlServerName)' databaseName: '$(SqlDatabaseName)' deployType: InlineSqlTask authenticationType: 'server' sqlUsername: '$(SqlUser)' sqlPassword: '$(SqlPassword)' - task: PowerShell@2 displayName: 'Run migrations' inputs: workingDirectory: '$(System.DefaultWorkingDirectory)/src/myapp.DbMigrator' targetType: 'inline' script: | dotnet run -- "$(CONNECTION_STRING)"

Note: SqlAzureDacpacDeployment@1 task is completed successfully.

Does that mean Azure SQL Database connectivity is working from Azure Pipeline from Microsoft Hosted Agent?

Why are we getting the same network related error, when running the below inline command from powershell@2?

dotnet run -- "$(CONNECTION_STRING)"

Please provide your suggestion.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-20T21:30:05.3633333+00:00
Hi Al Amran

Yes, SqlAzureDacpacDeployment@1 success means Azure SQL is reachable from Microsoft-hosted agent. But your dotnet run failure means the DbMigrator is not using the same working credentials or firewall access.

ASP.NET Core apps typically read connection strings from environment variables or appsettings.json. So, update your YAML like this:

- task: PowerShell@2 displayName: 'Run migrations' inputs: workingDirectory: '$(System.DefaultWorkingDirectory)/src/myapp.DbMigrator' targetType: 'inline' script: | $env:ConnectionStrings__DefaultConnection = "$(CONNECTION_STRING)" dotnet run

And also make sure your DbMigrator project is configured to read from IConfiguration like this:

var connectionString = configuration.GetConnectionString("DefaultConnection");

Hope this helps!

Please Let me know if you have any queries.
Al Amran 356 Reputation points

2025-08-21T06:04:26+00:00
Hello @Durga Reshma Malthi

I have executed this task earlier like your suggested way but still throwing error,

- task: PowerShell@2 displayName: 'Run migrations' inputs: workingDirectory: '$(System.DefaultWorkingDirectory)/src/myapp.DbMigrator' targetType: 'inline' script: | $env:ConnectionStrings__DefaultConnection = "$(CONNECTION_STRING)" dotnet run

Which file to add below variables?

var connectionString = configuration.GetConnectionString("DefaultConnection");

In the DBmigrator project=>

Below is the code of appsettings.json that might be pointed other SQL server and database which is local. I will check with the dev team regarding this.

I think appsettings.json causes the problem. Can you please confirm?
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-21T16:00:33.33+00:00
Hi Al Amran

Yes, you are right appsettings.json causing the problem.

From your screenshot of appsettings.json, I see this:

"ConnectionStrings": { "Default": "Server=..\\SQLDEVELOPER;Database=ClientPortal;Trusted_Connection=True;TrustServerCertificate=true" }

This points to a local SQL Server instance (\\.\\SQLDEVELOPER) using Windows Authentication (Trusted_Connection=True). When your DbMigrator runs in Azure Pipelines, it tries to connect to this unreachable local server, that's why it fails with network-related error since the hosted agent doesn’t have that local instance.

You need to ensure that your DbMigrator project prefers the environment variable over the value in appsettings.json.

If your DbMigrator reads:

var connectionString = configuration.GetConnectionString("Default");

or you can make sure like this:

var configuration = new ConfigurationBuilder() .SetBasePath(Directory.GetCurrentDirectory()) .AddJsonFile("appsettings.json", optional: true) .AddEnvironmentVariables() .Build(); var connectionString = configuration.GetConnectionString("Default");

then you must set the env var like this in your pipeline:

- task: PowerShell@2 displayName: 'Run migrations' inputs: workingDirectory: '$(System.DefaultWorkingDirectory)/src/myapp.DbMigrator' targetType: 'inline' script: | # Override appsettings.json connection string $env:ConnectionStrings__Default = "$(CONNECTION_STRING)" dotnet run

Your YAML is correct:

$env:ConnectionStrings__Default = "$(CONNECTION_STRING)" dotnet run

Just make sure the variable name matches exactly Default in both the code and the YAML.

Confirm with your dev team that DbMigrator calls configuration.GetConnectionString("Default"). If yes, then this fix will solve the pipeline error.

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-22T15:46:36.92+00:00

Hi Al Amran

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Al Amran 356 Reputation points

2025-08-22T16:43:54.1+00:00

Hello @Durga Reshma Malthi

I have forwarded the issue to our dev team. They will get back to me by Wednesday of Next Week.

Thanks for your continuos support to me.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-22T16:53:11.34+00:00

Hi Al Amran

Thanks for your update.
Al Amran 356 Reputation points

2025-08-25T13:12:56.2766667+00:00

@Durga Reshma Malthi

Many thanks for your excellent support. Run the DBMigrator project successfully.

After keeping the same version of @ABP/ng.schematics@8.1.2 and Volo.Abp.Cli version 8.1.2, generating the Angular service proxy. Then the Angular application build is completed successfully. We have followed your suggested ways to modify the pipeline scripts.

Best Regards,
Amran

Share via

Failed to generate Angular Service Proxy into Azure Pipeline build stage

0 additional answers

Your answer