Oh, and after the raw basics work, we'll iterate like we always do,
until it works well. <smile/>
Rob Mensching wrote:
> A few more details:
>
> 1. I think we will end up doing the work to host the CLR. It won't be
> available right out of the gate but it is a thing to solve (and there
> are several very challenging things to solve).
>
> 4. There will not be different entry points. However, you application
> will be provided the "action state" (install, uninstall) if it was
> provided on the command-line. Also, burn will calculate the install
> states for all of your packages. The problem with picking "install mode"
> vs. "repair/maintenance mode" is how would burn know which is which? For
> example, if none of your packages are on the machine is that because the
> user removed them or this is the first install? If one of 5 packages is
> missing, is that because the user chose not to install it the first time
> or some other app happens to install 4 of your 5 packages? Anyway, the
> goal is to provide enough information to the UI so it can decide how it
> would like to proceed.
>
> We're trying very hard not to make a lot of decisions for the UI
> (instead, just provide data).
>
>
> Brian Rogers wrote:
>
>> Hey Guys,
>>
>> Although I cannot commit to a time line right now, I do have the following
>> plans if all continues as schedule.
>>
>> 1. We are working on hosting the CLR for our team's consumption. If we get
>> something usable in place that the WiX team will accept then we will hand it
>> over.
>>
>> 2. Not sure how, or if we will handle this currently, but my thoughts were
>> to show the passive install UI for .NET. We will be writing that in native
>> code.
>>
>> 4. I believe the plan is no (as of now), there will not be different entry
>> points. You will need to detect the system state to figure what you would
>> like to do. From point #3, however, there is one key you can be set where
>> you could pass in a command line value you expect as uninstall
>> (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{PRODUCT-GUID}\UninstallString).
>>
>> Hope this helps,
>>
>> Brian Rogers
>> "Intelligence removes complexity." - Me
>> http://icumove.spaces.live.com
>>
>>
>> On Wed, Apr 29, 2009 at 5:51 PM, Bob Arnson <b...@joyofsetup.com> wrote:
>>
>>
>>
>>> jhennessey wrote:
>>>
>>>
>>>> 1. I remember reading that burn will allow you to provide a custom UI
>>>>
>>>>
>>> .dll.
>>>
>>>
>>>> If this is still the case, can this be a .Net assembly?
>>>>
>>>>
>>> Not unless somebody does the work to host the CLR. Burn has to be native
>>> code so we can support installing .NET.
>>>
>>>
>>>
>>>> 2. Assuming that the answer to number 1 was "yes", will burn first allow
>>>>
>>>>
>>> the
>>>
>>>
>>>> installation of prerequisites (like the .Net Framework) before loading
>>>>
>>>>
>>> the
>>>
>>>
>>>> UI .dll?
>>>>
>>>>
>>>>
>>> See #1 and add "only if someone makes a CLR host that first shows
>>> native-only UI to bootstrap .NET."
>>>
>>>
>>>
>>>> 3. Will burn provide built-in functionality to allow the bootstrapper to
>>>>
>>>>
>>> be
>>>
>>>
>>>> launched from the Add/Remove programs applet (kind of like how the Visual
>>>> Studio installer launches its bootstrapper)?
>>>>
>>>>
>>>>
>>> Built-in? No. The right way to do it is by installing your Burn .exe so
>>> you can write the ARP overrides and service the chainer itself.
>>>
>>>
>>>
>>>> 4. Will burn allow you to specify different UI entrypoints for modify and
>>>> remove scenarios (or will you just have to code the detection logic
>>>>
>>>>
>>> yourself
>>>
>>>
>>>> like in an external UI)?
>>>>
>>>>
>>>>
>>> Dunno.
>>>
>>> --
>>> sig://boB
>>> http://joyofsetup.com/
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Register Now & Save for Velocity, the Web Performance & Operations
>>> Conference from O'Reilly Media. Velocity features a full day of
>>> expert-led, hands-on workshops and two days of sessions from industry
>>> leaders in dedicated Performance & Operations tracks. Use code vel09scf
>>> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>>> _______________________________________________
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>>
>>>
>> ------------------------------------------------------------------------------
>> Register Now & Save for Velocity, the Web Performance & Operations
>> Conference from O'Reilly Media. Velocity features a full day of
>> expert-led, hands-on workshops and two days of sessions from industry
>> leaders in dedicated Performance & Operations tracks. Use code vel09scf
>> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
