Balakrishna.BK wrote:
Hi All,
When I click on msi to install, I get an error message to
install the software using setup.exe only. How can I bypass
this and install from msi directly. Basically I need to
create install log file.
msiexec /i file.msi /l*v file.log
I am expecting
Rob Mensching wrote:
MSI SDK ships with a VBScript that allows you to execute SQL
statements against an MSI. I think it is called WiSql.vbs or
WiRunSql.vbs or something like that.
WiRunSQL.vbs, indeed. I'll havbe a look.
Thanks,
Andre'
incarnations of the .exe and only the final one is really needed.
Is there a way to create a patch containing only that
final version but which is still able to patch all
versions?
Andre'
--
André Pönitz, Software Developer
WASY GmbH, Institute for Water Resources Planning and System
Research
I wrote:
Hi all.
Is there a method to create a patch that is able to
update all stages of a given product?
Say I have a product A.B.0 containing a certain exe.
This exe is changed in each patch, i.e. in 0-1, 1-2
etc.
I want a patch that's able to upgrade A.B.2 as well
as A.B.4 to,
Hi all.
Is there a simple way to extract a propety from an .msi
on the commandline?
I seem to need the ProductCode of the UpgradeImage
in the TargetProductCode item when creating a patch.
[Is that true btw?]
Andre'
[Sorry for the extensive signature. New rules...]
--
André Pönitz, Software
Hi all.
I am curently trying to create a working .msp with Wix v3
So far I followed the Wix v2 tutorial and created a .msp
that is supposed to replace in file 'a.txt' the contents
'old stuff' by 'new stuff'.
When I run
msiexec '/l*v' PatchLog.txt /p patch.msp REINSTALL=ALL REINSTALLMODE=omus
Simon Topley wrote:
I'm not sure how much use this will be to you, but I ran into
a large number of issues with patching, I haven't touched it
in a while as we are now thinking a full re-release is going
to be cleaner. I created a self extracting exe file using
iexpress.exe (standard part
Ricardo Lopes wrote:
I don't know why it install one component and not the other
(at least i can't find it) if they belong to the same feature
(and only one).
You could have a look at the installation log (i.e. the file
log.txt produced by running 'msiexec /l*v log.txt /i yourinstaller.msi'
dave_c wrote:
I'm on the lookout for a simple example that illustrates
patching using WIX.
The functionality requried is
Step 1. Apply original application and associated code.
Step 2. Apply a patch to some of the files from step 1
Step 3. Have ability to remove the patch software,
dave_c wrote:
For clarity.
I should have added that when I ran evertyhing. I installed Error.msp which
laid down my foobar file.
When I applied the patch there were no updates to the Control Panel
Add/Remove programs but the updated foobar file was installed.
In this control panel, do you
Alex Henderson wrote:
My client wants his installer to have an uninstall shortcut, but I can't
seem to quite get it right... after reading some posts I ended up with this:
Property Id=UNINSTALLCMD Value=MSIEXEC.EXE /x [!PRODUCTID] /
And also...
Component Id=Uninstaller
Hi all.
My boss is currently very disappointed with the startup
times of my latest installers.
It seems to spend a lot of time in the CostFinalize action
[His machine is not much slower than mine, however the
harddisk is nearly full, maybe that's an issue]
Is there something I can do about it?
Bob Arnson wrote:
[...] MSI doesn't let you configure rollback storage except to
disable it entirely.
Can this be done from inside Wix? If so, how?
Andre'
-
Using Tomcat but need to do more? Need to support web services,
Rob MacFadyen wrote:
To deal with dark crashes what I've done in the past is some creative
editing using Orcas. Usually this means removing any offending entries and
or tables that dark is having trouble with. From the error message it looks
like dark doesn't like the value in a column named
I get an unexpect result when running dark (Version 3.0.2211.0) on one
of our old .msi files created by InstallShield.
dark -nologo -x data ../GeoDAta eXchange.msi geodax.wxs
GeoDAta eXchange.msi
dark.exe : error DARK0001 : Cannot set column 'KeyColumn' with value 0 because
it is less
David Thielen
It's all peer to peer, no server. So each AddIn listens for the UDP
broadcasts and replies to the broadcaster saying they exist.
The broadcast occurs at startup and if the number of replies is greater
than the license allows that AddIn is disabled. So the first N can run,
the
Ravikumar Gopinath wrote:
Hi,
By default, WIX treats all components as 32-bit. Our
installation package will install either 32 bits or 64-bits
binaries and we don't have any mixed files going into
separate directories. Is it possible to mark all components
as 64-bit?
Not as far as I
Rob Mensching wrote:
That is helpful. So, here's a bit more of breakdown:
1. 8 seconds, actual WiX processing (linking)
2. 3 minutes 30 seconds, calculating file hashes and
assembly information
3. 5 minutes, compressing files
4. 20 seconds,
Rob Mensching wrote:
There are many threads about the work going on in WiX v3 to
create a chainer. In fact, it's already there (even though
it needs a lot more work). There is also a chainer that
ships with VS (that is freely available, I think).
Is this the ideal? No, but we (i.e.
Rob Mensching wrote:
What version of the WiX toolset are you using?
[EMAIL PROTECTED]:~ light
Microsoft (R) Windows Installer Xml Linker version 3.0.2211.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
That sounds like an unexpected performance problem.
Glad to hear that
Hi all.
I have the problem that longer runs of 'light'
make my desktop machine basically unusable for
any other task in that time (unless one counts
the display of partially updated windows as
'task'...)
I do not really understand the reason for that.
Windows thinks my desktop machine has two
Stefan Krueger [MVP] wrote:
A bootstrapper is the officially recommended method to chain
two msi setups.
And what is the officially recommended method for creating
chainers? Everybody rolls his own from scratch?
It's hard to believe that such a basic functionality as
chaining two
Tony Hoyle wrote:
André Pönitz wrote:
One is not allowed to ignore ICE57 errors for Windows Vista
logo certification (even if everybody agrees that the errors
themselves are bogus and should be ignored ...)
I'd try to talk them into changing that..
I am not sure this is worth trying
Hi all.
There seems to be 'automatic' properties
StartupFolder (here locally: C:\Dokumente und Einstellungen\All
Users\Startmenü\Programme\Autostart)
and
StartMenuFolder (here locally: C:\Dokumente und Einstellungen\All
Users\Startmenü)
However, I'd like to access the level inbetween,
Tony Hoyle wrote:
Simply using [StartupFolder]\Programme does not cut it as the 'Programme'
part is language-dependend.
ProgramMenuFolder
But with ALLUSERS=0 [ProgramMenuFolder] is in the user's hierarchy
whereas StartupFolder and StartmenuFolder are under 'All Users'
I basically want
Johan Appelgren wrote:
So the answer to the initial question is that windows installer is
broken, and I should just ignore the ICE57 error?
I think 'yes, and not necessarily'. Have a look at hack I just
posted in the 'Solution for StartMenuFolder x StartupFolder ?'
thread today.
I'm trying
Arnette, Bill wrote:
Non-Windows Installer installers use the SharedDlls registry
key to refcount the usage of common/shared dlls. By default
Windows Installer will only increment that refcount if it
already exists so that the other installer will track the
refcount properly if a WI
Can anybody explain me why I get the 'Action: Null' decision in some cases,
but not in all?
MSI (s) (68:C0) [12:28:49:678]: Component: Hasp_52; Installed: Local;
Request: Absent; Action: Absent
MSI (s) (68:C0) [12:28:49:678]: Component: NetlmProgramMenu; Installed: Local;
Request:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
André Pönitz
Sent: Wednesday, December 20, 2006 12:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installed: Local; Request: Absent; Action: Null ?
Can anybody explain me
Mike Dimmick wrote:
If you don't think you need install-on-demand,
repair-on-launch, or the ability for domain administrators to
advertise software through Group Policy, by all means use
non-advertised shortcuts.
Which, unfortunately, does not seem to work with Wix v3 and
validation. At
Matthew Janulewicz wrote:
I don't think there is an elegant way to do this, as the Wix
tools (or any other tools for that matter) can't predict what
ComponentRef's you want under which features.
Everything under a certain directory put in one feature seems
to be a fairly good first
David Thielen wrote:
I took a look at 7Z but according to it's docs it doesn't
even have self-extracting zips.
So either you haven't looked hard enough (which I don't
want to imply) or docs are wanting nowadays in general...
I have the following snippet in my Makefile for creating
a
Bob Arnson wrote:
Scott Palmer wrote:
Then I get the following error:
Error LGHT0204: ICE43: Component thing1 has non-advertised shortcuts.
It should use a registry key under HKCU as its Error LGHT0204: ICE57:
Component 'thing1 ' has both per-user and per-machine data with a
Scott Palmer wrote:
I'm using WiX3.
I am trying to make a shortcut as part of installing a
component. The shortcut is to a launcher application that is
installed in another component with a command-line argument
that has the path to a file in the component that contains
the shortcut.
Dana Gutride wrote:
When the already installed version was created, were those
uninstall custom actions included in it? The installed MSI
is called to handle the uninstall sequence, any changes you
make to your uninstall sequence will only affect the new
installers you create.
As far
I have a product that needs to run custom actions
when uninstalling. This works.
However, when trying to install a major upgrade
on an already installed version the older version
is properly found (i.e. I get something like
MSI (s) (3C:DC) [09:51:36:582]: PROPERTY CHANGE:
Adding
Steve Bennett wrote:
Hi all,
Hi Steve.
I'm trying to automatically maintain wix source files to
generate a .msi as the final stage of a build process. That
is, each time a build is done, I'd like to update a wix
source file to refer to the latest set of files that are
designated as
Rob Mensching wrote:
Is MSI that bad? I mean, I know that declarative programming
is very different from procedural programming but the Windows
Installer handles a lot of things very well. Probably my
biggest gripe is that the Component Rules suck. Is there
something you think is worse
Tony Hoyle wrote:
André Pönitz wrote:
One of my biggest gripes with MSI so far is that it dead slow
(which is, of course, a very subjective impression).
Not so subjective when it comes to patching... VS2005 SP1 took 6 hours
on one machine here. 30 minutes even to get to the EULA
André Pönitz wrote:
Rob Mensching wrote:
Is MSI that bad? I mean, I know that declarative programming
is very different from procedural programming but the Windows
Installer handles a lot of things very well. Probably my
biggest gripe is that the Component Rules suck
[EMAIL PROTECTED] wrote:
I have a very similar issue whereby Vista Logo testing
automatically fails any component that has more than one
shortcut within it. As such I have removed a shortcut from
the component containing the app's main executable and have
created a new component that
Ok, let's try again.
I have the following code in my test installer.
Property Id='ALLUSERS' Value='1' /
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='Desktop'
Component Id='desktop_folder'
Guid='{E88B9843-688B-40FA-8BD3-E137EAA1D18D}'
Rob Mensching wrote:
Was this issue ever figured out?
Media
Id=1
Cabinet = setup.cab
CompressionLevel = high
EmbedCab = yes /
Wouldn't the 'EmbedCab = yes' stanza be responsible for
such a 'warning'?
Andre'
Bob Arnson wrote:
André Pönitz wrote:
However, this page only contains three Sponsor Links,
no trace of any Wix related documentation at all.
This gives the wrong impression IMHO.
Anyone can contribute documentation.
I was not aware that mere users were supposed to contribute
Rob Mensching wrote:
2. There is a block of documentation in the WiX.chm file
that should be in every binaries.zip. You can also go to
http://wix.sourceforge.net and see the online manual and the
online tutorial there. We can always use more documentation
but there is definitely
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
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
Component Id='install_reques' Guid='x'
RegistryValue Id='InstallNetlmCommand' Root='HKLM'
Hi André,
Hi Stefan.
I realy don't know what is wrong.
Maybe you should try to use the ![CDATA[Condition]] 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
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 write
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
This wix v3.
I have a wix based merge module installing some exe + auxillary
stuff. In the main .wxs I can use this merge module and
everything works fine so far.
Now I'd like to add shortcuts in the startmenu and associate
a few extensions with this .exe - which seems to works at least
for
Is there a possibility to change the icons in the
'feature selection tree' to simple checkboxes?
I think I read the relevant parts in Wix Schema and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/selectiontree_control.asp,
and my guess
is 'no', but I thought I'd
[Could probably be dismissed as Can't read the FAQ...]
How would I approach a 'network based installation'?
Scenario is as follows: I'd like to produce a 'slim' .msi
and several .cabs (or whatever, maybe one per feature)
somewhere on the net. Then a user downloads only
the .msi, selects some
Hi André
Hi Stefan.
the Type=Edit is probably what you want to use.
Indeed.
You should read the wix tutorial
http://www.tramontana.co.hu/wix
Believe it or not, I had looked at it yesterday evening but was probably too
focused
on the 'line' part...
The possible controls which are
I've just started to use Wix v3 (or any .msi based installer toolkit for
that matter)
so please bear with me.
First question: How would I add a line edit control to a dialog?
I have found examples for PushButtons, RadioButtons, static text etc but
nothing that looks like something that might
I have a third party product with an msi based installer that I need to
install
alongside my own stuff.
Simply launching msiexec from a custom action does not seem to work as
msiexec will complain that another installer (presumably my own) is already
running.
Decompiling the third party
56 matches
Mail list logo
