search

WaelHamze / dyn365-ce-vsts-tasks

VSTS Extension for Dynamics 365 Customer Engagement
https://marketplace.visualstudio.com/items?itemName=WaelHamze.xrm-ci-framework-build-tasks
GNU General Public License v3.0
117 stars 56 forks source link

MSCRM Pack Solution error (FLOW) #68

Closed drivardxrm closed 5 years ago

drivardxrm commented 5 years ago

I'm having an issue with the MSCRM Pack Solution task.

I have a solution-aware FLOW in my solution and it makes the solution packager tool crash. This is a known issue but it is apparently fixed with the latest version of the Core Tools 9.0.3.1 https://devkeydet.blog/2018/04/10/build-and-deployment-automation-of-a-model-driven-powerapp-using-vsts/

I'm able to pack and unpack locally using the updated Core Tools but my Azure Devops Build is not working using the MSCRM Pack Solution task. build error

WaelHamze commented 5 years ago

@drivardxrm the extension is using the latest version, what version of the MS Tools Installer is coming up? I presume you have selected 9.0 in the SDK selection?

drivardxrm commented 5 years ago

@WaelHamze I'm using Microsoft.CrmSdk.CoreTools V9.0.3.1 (last update April 3) 2019-04-16_16-10-37

Using the Solution Packager included in this version, I'm able (locally) to pack and unpack a solution that contains a FLOW. Before I updated to this version, I had the same error that I have using the VSTS BuildTools (see first post).

might be related to issue #69

Thanks

drivardxrm commented 5 years ago

@WaelHamze I was able to make it work. It seems I was not running the latest version of the extension in Azure Devops.
I didn't find a way to update the extension directly in Azure Devops, I had to uninstall and reinstall. Now my solution with a Flow is packing and unpacking correctly with the tool.

Thanks for your help, these tools are legendary ;)

WaelHamze commented 5 years ago

@drivardxrm really glad you got it working. By the way I have released an update yesterday. It will print in the log the version of the Sdk files it is using so users don't have to wonder which version it is using.