Release Management vNext pitfalls

Recently I have been playing around with vNext Release Templates in Microsoft Release Management. These type of deployments use Powershell Desired State Configuration (DSC) to perform the actual deployment of your application to the target environment. While this generally works very well, I had a couple of “head-against-brick-wall” experiences which – I must admit – did cause a bit of an headache. This post is the first in a series to share some of those experiences, so that you can avoid them.

Installing WMF 4 requires .Net 4.5

I knew that in order for DSC to work I needed to install Powershell 4, which is part of the Windows Management Framework (WMF) 4.0. So I went ahead and downloaded and installed WMF 4.0. However, my DSC scripts wouldn’t work. Turns out you need to install .Net Framework 4.5 before you install WMF 4.0. A good way to check if everything is OK is to open up a Powershell prompt and type:


That should return a PSVersion of 4.0:image

More information can be found in this post on the Windows Powershell Blog: WMF 4.0 – Known Issue: Partial Installation without .Net Framework 4.5

Happy DSC-ing!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s