In the previous post, I added the tasks to on-premises TFS using C#. This time I will add similar data using an Excel add-in. I will also learn how to accidentally remove the link from the task to the parent element.
Continue reading
Adding a new Task in TFS using C#
An assignment: using data from the Excel file (sample data below) insert them into TFS (on-premises). Automatically. Start. You have three months from now. Or a few hours.
Continue reading
Draw the SSIS Package using SVG – part III
In the third part of a series, I focus on drawing the constraints’ descriptions and the colours. And also a bit of PowerShell for automation.
Continue reading
Draw the SSIS Package using SVG – part II
The post is a second part of the series. In the previous one, I created an SVG image of the simple SSIS package, but when I tried to draw something advanced (upper image below) I got something far from expected (lower image below). This time I’ll fix it.
Continue reading
Draw the SSIS package using SVG – part I
For one of my projects, I need to draw the content of an SSIS package. It should not be a big problem, as the file contains all the required information. If you need to do something similar – I write a series of posts on how to achieve it using SVG, XSLT transformations and a bit of PowerShell (and maybe something more along the way). All the code is available on GitHub. The setup I start with the sample package as on the picture. It has three elements aligned vertically, with AND precedence constraints, evaluated as Success. It also has a small annotation on the side. The part responsible for
Continue reading
Working with properties in ssisUnit
One of the ssisUnit commands is a PropertyCommand. It allows you to read or set a property of the task, the package or the project. As of the time of writing – you can’t test the properties of the precedence constraints or data flow elements (but you can’t currently test data flow at all). How do you use it?
Continue reading
What’s new in ssisUnit?
ssisUnit has a stable version for SSIS 2005 – 2014. It didn’t change much since August 2014, until August 2017. Then my Pull Request was merged, and it added some new functionality for ssisUnit. First – it works with SSIS 2017. You can probably use it with SSIS 2016 packages, but I didn’t test it yet. Although – you can’t check everything – there are problems when you want to use Control Flow Templates in your packages. When I tried to read the variable from the container included from the template – it hangs for a few seconds and returns an incorrect result. It’s something to investigate later.
Continue reading
Writing ssisUnit test using API
In the post about using MSTest framework to execute ssisUnit tests, I used parts of the ssisUnit API model. If you want, you can write all your tests using this model, and this post will guide you through the first steps. I will show you how to write one of the previously prepared XML tests using C# and (again) MSTest.
Continue reading
Testing the loops in ssisUnit
In the Q & A post after the webinar on ssisUnit (in 2013) John Welch answered the question about the loops: “If possible, can you demo if a container can be executed? Especially a For loop or For Each loop?” I didn’t have time to demo this during the presentation. Good thing too, because there was an error around handling of containers. This has now been fixed in the source code version of the project. There is no example though, so let’s add one.
Continue reading
Setting package references in ssisUnit
When you set the packages’ references in the ssisUnit tests you have four options for the source (StoragePath) of the package: Filesystem – references the package in the filesystem – either within a project or standalone MSDB – package stored in the msdb database Package store – packages managed by Integration Services Service SsisCatalog – references the package in the Integration Services Catalog In this post, I will show you how to set the package reference (PackageRef) for each option.
Continue reading