Unanswered

Build and Release Pipeline using Azure DevOps

(4) Share

Report

Posted on by DM-11070006-0

I am working on ALM for Dynamics CRM using Azure Devops. We want solution to be saved in repo as unpack and create solution as managed and unmanaged in build pipeline from repo. I have done a PowerShell script to unpack unmanaged solution to a specific folder in repo.

The user will check-in changes and then PR will be created.

When PR is approved and branch is merged then build will kick-off. I have added two steps to pack solution as Unmanaged and Managed using Power Platform Build Tools.

As I have exported solution as Unmanaged using my Powershell Script, the solution is packed as unmanaged successfully. When I try to pack solution as Managed it fails.

Is there a way around to fix this? I want to unpack solution store in repo and pack solution as managed and unmanaged both. Is there any other way to achieve this?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

TD 74 on at

Like (1)

Report

Hi there,

So i recently came across this issue before and found that there is no way to pack a managed solution from source control, so i'm not sure what the option is for.

I did the following work around:

Separate your build pipelines into two separate builds.

1st pipeline

An export pipeline to export your unmanaged build into source control. (creation of separate branch)

2nd pipeline

A build pipeline to import your build into a separated build environment (triggered from PR to main) as unmanaged (to check if your build is working and to catch deployment errors) and export from this environment as managed finally copying over relevant file to the build artefact and staging the build int he artefact directory.

3rd pipeline

A release pipeline that triggers when a new build is available from publishing the artefact which then ports to UAT and Prod.

This article is the biggest helper in figuring this out by Luise How to get from Dev? Ooops! 🤭 to proper (Azure) DevOps for Power Platform which was also recently suggested to me by an ex-MSFT engineer as best practice.

Let me know if this helps!

Rgrds,

TD

Was this reply helpful? Yes No
Michael E. Gernaey 53,351 Super User 2025 Season 2 on at

Like (0)

Report

Hi @DM-11070006-0

Let me see if I can find my script, which can pack it as managed and I will share. Give me a little time as I don't use it much anymore and have to find it in one of my repo's. But it can be done.

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report

If you are using pac solution pack you can try and use the following argument if you don't have the managed source files (specifically its forms that have a manged version, all other files are basically the same):

--useUnmanagedFileForMissingManaged -same

Ideally though you should be extracting and unpacking both unmanaged and managed. I prefer using pac solution sync -p Both because it does all 4 of those steps in one command cleanly and will run faster as a result. You'll need to do a pac solution clone initially though so that it creates a cdsproj file which is used to control the solution unpack/pack configuration.

Was this reply helpful? Yes No