Wouldn't the right answer be to treat the prereq the same as every other
package (once you get to the point of successfully starting the BA)? When the
BA runs detect it would be found to already be installed, and thus would only
be "tampered with" if the BA goes out of its way to mess with it?
Or have I missed something?
Blair
From: [email protected]
Date: Sat, 8 Jun 2013 22:56:36 -0700
To: [email protected]
Subject: Re: [WiX-devs] WixBa\InstallationViewModel.cs code rot?
The engine doesn't make many assumptions about the desires of the bootstrapper
application today. That's purposeful because it allows the bootstrapper
application to do things that would otherwise be impossible. So, yes, the
engine could make assumptions about the correct way to handle packages after
restart but it doesn't today. We have to think through assumptions very
carefully and generally ensure they are overridable for the situations where
the assumption does not apply... or the engine can just not make an assumption.
<smile/>
In v1 (Burn is basically v1 or maybe v1.0.1 in v3.7), we chose not to make a
lot of assumptions to provide flexibility and, honestly, get it done.
On Sat, Jun 8, 2013 at 6:35 PM, Bill Tutt <[email protected]> wrote:
Shouldn't the engine just handle that little detail? I would have thought the
only interesting thing the BA might care about the PreReq package might be to
force it to uninstall (if such a thing was possible). Even that is probably a
large stretch.
Thanks,Bill
On Sat, Jun 8, 2013 at 7:09 PM, Rob Mensching <[email protected]> wrote:
You got it.
On Sat, Jun 8, 2013 at 1:08 PM, Bill Tutt <[email protected]> wrote:
It looked to me like the logic was trying to prevent the PreReq pkg (i.e. .Net
4.0 in WiX's case) from being installed after the BA was successfully
initialized since the PreReq package should have been correctly run or not run
before the BA even starts, right?
Or am I missing something a little more subtle?
Bill
On Sat, Jun 8, 2013 at 10:38 AM, Rob Mensching <[email protected]> wrote:
Actually, it looks like a very subtle bug. The intention is that a Bundle
Variable tells the BA which package is NetFX. It looks like the value got lost
(or incorrectly removed) somewhere along the way. If you are interested in a
great learning exercise, you might try to fix it.
Otherwise, would be great to have a bug opened on the issue so we don't forget
it. <smile/>
On Tue, Jun 4, 2013 at 4:59 AM, Bill Tutt <[email protected]> wrote:
Is the PlanPackageBegin code still necessary? It looks like code rot from older
Burn variable names....
Thanks,Bill
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
