https://www.jaestevan.com/en/tag/powershell/Recent content in PowerShell onHugo -- gohugo.ioen-USTue, 12 Jan 2016 00:00:00 +0100https://www.jaestevan.com/en/blog/2016/automatic-build-processes-with-tfs-and-ax-2012-2-2-alm-x/Tue, 12 Jan 2016 00:00:00 +0100https://www.jaestevan.com/en/blog/2016/automatic-build-processes-with-tfs-and-ax-2012-2-2-alm-x/<p>In the <a href="https://www.jaestevan.com/en/blog/2015/automatic-build-processes-with-tfs-and-ax-2012-1-2-alm-ix/">previous article in this series</a> we defined the main process to configure a Microsoft Dynamics AX 2012 Build in TFS, in summary:</p> <ul> <li>Install and configure the necessary TFS components on the build server (Agent, Controller, etc.).</li> <li>Create a new project with custom activities and the default template.</li> <li>Upload all of this to the source code repository in TFS or Team Services so the Controller can access them.</li> <li>Add these references to <em>Visual Studio</em> so it recognizes the new activities.</li> <li>Create a new Build definition using the downloaded template.</li> </ul> <p>We were left executing this newly created <strong><a href="https://www.jaestevan.com/en/blog/2015/automatic-build-processes-with-tfs-and-ax-2012-1-2-alm-ix/">Build definition</a></strong> with all options, activities and default template, and after which we received an error. Frustrating, isn&rsquo;t it? It may be, but if you think about it, it&rsquo;s quite logical, let&rsquo;s see:</p>https://www.jaestevan.com/en/blog/2015/automatic-build-processes-with-tfs-and-ax-2012-1-2-alm-ix/Thu, 03 Dec 2015 00:00:00 +0100https://www.jaestevan.com/en/blog/2015/automatic-build-processes-with-tfs-and-ax-2012-1-2-alm-ix/<p>In the previous posts of this series we have seen <a href="https://www.jaestevan.com/en/blog/2012/team-foundation-server-2010-installation-alm-ii/">how to configure a TFS server</a> (local or in the cloud) and how to <a href="https://www.jaestevan.com/en/blog/2012/microsoft-dynamics-ax-2012-application-lifecycle-management-alm-i/">use it to manage our tasks</a>, <a href="https://www.jaestevan.com/en/blog/2015/source-code-control-with-tfs-in-microsoft-dynamics-ax-2012-alm-vi/">control the source code</a> and <a href="https://www.jaestevan.com/en/blog/2015/version-control-in-microsoft-dynamics-ax-2012-using-team-foundation-server-branches-alm-vii/">manage versions through branches</a>, among other things. To close the circle we must process all that information, code and versions into something we can deliver to our clients/users.</p> <p>This is where automatic build and compilation processes come in, called <em><strong>Build</strong></em> processes. Running a <em>Build</em> in TFS is relatively simple if we work with .NET languages, but to do it with AX we&rsquo;ll have to work a bit beforehand to prepare the environment and install the necessary components on the servers.</p>