Hi Denis Trunin ,

Thank you for sharing this amazing article. Do you know how do we split tasks "Upload build package to asset library" & "Deploy the asset to environment" into separate stages? It should be fairly simple, but I am unable to do that for one of my client.

Per the best of my knowledge, we should capture the output of the Dynamics Lifecycle Services (LCS) Asset Upload task to a variable that has a scope of the release and use that variable as an input in Dynamics Lifecycle Services (LCS) Asset Deployment task. I attempted to do it but my variable (in your example, it is LCS File Asset Id) comes out to be blank always.

Thanks.

Thanks. From the post - you should tick "Wait for Completion" checkbox if I understand the question correctly

I am getting error at NuGet custom install Packages ##[error]The nuget command failed with exit code(1) and error(File 'D:\a\8\s\Build\Current40\nuget.config' does not exist.

For existing pipeline another error came up:

##[error]The nuget command failed with exit code(1) and error(There is not enough space on the disk.

How to clear disk space?

This looks like consulting task. I suggest trying to post it on some public forum

Hi Denis,

Thanks for this amazing post. I have followed this blog but unable to create project for ISV model under solution as mention in step 7.

Kindly explain this step in details.

Regards,
Rahul Singh

maybe your ISV is binary? In this case you don't need to compile it