Monday, September 17, 2012

Power your WiX conversion with this VdProj2Wix conversion PowerShell script

InfoQ - WiX – Powerful Deployment For Your .NET Apps

"Visual Studio 2012 gets rid of “VS Setup” projects. However, the WiX toolset provides a strong open alternative for creating your installation packages.

WiX 3.6, which was recently released, includes the Burn bootstrapper/chainer. This means not only can you create installer packages such as MSI files, but can also chain multiple installers (for e.g. to install prerequisites) and provide a much smoother installation experience for your users. The new release also has several new features and fixes over 500 bugs.

What if you are already using VS Setup projects for your products? You can try using this PowerShell script for converting your existing VS Setup projects to WiX format.

Also, instead of editing the XML files in a text editor, you can use Votive - a VS package that lets you write WiX scripts from within Visual Studio and brings benefits such as intellisense, MSBuild support, project templates and more. ..." [GD: Post Leach Level: 90%]

Chris Oldwood - vdproj2wix v1.0

Introduction

This PowerShell script (vdproj2wix.ps1) is a very simple one for converting a Visual Studio setup project (aka a .vdproj file) into a WiX format one (i.e. a .wxs file). Although there are other more fully featured tools for creating a .wxs file, such as from an existing MSI binary, I wanted something that gave me a bare bones .wxs file that ignored all the boilerplate code that Visual Studio adds by default. As a server-side chappy all the MSI installers I create are simple ones designed to deploy a bunch of files into a folder - this script targets that scenario.

Converting a Setup Project

The script requires just a single argument to run - the path to the .vdproj file that you want to convert. It will create a new file in the same folder with the same name but with a .wxs extension instead, e.g.

image

I hadn't seen that PowerShell script before... Looks like that might come in handy!

That and I'd not mentioned the v3.6 release (I know, I'm a little behind... ;)

 

Related Past Post XRef:
Just to reiterate, VS2010 is the last version of Visual Studio to support Visual Studio Deployment Projects
Visual Studio Setup & Deployment Projects declared dead & retired. VS2010 will be the last…

"Visual & Installer" Free Visual Studio Add-in for creating NSIS and Inno Setup installers

WiX rounds the curve and joins Outercurve
An end-to-end WiX example...
Get your WiX fix now on WiXToolset.org

Wintellect goes GitHub, sharing Paraffin, Wintellect PowerShell, Wintellect VS Cmdlets and more

WiX 3.5 released (Think “IIS7, VS2010, plus bunches of bugs squashed” release)
WiX Resources – Some help up the learning curve
Stick a fork in it, WiX (Windows Installer XML) 3.0 is done…
WiX (as seen in VS2010) Documentation CTP – What is WiX, how to use it, and how to extend it.
More WiX Mixing (WiX, Votive and VS2005/8)
WiX Your Way to Installer Happiness
WixTrim - WiX Designer (with C# 2 Source)
Windows Installer XML (WiX) toolset has released as Open Source on SourceForge.net

2 comments:

  1. "Although there are other more fully featured tools for creating a .wxs file, such as from an existing MSI binary"


    I wonder if you could give some examples or links to tools that do this (wxs from MSI)?

    ReplyDelete
  2. @Simon,
    Best bet would be to click through to the original post and contact the Chris directly (there's an email address at the bottom of the post)...

    http://www.chrisoldwood.com/win32/vdproj2wix/vdproj2wix.html

    BUT one of the utilities I bet he was referring to was Dark

    ReplyDelete

NOTE: Anonymous Commenting has been turned off for a while... The comment spammers are just killing me...

ALL comments are moderated. I will review every comment before it will appear on the blog.

Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...

I reserve, and will use, the right to not approve ANY comment for ANY reason. I will not usually, but if it's off topic, spam (or even close to spam-like), inflammatory, mean, etc, etc, well... then...

Please see my comment policy for more information if you are interested.

Thanks,
Greg

PS. I am proactively moderating comments. Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...