<< calling all plugin developers! | Home | random: check your hygene at the gate >>

  • msi for simple deployments

    posted @ Friday, August 25, 2006 2:43 PM | 2 Comments | 

    in writing some plugins for windows live writer i started out creating a deployment package.  first, i suck at writing installers.  i rely on tools to do it for me.  for writer plugins, it really is a simple process to ensure the plugin is installed in the right directory, that's it.

    so using the visual studio 2005 package project, i went about creating my msi.  add file, put destination directory, build.  when i run the msi, it takes FOREVER.  what gives?  why does a simple operation take so long.

    it frustrated me, so i gave up and went to .  simple, lean, fast.  installer runs in nanoseconds (okay, not nano, but compared to msi, it is).

    so someone enlighten me...what gives with MSI and simple operations?

    Friday, August 25, 2006 2:43 PM

    PostTypeIcon

Comments.

  • Bob Arnson said:
    Gravatar
    # re: msi for simple deployments


    MSI's biggest overhead for tiny setups is creating and finalizing installation transactions. But it's also possible that you're getting some overhead from .vdproj. Try WiX.

    8/25/2006 6:47 PM
  • Spike Washburn said:
    Gravatar
    # re: msi for simple deployments


    Bplo posted a good starter on using WiX to build MSIs for Writer plugins here:

    http://bplo.spaces.live.com/blog/cns!CF2831C0AE64E81B!210.entry

    8/30/2006 10:45 AM

Your Reply.

  Comment Form  

Fields denoted with a "*" are required.

*Your name:
Subject:
Your blog:
Your email:  (will not be displayed)
*Your message:

 
Please add 2 and 1 and type the answer here: