coapp-developers team mailing list archive

[Rafael Rivera <rafael@xxxxxxxxxxxxxxxxx>]

I was reviewing this email today again and... I'm a little confused. From
what I gleaned, it appears this is how you envision this working:


   1. User downloads DoubleRainbowsWallpaper-1.0.0-x86.msi and runs it on
   their clean PC.
   2. The bootstrapper runs and identifies the PC is without CoApp engine.
   3. The bootstrapper downloads and installs CoApp-Engine.msi
   4. The bootstrapper calls some engine component to install my app
   (coapp-installer).
   5. ???
   6. Profit.


Questions:

   1. When the user double-clicks the MSI, and the bootstrapper executes, is
   the MSI install blocked, aborted, or suspended/continued?
   2. If suspended... Can you launch and install the engine while the other
   MSI package is suspended, given Windows Installer one-package-at-a-time
   limitations?
   3. If aborted... is the MSI in this case a non-executable container? What
   happens when I do msiexec /a <msi> (administrative install)?


/rafael


On Tue, Sep 14, 2010 at 2:14 PM, Garrett Serack <garretts@xxxxxxxxxxxxx>wrote:

>  Howdy folks,
>
>
>
> (Some of this is review, some of this is a small divergence from previous
> design)
>
>
>
> I’ve been doing some work to support working on two tracks (Managed Engine
> and Native Engine), and my testing with the bootstrap component calls into
> the needed to modify how the engine code gets called.  The change to my
> previous plan is that the functionality of the coapp-bootstrap.exe has been
> split into two pieces: the ‘bootstrap agent’ and a ‘tiny-installer’—the
> tiny-installer contains the code that calls into the engine, and is
> installed in the same Side-by-side assembly as the engine itself.
>
>
>
> Each CoApp package MSI is embedded with a bootstrap.exe that gets extracted
> and executed when the MSI is installed (outside of the application)
>
>
>
> *CoApp-Bootstrap.exe* Process:
>
> -          The bootstrapper identifies the location of the
> coapp-installer.exe by finding one of (first-wins):
>
> o   Check the registry for a pre-set location for the tiny-installer.exe
>
> o   Looks in WinSxS for a registered coapp-engine assembly. (the manifest
> embedded in the EXE identifies the minimum engine version currently:
> 0.0.0.0)
>
> o   if the correct version of the engine is not installed, it downloads
> the MSI at http://coapp.org/coapp-engine.msi and installs it.  After the
> engine is installed, it looks *inside* the WinSxS assembly for the
> coapp-installer.exe
>
> o
>
> -          calls the target EXE with the path of the current MSI.
>
>
>
>
>
> [image: Description: fearthecowboy] <http://fearthecowboy.com/>
>
> *Garrett* *Serack* | Microsoft's Open Source Software Developer | *Microsoft
> Corporation
> Office*:(425)706-7939                                       *email*/*
> messenger*: garretts@xxxxxxxxxxxxx
> *blog*: http://fearthecowboy.com                                      *
> twitter*: @fearthecowboy <http://twitter.com/fearthecowboy>
>
> *I don't make the software you use; I make the software you use better on
> Windows.***
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
> Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
> More help   : https://help.launchpad.net/ListHelp
>
>