When working on your precious pipeline templates that you write in YAML, it can be a burdensome to document each parameter individually. Documentation is also overlooked, as you always seem to be busy with other things, but eventually you'll be glad you did it. What if you can make it more fun and easier to do?
ReadBack in June I explored the Crescendo module for Powershell to wrap native command line tool into cmdlets. In the blog post, I needed to make a deviation and did not spend time on looking to the output handler.
ReadQuite recently I was facing an issue whereas a new service was introduced which needed deployment through Azure DevOps remotely. Normally spoken I would fallback in Windows Remote Management (WinRM) and use it in combination with the Invoke-Command cmdlet to create in conduction with the New-Service cmdlet. Unfortunately, WinRM was disallowed by the Network Security Groups (NSGs) on the Azure VMs. Luckily the RPC protocol was allowed, giving us the ability to use the native sc.exe command line tool.
ReadIf you went through the first part of this tutorial series, you are going to add an existing project side-by-side you're working project. This is also known as a **composite** project, where you will create a reference to the other main database project, and also include the tSQLt DacPac as a reference for deployment, as this includes all the objects to run tSQLt tests. So, if you did not follow along with the first series, make sure you do that first to follow along with this second part! If you're already there, let's get started
Read