DOH! MODE not MOVE
msiexev /I foo.msi REINSTALL=ALL REINSTALLMODE=vomus
Thanks for the help, this worked!!
Ryan Taylor
Office (207)-504-5294
rtay...@penbaysolutions.com
www.penbaysolutions.com
-Original Message-
From: Ryan Taylor [mailto:rtay...@penbaysolutions.com]
Sent: Thur
This is dev box. I patched the installer and ran
msiexec /I foo.msi REINSTALL=ALL REINSTALLMOVE=vomus
However, I receive the following error:
Another version of this product is already installed. Installation of this
version cannot continue. To configure or remove the existing version
Is this on a dev box or deployed? If dev box, the easiest way out of this
problem is to fix the msi and recache it with msiexec /i foo.msi REINSTALL=ALL
REINSTALLMOVE=vomus. Then you should be able to do your uninstall.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip
I believe that I have created an installation that I cannot uninstall due to a
thoughtless condition. Behold!!
I want the installer to fail if PowerShell is less than version 2.0. However,
I do not want to perform this check on uninstall. I should be able to
uninstall my applica
The solution was: [#RegisterHttpModulePS1]
This formatted string will return the full location of the installed file.
This was described here: http://www.tramontana.co.hu/wix/lesson6.php under
section 6.3 Formatted Strings.
The 'complete' solution is:
Ryan Taylor
Office (207)-504-5294
rtay.
Say I have a file defined as:
And a custom action defined as:
How can I reference the full path of the installed file (e.g. C:\Program
Files\My App\register-httpmodule.ps1) such that I could include it as a
variable in CustomAction/@Value as I have with t
@Advertise="yes" requires that the target be a component, not a file (the
system will eventually resolve it as the component's keypath).
-Original Message-
From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com]
Sent: Wednesday, November 10, 2010 12:01 PM
To: General discussion for Windows
I haven't tested this, but IIRC 32-bit processes get the "32-bit"
environment variables, and the fact that candle is marked as a 32-bit
program should make the following work on both platforms:
-Original Message-
From: Mike Edenfield [mailto:kut...@kutulu.org]
Sent: Thursday, November
Hi,
Is there a way to tell, while building an installer package, whether the
building system is a 32-bit or 64-bit version of Windows?
We are starting to move some of the machines in our build farm and
developer's workstations to 64-bit Windows systems, but they are failing
on the WiX builds beca
Adding the line did the trick. I have
not even noticed - I removed it when we decided not to have UI.
Thanks a lot Neil!
Lena
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, November 11, 2010 3:56 PM
To: General discussion for Windows Installer XM
Have you got something like this in your code:
I have to say I don't see why this would only be required on some OSs.
Have you checked the version of "Windows Installer" on each of the
targets? May be that would explain the difference.
Neil
-Original Message-
From: Lena Vinogra
This is exactly the type of thing I was looking for. My installation will be
much simpler as a result. Thanks!! The link is helpful too, I have found that
the online help for WiX 3 is often broken. I found additional content
describing how to use binder variables with assemblies that are not i
This is exactly the type of thing I was looking for. This will make my
installation much simpler. Thanks!!
Ryan Taylor
Office (207)-504-5294
rtay...@penbaysolutions.com
www.penbaysolutions.com
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, November
Hi,
I am observing a bizarre behavior - when running installer with no UI on Win XP
32 bit the dialog is missing the description text.
The initial small dialog with title "Windows Installer" saying "Preparing to
install.." shows up, then followed by the dialog with no text.
The same installer ru
You can use the linker bind variables.
!(bind.assemblyFullName.)
Doc links seem to be busted so here's a cached version of the page (see the
very bottom of the page)
http://webcache.googleusercontent.com/search?q=cache:q5MngQTFO1cJ:wix.source
forge.net/manual-wix3/light.htm+wix+bind+assemblyfull
Take a look at "Binder Variables" in the help file, I think they do
exactly what you need. If your assembly is not in the GAC you will need
to set the File/@AssemblyApplication and File/@Assembly attributes.
Neil
-Original Message-
From: Ryan Taylor [mailto:rtay...@penbaysolutions.com]
S
How might I obtain an assembly's fully qualified name for use in a property? I
would like to obtain this information either at compile time via binding, or at
runtime so that I may register a .NET assembly with IIS using a fully qualified
name.
For example, I need to add the assembly to the ass
The '"/c" switch in the commandline' is - how can I put this - in the
commandline ;). It's a parameter of the command, just data as far as WiX is
concerned. It can't affect Wix's behaviour.
> -Original Message-
> From: David Binkovic [mailto:david.binko...@googlemail.com]
> Sent: Thursd
No, the CA DLL doesn't get installed at all if you've set it up correctly. It's
a binary stream in the MSI and is available at uninstall time.
Hard to tell what's wrong without seeing your WiX code and the relevant bits of
a verbose log.
> From: sagar shinde [mailto:sagar.i...@gmail.com]
>
>
Hi,
I think u got it wrong,
i did it in same way
u can use that dll in custom action while installation but at uninstall time
that dll will be uninstalled with other files and i want to use it at
uninstall timehow can i do this
On Thu, Nov 11, 2010 at 3:08 PM, Umeshj wrote:
>
>
> Why are you co
Why are you copying this to the user's system?
Just use it like this:
refer to it with the id.
This way it will stay with your MSI and uninstall will have access to it.
Umesh
sagar shinde wrote:
>
> Hi,
>
> I created one custom action dll file,
> which is copied to destination computer.
Hi,
this statement doesn't even compile here:
"The CustomAction/@Value attribute cannot be specified without
attribute Directory or Property present."
But again, even when using the "/c" switch in the commandline,
CAQuietExec still prints out everything inside the "Value" attribute
to the .msi lo
22 matches
Mail list logo
