WI .NET user group slides

Thank you to everyone who attended my talk at the WI .NET User group last Tuesday. I posted the slides from the event below. I also wanted to let everyone know that if you’re interested in a career at Centare or want to attend any of the other great events we put on, check out the Centare Events page! Slides: IntroductionToDevOps.pdf

Read more

Deploying databases with Octopus Deploy Part 3

Completing my series on deploying databases with Octopus Deploy, I want to cover how to deal with a common gap when working with SQL Database Projects and SQL Server Data Tools (SSDT): seeding data into the database. Most people deal with this by using PostDeployment SQL scripts that do merge queries to insert or update the data. While this technique works, the data isn’t very readable and can be difficult to maintain as the data set or number of tables grow.

Read more

That Conference 2014 Presentation

I posted online the slides from my presentation at That Conference. There are resource links at the end of the presentation. Also see below if you would like to see the sample application I demoed during the presentation. Slides: BuildingStableCloudApplications.pdf Source: GitHub: dpiessens/cqrs-journey-code

Read more

Deploying Databases With Octopus Deploy: Part 2

Continuing with my series on deploying databases with Octopus Deploy, I want to cover an area that people commonly know is possible but often struggle with the details: Deploying with Entity Framework Migrations. Entity Framework Migrations are in concept simple. The EF team provides a great executable (migrate.exe) located in the tools folder of the NuGet package to perform the migration. Packaging it up can be a little more tricky. Project Setup When creating your deployment package for Octopus, you’re going to want to include the migrate.exe file.

Read more

Deploying Databases with Octopus Deploy: Part 1

One of the most common questions I get when helping people with Continuous Delivery is how to I push updates to my database? The traditional mindset is often create a folder of SQL scripts and make the deployment push the newest ones. The problem that often arises from this is there’s no rollback and things often get missed. There’s got to be a better way! Assuming your organization is (or will become) comfortable with tooling doing your updates, there’s some great options you have.

Read more