MetaProperty is marked as secure error message in MSDeploy

So I was running this command on an IIS 6.0 box:

msdeploy verb:sync -source:webServer60 -dest:package=c:\

and kept getting this error:

Error: The property ‘value’ located at ‘/webServer60/metaKey[@path=’/LM/W3SVC’]/metaProperty’ is marked as secure. You must specify an encryption password to archive this property.

Since this was a production server setup by someone else, I thought that I had to get the password from them.  NOPE!!!  After an hour of scouring the web to see how even to set this password in IIS 6; a colleague pointed out that it needs the password to encrypt the metabase properties going into the package!!!!

So I could set any password!!! Just have to remember it when I go to deploy that package somewhere else.

Here’s to hoping you find this post before wasting an hour like me! 🙂



An updated Word version of the MSF for CMMI Process Improvement v5.0 Process Guidance

Hi Folks,

This has been a very popular download on the site.  I’m starting to do some more work around the CMMI template, so I thought I’d update the word version.  Much cleaner in the table of contents.  Only thing missing is some info on the dashboard reports, but stubs are there for each one.  Weighs in at 216 pages!  Enjoy!

MSF for CMMI Process Improvement v5 – Process Guidance

Software engineers can have a high risk of unhealthy insomnia | The Informative Report

Software engineers can have a high risk of unhealthy insomnia | The Informative Report.

InfoQ: Announcing Verve – A Type-Safe Operating System

InfoQ: Announcing Verve – A Type-Safe Operating System

Cool stuff!

Color Printing Extension Now Available for Visual Studio 2010

Color Printing Extension Now Available! – The Visual Studio Blog – Site Home – MSDN Blogs.

Code Reviews

Code reviews are a best practice developed back in the early 1970’s by Michael Fagan.  He was a computer hardware engineer by training and knew from experience that reviews in his previous field found quite a few defects before a hardware spec was sent to the factory to be burned onto silicon.  It was expensive to undo defects once the spec had been sent to the factory and reviews were a great tool in catching defects early.  His original paper describes the “Fagan Inspection”.

As time has gone on, more papers and books have been published on the subject; most notably Handbook of Walkthroughs, Inspections, and Technical Reviews by Daniel Freedman and Gerald Weinberg in 1990.  The best current source for how to do reviews is the IEEE Standard 1028 for Software Reviews and Audits.  Regrettably, the IEEE does not make their standards free to access, which I think diminishes their use and ultimately their importance.  In it they describe four types of reviews: a Management Review, Technical Review, Inspection, and Walkthrough.  I have taken these four descriptions and amalgamated them into a review procedure that, I think, brings the four procedures together nicely.  I post it here for your edification and use.

Code Review Policy & Procedure