Share via

Release date for MSI 4.5 now looks like Q2-ish

  • Article

Back on September 1st, I answered the question When will Windows Installer 4.5 be RTM-ed? with Q1 of 2008.  Turns out that date was too optimistic.  Q2 of 2008 now looks more realistic but, given the first optimistic mistake and in an abundance of caution to avoid compounding the first mistake, let's call just it Q2 -ish. 

For those of you wondering what happened, we've had a number of unexpected setbacks that required we either 1) cut features 2) reduce quality efforts, or 3) take more time.  Taking more time is the best option available.  We had believed until just recently that we could make the date but our best intentions did not hold up.

For those of you that also ship software for a living, the story of this slip may be familiar.  Our chief mistakes were inadequately allocating time for a) unfilled positions, b) responding to user and partner feedback, and c) crossteam dependency execution.  Through the cycle we saw these in small increments but it wasn't until the entry point for our Q1 glide path was missed that we realized the small increments were compounding.

As of the end of November, we're hard at working down our backlog of knowns.  My reluctance to "set" a new date is because I'm not sure we've accounted for enough of the unknowns.  'Once bitten, twice shy' as the old saying goes. ;^) 

We'll have another project status update before the end of Q1 2008.

Comments

  • Anonymous
    December 22, 2007
    Hi, I understand that UNICODE (string/text) is not supported by Windows installer (MSI). Why is UNICODE not supported? Are there any plans to include UNICODE in MSI (Windows Installer)? Thanks.

  • Anonymous
    December 30, 2007
    Hi there Windows Installer Team and happy holidays. I've apparently run into a problem running Vista Home Premium 32bit where in my Windows Installer 4.0 installation has become corrupted. There appear to be no 4.0 redistributables to repair my installation and I'm left unable to install anything via .msi files. I'm repeatedly given errors of... "Internal Error 2203. C:WindowsInstaller77ad070.ipi, -2147287035" With occasionally the .ipi file in the error code differing. Any advice as all MS solutions thus far have been of little help.

  • Anonymous
    January 03, 2008
    The following post should help... http://groups.google.com/group/microsoft.public.platformsdk.msi/browse_thread/thread/5fe6882d572c6d25/6c822b6f62f44a7a%236c822b6f62f44a7a