Some Visual studio errors | VSTS extension | Continuous Integration | Azure DevOps tutorial -8

This Visual Studio tutorial will focus on some errors while creating VSTS extension and it’s continuous integration pipeline..
See which errors may happen during building VSTS extension or configuring build and release management with VSTS. Learn more about the error with referencing the images, which is usually because the filenames on VSTS are case sensitive. In addition, another error that may happen is the format of the build number while trying to override it. See how to override the package name appropriately. Error may happen also in the release management with the build number, which should increase each time the extension is published, so make sure that before trigger the deployment you increment the build number.

About the Author
-----------------------------
Video:
Blog:
Linked-in
GitHub
Twitter:

If you would like to learn more about how to create new Dynamics 365 CRM environment locally with Windows Server 2016 Standard Edition, then prepare this machine to be ready to upload to the cloud (Azure), then upload the machine to Azure, then create image of that machine, after that, we will start using this image for creating new virtual machine with Dynamics 365 then reconfigure the machine to fix all the problems because changing the hard disk and the machine name which will make problem for SSRS (SQL Server Reporting Server), all IIS application pools crashed, the SQL Server name crashed, and of course Dynamics 365 CRM doesn’t work, so I will show exactly how to solve all those problems so we can have a new copy of an existing Dynamics CRM machine and make it works fine- have a look at this post:
#Visual_Studio_Errors #VSTS_extension #Continuous_Integration #Visual_Studio

[MRadwanMSF]

The following video is also important and will cover DevSecOps which is very important