/en/tags/engagement-sdk/Recent content in Engagement SDK on DVLUPHugoen-USFri, 04 Jan 2019 00:00:00 +0000/en/blog/2019.01.04-using-powershell-to-installing-msi-in-a-devops-build/Fri, 04 Jan 2019 00:00:00 +0000/en/blog/2019.01.04-using-powershell-to-installing-msi-in-a-devops-build/<p><img src="../../../en/blog/2019.01.04-using-powershell-to-installing-msi-in-a-devops-build/image-4.png" alt=""></p> <p>I have <a href="https://github.com/LanceMcCarthy/MvpApi" target="_blank" rel="noopener">an open source UWP project</a> that relies on the Ad SDK and Engagement SDK to be installed to Visual Studio. This normally isn&rsquo;t a problem, because you can just run the MSI on your PC (see installation instructions <a href="https://docs.microsoft.com/en-us/windows/uwp/monetize/microsoft-store-services-sdk" target="_blank" rel="noopener">here</a> and <a href="https://docs.microsoft.com/en-us/windows/uwp/monetize/install-the-microsoft-advertising-libraries" target="_blank" rel="noopener">here</a> ).</p> <p>I decided to move the project into DevOps so that I get some of that CI/CD goodness to build and publish new releases automatically to the Microsoft Store. However, there was a problem, when trying to build the project in a DevOps build pipeline, you&rsquo;ll get the following error:</p>