I note that there is MSI interop coded in wix, and there is another
msi interop C# library floating around
(http://workspaces.gotdotnet.com/msiinterop).
Can I call an entry point in a .net dll from a wix script? (or rather,
can msi files handle this).
Also, why is the MSI Interop classes in wix
I am trying to read a registry key and setting that as a property but
for some reason it's not working. The installation interrupts with the
launch condition message defined in WIX.
I have a registry key created from another software
HKLM\Software\[Manufaturer]\RuntimeInstalled with a value of "ye
Adriaan wrote:
> How can I bypass the Launch Condition on Uninstall?
>
Use a condition of "Installed OR ..." so the condition is true when the
product is being uninstalled.
--
sig://boB
http://bobs.org
-
Take Surveys.
Hi,
I have a setup package that I created and I also have other setup
packages that are plug ins to the main application.
Now the installation of the the main app is checked via a ,
but when I uninstall the main application first and then the plugin
setup I get a fatal error saying the main applic
Dhaval Patel wrote:
> I have an MSI that installs numerous files - some of these may be
> shared by other components on the same box at a later time. I need to
> ensure that these specific files are not deleted upon uninstallation
> of my MSI. An example would help!
If the same components are s
Now I thought/hoped this would be trivial but no.
For various reasons we need to create an installer that
1) copies the original file to a well defined location
2) updates the original file with a newer version
On Uninstall we need to
1) Remove the patched version
2) Copy the original file back
We have been using WIX for building an MSI file for a new tool called Migration
Tool for Dynamics AX.
We are running into some issues with the msi files that were generated using
the Wix. We have to run APIScan on the msi before we can release the tool. The
purpose of the APIScan is from the on
Hi,
I know it is strange requirement (customers ... you know :-) but I'd like to
be sure that it is not possible to install IIS (Windows Server 2003 or 2000)
as a part of MSI setup. I know that "installing" IIS means rather "changing
the system configuration" but it might be scriptable somehow.
I was able to fix this issue - my windows form reads and writes values to
and from the registry... it turned out that the way WIX was creating the
registry key was making it unreadable somehow. The weird part was that the
form was able to read from a couple of keys (both created by WIX), but
unabl
To do that I need to conditionally set the command line arguments with
REINSTALLMODE=vomus REINTALL=all when the product is already installed. Does
anybody know how to do that using the Visual Studio 2005 GenerateBootstrapper
task?
-Matthew Rowan
-Original Message-
From: Stefan Pavlik
I think I understand this a bit more now and it would appear to be
limitation of the element.
To register .Net COM components you need to set the InprocServer32 to
"mscoree.dll" and I can't see how you can do this with the
element as this is not a file that is installed by your setup. To work
I believe you set the Component Attribute Permanent="yes"
Dhaval Patel-4 wrote:
>
> I have an MSI that installs numerous files - some of these may be shared
> by
> other components on the same box at a later time. I need to ensure that
> these specific files are not deleted upon uninstallation o
Ok, I will go that route. THANK YOU for your quick responses!
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of K-ballo
Sent: Wednesday, February 14, 2007 2:42 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to use a Property
You cannot set a property to the value of another property in that way.
That is necessary to prevent creating circular references. What you
should do is call a CustomAction that will set the value of VDDIR
property after MAINDIR has been set. You would have to do something like
this:
K-bal
Thanks for the quick response.I just tried your suggestion and
unfortunately I got the same result.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 2:11 PM
To: Nick Hennemann
Cc: wix-users@lists.sourceforge.net
Subject: Re: [
Have you tried:
I think that should resolve to what you want.
On 2/14/07, Nick Hennemann <[EMAIL PROTECTED]> wrote:
*I have the following Property "MAINDIR" and it is populated correctly
from the registry….*
And then I have another property call "VDDIR" and I use
I have the following Property "MAINDIR" and it is populated correctly
from the registry
And then I have another property call "VDDIR" and I use the "MAINDIR"
property to help build the path for my virtual directoryhowever I
can see that instead of the path being
I have an MSI that installs numerous files - some of these may be shared by
other components on the same box at a later time. I need to ensure that
these specific files are not deleted upon uninstallation of my MSI. An
example would help!
Thanks for the help, guys!
---
Wix syntax isn't something I'm very familiar with, but in general you
need a feature-action condition based on the feature transitioning to an
installed state, &FeatureName=3.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of dave_c
Sent: We
What I did was make a small bootstrapper application that contains both MSI's
one that does per-user and one that does per-machine. My bootstrapper
prompts the user to select one and then it launches the appropiate MSI.
Mike Robertson wrote:
>
> Simple question but I can't find a definitive an
I have one file > 2.0GB in size. Is there a way for the Installer to chop up
a file into smaller sizes, so it is managable. I need it to be a process
that the installer does because it needs to also reintegrate them during
installation. I don't know how to do this though. I tried seeing if
sli
My install creates virtual directories under "Default Web Site" - "All
Unassigned" IP.
The IP, however, is guaranteed to change to a static IP address which
botches the uninstall of the virtual directory. So I would simply like
to delete it regardless.
Fr
Not today. Kinda' weird scenario, what are you doing?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
Sent: Tuesday, February 13, 2007 2:51 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Delete a virtual directory
Is there a command to delete a virtual
No, it is not possible but it should have been. I've voiced my complaints to
the Windows Installer team.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Robertson
Sent: Wednesday, February 14, 2007 3:27 AM
To: wix-users@lists.sourceforge.net
Subject
Hi there,
I've managed to find some more information on the subject and think I have
solved the problem I was having.
In the CustomAction I've changed the condition from NOT Installed to
$Install=3
I.E. Only run if the client component is being installed. I've tried it o
I came across this post whilst searching for an answer to the same problem.
I assume you are talking about the WiX tutorial on
http://www.tramontana.co.hu/wix/lesson4.php; if so, then the problem comes
from the fact that the author includes a single quote in this line:
> Hello everybody
>
> I
Simple question but I can't find a definitive answer here. Is it possible to
build a
single package that will install on Vista per-user without asking for admin
privileges
but that will also be able to install per-machine (and ask for elevation)?
All I can
find here is InstallPrivileges, but that'
Hi again...
Matthew Rowan wrote:
> Thanks for the quick reply Stefan. What I have found is that when I build a
> new installer for the next minor version it does not launch in Maintenance
> mode because the package code is different, but the product code is the same
> and I get the error messag
Thanks for the response.
This would make sense. I only want to run this customAction if I am
installing the client side of things. When I select the server side to be
installed the executable is not selected for install (it is a feature of the
client).
So I guess I need to add extra control to t
Thanks for the quick reply Stefan. What I have found is that when I build a new
installer for the next minor version it does not launch in Maintenance mode
because the package code is different, but the product code is the same and I
get the error message "Another version of this product is alre
30 matches
Mail list logo