Hi All!
I have error on uninstall if some files in my install dir are deleted
manually (for example).
When I execute install.msi, I've following message: Another version of this
product is already installed...
If I try uninstall throught Add|Remove Prg, system promt me select install
source
Bob Arnson-6 wrote:
Anidil wrote:
I want to create a registry entry after the application is installed.How
do i
get this functionality in the same msi?
What do you mean by after the application is installed?
Create the registry entry after the application files are installed in
My understanding is that the order that shortcuts appear is
usually alphabetical. But ultimately it is a user-setting. Schortcut
groups are just folders and I believe that the arrange by setting
applies.
Windows does store some special metadata about ordering though, since
you can
Yes, the .wixproj has Culturesen-US;en-GB/Cultures
Is it worth posting my .wixproj file?
Bob Arnson [EMAIL PROTECTED]
24/07/2007 03:28
To
Martin Evans [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] MSBuild / localisation variable problem - culture
information
Ok, thanks a lot for your explanation.
So if I correctly understood what you said, I must declare my custom
action as deferred. So I guess I write it this way:
CustomAction Id='ConfigureHttpConf' BinaryKey='apmwsinst.dll'
DllEntry='apm_edit_conf' Execute='deferred' Return='check' /
I'm looking for a good way to include/embed/combine 2 installations. I
have an installation that depends on the product of a different vendor.
The second installation is only available as an MSI package. My wish is
to fully combine the installations, so the users can also pick the
components in
after installing the package ,when we go to the add remove and press change it
opens a dialog box repair ..how should we implement that
-
DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the
property of Persistent Systems Pvt. Ltd. It is
nant gives the following error: Build File c:\tools\wix.include does not exist.
I suppose in reference to this include.
include buildfile=..\..\..\..\wix.include
unless=${property::exists('wix.properties.defined')} /
so, two questions where are the includes in the example? and how do I
set the
Hi,
I need to write a key to the registry pointing to the location of my
program. It is in the ProgramFilesFolder. How do I refer to this
variable in the registry key?
with the following I get an MSI out but it crashes halfway through;
Directory Id='TARGETDIR' Name='SourceDir'
I think you want to change ${var.MYDIR}\hotkeys.exe to [MYDIR]hotkeys.exe
Rob
bryan rasmussen wrote:
Hi,
I need to write a key to the registry pointing to the location of my
program. It is in the ProgramFilesFolder. How do I refer to this
variable in the registry key?
with the following
Jeroen,
A bootstrapper (also known in some places as a chainer) is the option to
use.
Microsoft Installer does not support two simultaneous installations.
(There was a custom action intended to support nested installations, but
it was deprecated long ago. Based on comments from others, I
I'm attempting to add permissions to an existing registry key during
installation. The problem is what happens when I try that is the
original key is overwritten by a new key. The new key has the correct
permissions but this causes a lot of problems. The tag I'm using is:
Component
From: Rob Hamflett [EMAIL PROTECTED]
I think you want to change ${var.MYDIR}\hotkeys.exe to [MYDIR]hotkeys.exe
Hmm, still doesn't work. Actually I think this is wrong:
Registry Root=HKCU
Key=Software\Microsoft\Windows\CurrentVersion\Run
Action=createKey
I thought it might be better like this:
Registry Root=HKCU
Key=Software\Microsoft\Windows\CurrentVersion\Run
Action=write Name=SIHotkeys
Value=[MYDIR]\hotkeys.exe Type=string /
but that didn't work either. Sorry to be asking what are no doubt
stupid questions
The WiX references to keys are the same concepts as registry keys. The
Type=string is how you
tell WiX you want a string value. When you say it doesn't work, what does it
do?
Rob
bryan rasmussen wrote:
From: Rob Hamflett [EMAIL PROTECTED]
I think you want to change
Hi everybody,
I'm trying to deliver a product with a msi, and I need help. I want to
separate this product in two part, the big and commun one with all the
main program, and the small and specific one with some configuration files.
The idea behind this separation is to make easier futurs
Hi,
I have a scenario where a product has a config file that gets installed
with some default values at initial install. The user may subsequently
add or remove lines from this file. Therefore on upgrade I do not want
it to get overwritten with the initial version again. The file is
actually
Hi,
I'm attempting a silent install in Windows Vista. However, the setup does
not work and the log gives the following message:
MSI (s) (98:48) [09:55:23:197]: MSI_LUA: Installation UI level is silent, no
credential elevation is possible
In Windows XP, the silent install works with no
Vincent Ho wrote:
In Windows XP, the silent install works with no problems. Is there a way to
grant credentials for silent installs within Vista?
Not without the admin disabling UAC, no.
If an installer could silently give itself admin rights there would be
little point in UAC at all!!
Tony
This is a known issue with UAC in Vista. You can choose to do a /QB for brief
instead of fully silent and then you'll actually see/aprove the eleveation
request. Otherwise the reccomendation is that you run the package from an
elevated process ( such as using a tool like SMS 2003 ) as to
The flip side is that there is very little use to a fully silent install if an
interactive step is needed to invoke it.
Tony Hoyle [EMAIL PROTECTED] wrote:
Vincent Ho wrote:
In Windows XP, the silent install works with no problems. Is there a way to
grant credentials for silent
This option sets the msidbComponentAttributesNeverOverwrite bit in the
Attributes column of the Component table for the component.
If you use @Advertise='no' with the Class, Extension, ProgId, MIME, Verb
elements, WiX generates Registry table entries rather than the corresponding
Class (etc)
This isn't your key to modify so I wouldn't advise doing this. It'll weaken
system security to an extent - your users won't thank you. You shouldn't
need to modify the permissions on this key to allow anything running as
NetworkService to write log entries.
If you're creating a log event
Sorry, either mark as deferred and schedule between InstallInitialize and
InstallFinalize, or mark as immediate and schedule after InstallFinalize. If
you try to schedule a deferred action after InstallFinalize I believe you'll
get a runtime error.
If you use an immediate action after
Hi Bob,
Yes, it seems to be a Wix tool which is producing error. Currently its a gray area for us that why this Assembly tag is not supported, can you you throw some light on this?
Thanks.
Jaivardhan
From: Bob Arnson [mailto:[EMAIL PROTECTED]Sent: Tue 7/24/2007 7:45 AMTo: Rob WickhamCc:
Hi there,
One of our data files is about 3.5 GB uncompressed and light.exe crashes
with the following exception.
The MSI builds fine if I exclude the huge file. Is this a WiX or Windows
Installer limit? If it comes from Wix, is there a workaround?
I am using Windows Installer Xml Linker version
Hello, I'm getting an error when compiling my wix under VS. The following is
the error information, I believe it's complaining about the large number of
periods we use in project names. Can someone let me know if that is a bug?
Error 1 Ill-formed preprocessor variable '(
Hi all,
I'm a relatively new user of WiX, and have just subscribed to this mailing
list - hopefully to get this question answered. I've searched Google, but
couldn't find an answer, and the search of the mailing list archives is
currently not working. Anyhow here's the question and situation
Anidil wrote:
Create the registry entry after the application files are installed in the
system.
(Say create the reg entry if application executable is found in the
installation path (dynamic))
You can use FileSearch to see if a file already exists on the system
then use that property
Martin Evans wrote:
Yes, the .wixproj has Culturesen-US;en-GB/Cultures
Is it worth posting my .wixproj file?
Maybe. I don't know why it wouldn't get passed to the command line.
--
sig://boB
http://joyofsetup.com/
-
This
Jaivardhan Agrawal, Noida wrote:
Yes, it seems to be a Wix tool which is producing error. Currently its
a gray area for us that why this Assembly tag is not supported, can
you you throw some light on this?
Please post the WiX source you're compiling and what the exact error
message is.
--
Jeroen Davelaar wrote:
What are the alternatives; bootstrapper or a customaction that
installs the second package?
A bootstrapper -- two MSIs can't be installed during one installation
transaction.
--
sig://boB
http://joyofsetup.com/
Tony Hoyle wrote:
Not without the admin disabling UAC, no.
If an installer could silently give itself admin rights there would be
little point in UAC at all!!
And if you use /qn, you're explicitly asking for no user
interface/interaction; throwing up a modal prompt counts as UI, I'd
Quattro IV wrote:
Hello, I'm getting an error when compiling my wix under VS. The
following is the error information, I believe it's complaining about
the large number of periods we use in project names. Can someone let
me know if that is a bug?
You're missing a closing paren:
Name=
bryan rasmussen wrote:
nant gives the following error: Build File c:\tools\wix.include does not
exist.
I suppose in reference to this include.
include buildfile=..\..\..\..\wix.include
unless=${property::exists('wix.properties.defined')} /
so, two questions where are the includes in the
Emilien Bertin wrote:
So I want the big msi to install the 2 msi. I employ the CustomAction
type 50 (with [SystemFolder]msiexec and /quiet /i path_to_small_msi
). But it seems impossible to install two msi in the same time.
That's correct. You need to use an external .exe bootstrapper.
--
Jim Fagan wrote:
When I uninstall and there's only one instance on the server, the
uninstall works as planned. However, if there's more than one
instance, then the keys remain in the registry - probably because the
Key is tied to the same component with a different ProductID.
That's
Anyone have suggestions on how to handle the situation where setup fails on
uninstall because the website associated with a virtual directory no longer
exists? It is possible for users to re-create the website in IIS manager and
then run uninstall, but it seems it would be better to simply
38 matches
Mail list logo
