PoshSSDTBuildDeploy Updated - Now With Proper VS2019 Support

Hello! I’ve finally gotten around to adding proper support for VS2019-based projects. Back in May I added a variable to Invoke-MSBuildSSDT so that the path of msbuild could be passed in directly, instead of trying to find MSBuild. This was because at the point of me writing the function VS 2017 was the latest version. So this should work for all subsequent builds going forward. And today I finally added ‘16’ as an option on the MSBuildVersionNumber, which makes things a little easier, and also added the function Install-VsBuildTools2019 that can be used to download and install MSBuildTools version 16, which is compatable with VS 2019.

PoshSSDTBuildDeploy 2.0.519: Now With Dynamic Deploy Options

Hello! And Happy Friday! Right, so PoshSSDTBuildDeploy got another minor tweak today. I’ve had a couple of requests in the past for Dac Deploy Options to be configured at deploy time. Generally these are loaded from the publish xml file and whatever the defaults are, or if the publish file has been set to something else. And so if you want things different for different environments you need to have separate publish files for different environments.

PoshSSDTBuildDeploy: Fix for File Paths

Hello! I got a pr from Peter Schott wrt PoshSSDTBuildDeploy not quite working as expected. Turns out there was a few bugs with a couple of the functions. And I noticed another one myself so there’s been a relative flurry of activity over on the GitHub. What bothered me though was that I was sure that I had tests to cover these bugs. Turns out I do have tests to cover the issue of spaces in folder names when passing a Nuget path, it was to do with some weird concatenation.

Mocking With Pester

Hello! Last week we spent some time in the office here getting to grips with Pester. I’ve written some Pester tests in a few projects I’ve got in GitHub, most notably PoshSSDTBuildDeploy (henceforth known as PBD) and have them running in the VSTS CI build here and the Publish build here. So I felt I was quite familiar with Pester testing. But one thing I had missing in my tests was mocking.

New Year New Me 2019 Musings

Hello! And Happy New Year! Another year finishes, and no sooner than that, another one starts! Amazing! PoshSSDTBuildDeploy Changes Appropriately I start this year the way I finished last year: once again the Publish-DatabaseDeployment function gets a small but useful change. I’ve been deploying a database to a cheap VM using Standard HDD in Azure, and the deploy times out on post-deploy scripts. I think it only happens on the initial deploy as I’m not setting the size of the data/log files (tsk).

Christmas 2018 Musings

Hello! Another year draws to a close; 6 years blogging and counting… but forget looking too far dwelling on the past, what has happened recently??? PoshSSDTBuildDeploy Changes Of course the PowerShell module which has taken most of my time has had more updates. I’ve added some documentation to both the readme and a couple of the functions that end users will use most frequently. But I’ve also added a switch to Publish-DatabaseDeployment to stop the deployment summary being generated.

November 2018 Musings

Hello! Changes to dbatools Functions What I Wrote As the saying goes, it never rains but it pours. And there’s been a flurry of activity on a few of the functions that I initially contributed late last December to dbatools. Up to this point, there have been very few changes pushed and issues raised. However fom the middle of October to the beginning of November there’s been about 15 issues/pr’s. Extraordinary!

Deploying Logins With Different Domains Via SSDT

Hello!

Unlike certain objects like tables, views etc. in SSDT projects, windows logins can be more difficult to deploy, mainly because the logins will most likely be across different domains. In one place where I used to work they implemented a solution of having many different configurations in the Configuration Manager, and a pre build task would switch in and out certain files to be built. This is quite a messy way to do things, because you have to build the same project relative to the number of environments you have.