ariste.info
  • MSDyn365 & Azure DevOps ALM
  • Get my book!
  • ISV License Generator
  • About me
    • About me
    • Subscribe
    • Contact
  • Logo
  • LinkedIn

Unified experience ALM

  • Welcome to the new ALM guide
    • Introduction
    • Prerequisites
  • Create and prepare Azure DevOps organization and project
    • Create an Azure DevOps organization
    • Create an Azure DevOps project
    • Enable TFVC projects in Azure DevOps
    • Add CI/CD agents with an Azure subscription
  • Unified development environment
    • What are unified developer environments?
    • Transition to a capacity-based model
    • Deploying a unified developer environment using PowerShell
    • Deploy an UDE environment from PPAC
    • Upgrade version in a Unified Development Environment
    • Useful links
  • Using Visual Studio
    • Connect Visual Studio to your UDE
    • Deploy code to a Unified Development Environment
  • Pipelines
    • What’s new in the pipelines?

Legacy Guide

  • Welcome
    • Welcome!
  • Dynamics 365 for Finance & Operations & Azure DevOps
    • Intro
    • Package and model planning
    • Azure DevOps
    • First steps
    • The build server
    • Visual Studio
    • Some advice
    • Branching strategies
  • Azure Pipelines
    • Builds
    • Continuous integration
    • Gated check-ins
    • Set up the new Azure DevOps tasks for Packaging and Model Versioning
  • Azure hosted build for Dynamics 365 Finance & SCM
    • Intro
    • Azure agents
    • How does it work?
    • What do I need?
    • Azure DevOps artifacts
    • Prepare Azure DevOps
    • Configure pipeline
    • Update for version 10.0.18 and greater
  • Azure DevTest Labs powered builds
    • Intro
    • Azure DevTest Labs
    • Getting and preparing the VHD
    • Create a DevTest Labs account
    • Creating the VM
    • Preparing the VM
    • Create a new image
    • Azure DevOps pipelines
    • Run the build
    • Times
    • Show me the money
    • Some final remarks
  • Add and build .NET projects
    • Intro
    • Build .NET in your pipeline
    • Add a C# project to FnO
    • Build pipelinebui
    • Things I don’t like/understand/need to investigate
  • Release Pipelines
    • Intro
    • Setting up Release Pipeline in Azure DevOps for Dynamics 365 for Finance and Operations
    • AAD app creation
    • Create the release pipeline in DevOps
    • Creating the LCS connection
    • New Azure DevOps release tasks: MSAL authentication and ADAL deprecation
  • Automation
    • Update VMs using pipelines and d365fo.tools
    • Builds
    • Releases
    • But I like to add some human touch to it
    • Extra bonus
    • Update a variable in a release
  • LCS DB API
    • Call the LCS Database Movement API from your Azure DevOps Pipelines
    • Automating Prod to Dev DB copies
    • Restore a data package with Azure DevOps Pipelines
  • Secure your Azure Pipelines with Azure Key Vault
    • Azure Key Vault
    • Securing your Azure DevOps Pipelines
View Categories
  • ariste.info
  • Dynamics 365 F&O Dev ALM guide
  • Legacy Guide
  • Azure hosted build for Dynamics 365 Finance & SCM
  • Prepare Azure DevOps

Prepare Azure DevOps

El nuevo agente necesita una solución para compilar tus paquetes. Esto quiere decir que hay que crear una solución vacía en Visual Studio y poner nuestro paquete como el que usa el proyecto. Tal que así:

2020 04 24 14 20 58
Solución Visual Studio

Si tienes más de un paquete o modelo, necesitarás crear un proyecto para cada uno dentro de la solución.

Tenemos que crear otro archivo llamado packages.config con el siguiente contenido:

<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="Microsoft.Dynamics.AX.Platform.DevALM.BuildXpp" version="7.0.5644.16778" targetFramework="net40" />
  <package id="Microsoft.Dynamics.AX.Application.DevALM.BuildXpp" version="10.0.464.13" targetFramework="net40" />
  <package id="Microsoft.Dynamics.AX.Platform.CompilerPackage" version="7.0.5644.16778" targetFramework="net40" />
</packages>

El tag de versión dependerá de cuando leas esto, pero el de arriba es el correcto para el PU35. Tendremos que actualizar este archivo cuando salgan versiones nuevas de los nugets.

Y para terminar esta parte necesitamos añadir la solución, el nuget.config y el packages.config a nuestro source control. Esto es lo que he hecho yo:

2020 04 24 14 29 01
Azure DevOps

Podéis ver que he creado una carpeta Build en la raíz de mi proyecto de DevOps. Eso sólo es una preferencia mía, pero prefiero tener sólo código en mis ramas, incluso los proyectos están fuera de la rama, sólo código para branchear y mergear. Ponemos los archivo sy la solución dentro (o dónde quieras) y listo.

Subscribe! #

Receive an email when a new post is published
What are your Feelings
Share This Article :
  • Facebook
  • X
  • LinkedIn
  • Pinterest
Still stuck? How can I help?

How can I help?

Azure DevOps artifactsConfigure pipeline

2 Comments

  1. Mahesh 1 year ago Reply

    hi i am facing below issue please help me

    Starting: Create Deployable Package
    ==============================================================================
    Task : Create Deployable Package
    Description : Task to create a deployable package for Dynamics 365 for Finance and Operations
    Version : 0.1.1573751
    Author : Microsoft Corporation
    Help : Review the Dynamics 365 for Finance and Operations [Developer Documentation](https://go.microsoft.com/fwlink/?linkid=2128586).
    ==============================================================================
    ##[error]No X++ binary package(s) found
    Finishing: Create Deployable Package

    • Adrià Ariste Santacreu Post Author 1 year ago Reply

      Review all the paths used, it’s not finding the binaries from the build step.

Write A Comment Cancel Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

  • Dynamics 365 Community
  • Subscribe!
  • Microsoft MVP
  • LinkedIn
  • Privacy Policy
  • Contact
  • About me

© 2024 ariste.info. Designed by CazaPelusas.

Top

    Type above and press Enter to search. Press Esc to cancel.