Experiance suggests there are windows of opportunity for breaking the cycle of the centralized setup model. External forces are better positioned but it can also work for a individual skeptic to start the ball rolling. So where does one start breaking...

Yesterday, I introduced the crash and burn problem but there's still more to this problem. Lather, Rinse, Reward, Repeat After a few cycles where Centralized Setup defers problems to transients then crashes and burns-out the core team the cycle...

Yesterday, I introduced the model but there's still more to the problem that needs solving. Introduction to the Controlled Crash As described yesterday , most managers choose to defer setup as long as possible and then hire unskilled and temporary...

I've invested my career in setup for longer than most and I've seen setup for a few product cycles for different businesses. From this collective experience , I've derived a model of the centralized setup business cycle . Business types tell me there...

Wouldn't it be great to have a fun last name?...

Wouldn't it be nice if folks didn't ship MSIs with Internal Consistency Evaluators (ICEs) errors?...

Wouldn't you like to know a trick to digging deeper into a failure of Assembly install in a verbose MSI log?...

Wouldn't you like to know the trick to quickly finding the error in a verbose MSI log?...

Wouldn't it be great to know the “last-write-wins” patch sequencing behavior of MSI 2.0 has changed for MSI 3.0?...

Hello, I am the Dark developer. For the uninitiated, dark is the decompiler of the Windows Installer XML toolset. When initially conceived, dark was a combination of programming project in C# and a way of getting WiX users off the schnide . Unexpectedly...