I managed to solve this using a type 2 ca which runs an executable to
perform the shutdown, or alternatively a type 6 vbs script which runs before
InstallValidate.
It turns out the reason I was getting errors initially is because a managed
ca cannot run as anything other than deferred (correct
Do or you need is drive Samsung.
Processor Again ati Crossfire Xpress. On Wednesday at pma long way or.
Time do is you need drive in Samsung says.
Nvidia in Intel is igp dx Cards in Works! Valkator in Sigh dwalton Sony
Dissected a Talks of About.
Announces Dedicated Stream Processor Again a ati C
Can anyone explain what the wix custom actions do in the case of a rollback,
specifically for Virtual Directories, WebSites, and Application Pools.
Thanks!
-Tina
-
Take Surveys. Earn Cash. Influence the Future of IT
Join Sour
Emma Hanna wrote:
I am installing a Windows Service which I need the user to indicate if
they want the service started on install or not, and if it is started
there is a SQL Script I have to execute. I'm using the script below to
install the service, but am not sure how to conditionally start
Dane Anderson wrote:
I have created an executable that hunts out any running instances of
our application or the one
that might be using it, and kills them (one way or another). The
problem is it is a command line
application itself, and when it runs it causes windows to toss up a
command
Don Tasanasanta wrote:
How would you go about enabling or disabling a feature dependant on
input provided by the user on a previous input screen?
Publish AddLocal and Remove control events in the Next button of the
wizard page before the feature-selection page.
--
sig://boB
http://bobs.o
I am installing a Windows Service which I need the user to indicate if
they want the service started on install or not, and if it is started
there is a SQL Script I have to execute. I'm using the script below to
install the service, but am not sure how to conditionally start the
service or how to e
Aaron Khoo wrote:
> Hi there, I'm writing an installer using Wix, and we have an
> interesting scenario. Our application has two DLLs, one is the main
> DLL (which gets updated fairly often) and the other is a resource only
> DLL (which is static, for the most part). We'd prefer not to ship the
Arnette, Bill wrote:
> A merge module should never deliver a component containing system files
> to the main feature of an application, because this may cause the
> Installer to validate and repair the application each time the system
> file is used. A .msi file that is intended to accept component
The problem: The install package I created works. HOWEVER, the customer
runs this under SMS
in some unattended mode. There is no way to control whether our
application or another application
which uses our application is running at the time of install, or not. If
it is running, it causes msiexec
to
How would you go about enabling or disabling a feature dependant on
input provided by the user on a previous input screen?
I would like my feature select screen to show the user what they can
(and can not) install dependant upon the answers they've provided on
screens previous to my feature se
Hi there, I'm writing an installer using Wix, and we have an interesting
scenario. Our application has two DLLs, one is the main DLL (which gets
updated fairly often) and the other is a resource only DLL (which is static,
for the most part). We'd prefer not to ship the latter DLL during our
update
If you do that, how do you resolve it against this:
http://msdn2.microsoft.com/en-us/library/aa368034.aspx:
A merge module should never deliver a component containing system files
to the main feature of an application, because this may cause the
Installer to validate and repair the application eac
Seems to be broken. Not sure why.
I know that the list is mirrored at
http://www.mail-archive.com/wix-users%40lists.sourceforge.net/, although
this doesn't seem to have today's posts up yet.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf O
I would imagine that you would need two projects, one for each package. You
can have both projects in the same solution. However, some versions of
Visual Studio misbehave if you have multiple projects with the same output
directory (though that may just apply to C# or VB).
I would recommend us
Alan W. Waddington wrote:
My issue is that I initially tried to create the patch to find out
that you can't use compressed files. I then changed the wxs file to
remove the compression.
To build a patch, you need uncompressed files. However, you can still
install using compressed files --
Stefan Pavlik wrote:
> I would prefer to use C++ Custom Action DLL. You should use the
> RegSetValueEx() function to write the values to registry.
> http://msdn2.microsoft.com/en-us/library/ms724923.aspx
Just for the record: I just found out why the uninstall CA
was not called: The feature on wh
Hi All
I've been trying to create a patch for our product using WiX v2.0.4221.0
My issue is that I initially tried to create the patch to find out that
you can't use compressed files. I then changed the wxs file to remove
the compression. The build still creates the msi but it's smaller t
Sergey Balobin wrote:
> Actually, the text is NOT hidden! But my custom action runs BEFORE the dialog
> is shown.
>
I don't think that's going to work. The CA runs in the execute sequence
of the setup so it can't pass properties back to the MSI client, which
is where the UI runs.
--
sig://
Michael Carlisle wrote:
If I run the CA as immediate I get an error on uninstall, also when I tried
moving the CA in the sequence it errors. I also notice that the files in use
check happens before elevation so my CA woudn't have permissions anyway.
The Files in Use model is to report, not fo
Friedrich, Oliver wrote:
For our Solution we need to build 2 packages, one for the client and
one for the server application. Those packages use pretty much the
same code, thats why they are in one Solution of VS2005. Now, much
WiX-code could be shared between those to packages, too. So i tho
André Pönitz wrote:
> Does that mean I can build a single .msi that can be installed
> on 32bit and 64bit machines (provided that I get the stuff
> inside the package right)?
>
Not really. 32-bit packages can't install 64-bit components. 64-bit
packages can't run on 32-bit Windows. For the mo
vij wrote:
> If I do that, I have to make the complete merge module as a single
> feature in my MSI and I will not be able to classify my
> components(which are part of merge module) into features, so I don't
> want to do that.
Create multiple merge modules, one per feature.
--
sig://boB
htt
If I run the CA as immediate I get an error on uninstall, also when I tried
moving the CA in the sequence it errors. I also notice that the files in use
check happens before elevation so my CA woudn't have permissions anyway. I
could remove the RM Files in use dialog altogether which will then n
Stefan Pavlik wrote:
> The Registry Table of Windows installer does not support such
> action. see MSDN:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/registry_table.asp
Too bad...
>>> If you need during uninstallation to write something to registry you
>>> should
You can increase the level attribute of each feature. If this is set to
higher than the INSTALLLEVEL property, the feature will be disabled by
default. I believe INSTALLLEVEL is set 100 by default (though don't quote me
on that).
On 11/15/06, Brandon Tyler <[EMAIL PROTECTED]> wrote:
I have t
Hello, All!
I`m writing an installation in WIX
1. During the installation I run a Custom-Action that doing something and make
record in the registry.
2. I want the text in ExitDialog to be changed depends on the registry changes.
I created a Custom-Action DLL function that checks the registry a
I have the same question. I was wondering how you set it to false or
something? Anyone?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Don
Tasanasanta
Sent: Tuesday, November 14, 2006 4:59 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-user
Hi again...
André Pönitz wrote:
>> But I know that you cannot write to the registry during
>> uninstallation using standard action WriteRegistryValues.
>
> Urm, that's bad. Do you know why?
The Registry Table of Windows installer does not support such
action. see MSDN:
http://msdn.microsoft.com/
> Hi André,
Hi Stefan.
> I realy don't know what is wrong.
>
> Maybe you should try to use the to avoid
> conflicts with XML.
Well, you did know what was wrong after all. CDATA helps indeed,
&Netlm is no valid XML...
> But I know that you cannot write to the registry during
> uninstallation us
Hi André,
I realy don't know what is wrong.
Maybe you should try to use the to avoid
conflicts with XML.
But I know that you cannot write to the registry during
uninstallation using standard action WriteRegistryValues.
If you need during uninstallation to write something to registry you
shoul
David Walton wrote:
> I have been using
> http://sourceforge.net/mailarchive/forum.php?forum=wix-users but it doesn't
> seem to be showing posts after 2/10 even though I'm getting digests. Is there
> another site or am i being dumb.
Dunno, but gmane is still working fine:
http://dir.gmane.org
Hi all.
I want to write a certain registry key during an installation
and the same key with a different value during uninstall.
So I thought I could have something like
(&Netlm = 3) AND NOT (!Netlm = 3)
(&Netlm = 2) AND (!Netlm = 3)
under the main ('Ne
Title: [WiX-users] Votive V3 and multiple .msi support?
Hello again,
Using Votive V3 is pretty nice, though one thing is a little bit anoying...
For our Solution we need to build 2 packages, one for the client and one for the server application. Those packages use pretty much the same cod
Hi all,
I just stumbled over the 's' in the Package's "Platform_s_"
attribute and then over the documentation
"The list of platforms supported in the package."
Does that mean I can build a single .msi that can be installed
on 32bit and 64bit machines (provided that I get the stuff
inside the
To build the merge module, you could run a script over the wix files and
rewrite them out to disk,
using a RegExp to remove the DiskId bits. You would then use these new files
as the source files
for your merge module.
Rob
vij wrote:
> If I do that, I have to make the complete merge module a
If I do that, I have to make the complete merge module as a single feature in
my MSI and I will not be able to classify my components(which are part of
merge module) into features, so I don't want to do that.
Is there any other way?
thanks
Vij
Bob Arnson <[EMAIL PROTECTED]> w
hi
I have been using http://sourceforge.net/mailarchive/forum.php?forum=wix-users
but it doesn't seem to be showing posts after 2/10 even though I'm getting
digests. Is there another site or am i being dumb.
regards
Dave.
---
38 matches
Mail list logo
