How does WiX handle the deletion of the user if rollback is disabled by policy?
Rob Mensching [EMAIL PROTECTED] wrote:
On the MSI 4.5 aspect I would caution you to not get your hopes up. I
haven't looked at the final details but I thought on one pass through
the Beta I saw that all
Sure, MSI should have the ability to combine complete MSI installation
packages as phases of the installation, together with the transactional
behaviour (including savepoints on the registry..)... is this
something related to staged installation Windows Installer 4.5?
Otherwise there might be
Why not blame MSI? Sure they are dependant on Fusion, but why did they make
the choice to wait to the commit phase to call fusion? The stated reason is
to provide rollback capabilities but the problem I have with that is GAC is SN
... while rollback is nice to have, the risk of system
That's actually a very good question and I've not tested this scenario in MSI
4.5.Right now I can create a redist prereq and chain it in my bootstrapper
before my install so that the assemblies are already in the GAC.
In MSI 4.5, if I have Package 1 with component A that deploys to
Subject: Re: [WiX-users] Services + Vista + GAC
Why not blame MSI? Sure they are dependant on Fusion, but why did they make
the choice to wait to the commit phase to call fusion? The stated reason is
to provide rollback capabilities but the problem I have with that is GAC is SN
... while
The problem isn't anything to do with Vista, its because your service
has a dependency on something in the GAC and the files don't really
appear in the GAC until after the Commit phase of the install.
Just mark your service as starting automaticly and you shouldn't have
any problem. Then
Talk about to the tail wagging the dog.Customer requirements should dictate
installation behavior, not the installation technology being used.
There are a number of ways to work around this limitation of MSI. Some
involve code changes to the service exe and some require using
Wouldn't a true solution be writing a chainer (bootstrapper)?
Otherwise I agree with Christopher: these why do you think answers are
implications of something that lies in the philosophy and the state of
art - if the developer is assigned to preparing the installation, the
developer thinks like a
Just mark your service as starting automaticly and you shouldn't have
any problem. Then Windows will start the service when its needed.
How does Windows know when the service needs to be started (other than
boot time)?
Another solution that was suggested here was to use a deferred custom
action to start the service. But that also doesn't seem to work. Using
WiX 2.x branch and it results in a runtime error. The custom action
works OK if run outside of the MSI. The error returned is
Unable to schedule
In article [EMAIL PROTECTED],
=?ISO-8859-1?Q?J=E1nos_Brezniczky?= [EMAIL PROTECTED] writes:
these why do you think answers are
They're not answers, they're questions.
Over and over and over again, I see people asking how do I do task
X? without ever stating the goal. Many times X is the
: [WiX-users] Services + Vista + GAC
Well, then what do you think, why is there a ServiceControl element with start
on install functionality? Should not it be completely removed to prevent people
from thinking that they can accomplish it with MSI/WiX? It seems to me like
people just simply
I agree the probing for the real goal instead of anwering the exact question is
a good thing, but when someone replies with the `why do you think` tone, it is
clear that the presumption is that they already know the requirement and have
voided it. It's not a good way of starting a good dialog
] On Behalf Of Adam Majer
Sent: Tuesday, November 13, 2007 8:07 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Services + Vista + GAC
Hi,
I have a service I want to install and automatically start with an
installer. Now, the runtime for the service is not available until after
installer
Richard wrote:
The problem isn't anything to do with Vista, its because your service
has a dependency on something in the GAC and the files don't really
appear in the GAC until after the Commit phase of the install.
Just mark your service as starting automaticly and you shouldn't have
any
In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED] writes:
Regarding the service now, I think the problem has a lot to do with the
installation of stuff into the GAC (the recommended way of doing things
after all). All that the service needs is the C runtime, nothing special
Richard wrote:
In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED] writes:
Regarding the service now, I think the problem has a lot to do with the
installation of stuff into the GAC (the recommended way of doing things
after all). All that the service needs is the C runtime,
]]/Custom
Custom Action=caNETSTART
After=NETSTART![CDATA[FrameworkRole = 3]]/Custom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adam Majer
Sent: Wednesday, November 14, 2007 11:08 AM
To: WiX Users
Subject: Re: [WiX-users] Services + Vista + GAC
In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED] writes:
ServiceControl does more than *start* services. [...]
I know this. My question was why have the start attribute of the
ServiceControl tag?
Because ServiceControl does more than start services.
Maybe a good feature
Adam Majer wrote:
I know this. My question was why have the start attribute of the
ServiceControl tag?
Because MSI supports it for low-dependency services.
Maybe a good feature for future release of WiX may
be a delayed start of services. That is, the service is started after
installation
I don't know where to reply to this thread so I thought I'd just start here.
Personally, in the list of all the technologies to blame, I blame
Fusion. smile/
Fusion is the technology under the GAC (Fusion is actually a code name
for a few things but the GAC is very much Fusion's fault) and
Hi,
I have a service I want to install and automatically start with an
installer. Now, the runtime for the service is not available until after
installer completed because the runtime goes into the GAC (it is just
the VS2005 SP1 C runtime).
One solution is to deploy the files locally (as in a
22 matches
Mail list logo
