On 2 Dec 2010, at 17:35, Wilson, Phil wrote:
Reference counting works on components, it really does work. I think you're
saying that there's a custom action that runs when one product is
uninstalled, even though others are using the pool. Is there a condition
somewhere on the CA that
On 29 Nov 2010, at 18:52, Wilson, Phil wrote:
This may be an issue with the SxS and policies depending on your OS. Some
people install the redist with the vcredist exe which also installs publisher
policy that redirects everyone up to the newly installed libraries. Some
people install
Hi,
We are currently using WIX 2 to build our MSI files. We are merging in the vc80
merge modules, apparently successfully. (Stuff runs :-)
While trying to upgrade to WIX 3, I noticed that the MSI files it produces are
a few megs bigger than the ones produced by WIX 2. But more critically, the
On 29 Nov 2010, at 15:54, Pally Sandher wrote:
v8.0.50727.762 of the VC++ 8.0 libraries is ancient (VS2005 SP1). Are
your binaries definitely built against that version of the VC++
libraries as the ATL security fix (which is in essence a stealth SP2 for
VS2005) released in July last year
On 14 Jul 2009, at 05:29, Igor Lemsky wrote:
I have x64 Windows XP. I tried to make 64 bit package by setting
attribute:
Package Id=* Platform=x64 /
and during compilation got an error:
light.exe : error LGHT0310 : Failed to open package for validation.
The
most common cause of
I started revising our package generating scripts from using Wix 2 to
Wix 3 yesterday.
It went well until I got to the custom UI :-)
We have some custom UI which is based on WixUI_Mondo, and in Wix 2 we
did this by using DialogRefs to all the Mondo screens we wanted to
keep, adding some
On 14 May 2009, at 01:04, Rob Mensching wrote:
Yes. Features are a tree but Components can be duplicated throughout
as leaves as you want. In the end, a Component is installed as long as
one of its Features is installed.
Thanks, that seems to work.
It does feel a little confusing to now
Is there any good way of checking exactly what features and components
of a package actually got installed by a user?
I was expecting to find some evidence of their GUIDs in the registry
somewhere, but none of them seem to be present despite things
seemingly being installed.
Cheers,
Chris
On 14 May 2009, at 16:53, Alex Shevchuk wrote:
I don't have ready to use solution, but
http://blogs.technet.com/alexshev/archive/2008/06/30/from-msi-to-wix-part-17
-windows-installer-automation-interface-part-2.aspx may give you a
good
starting point, if that's what you want.
Thanks Alex
Hi,
I've been working on properly supporting feature selection (Custom
installs) in our packages. So far so good, except I've got a slight
conceptual problem.
I install into 2 different directories, both of which are user-
configurable. So my WXS looks kind of like:
Directory INSTALLDIR
On 10 May 2009, at 19:37, Chuck wrote:
Chris Ridd wrote:
Yes, the higher compression levels make building the msi much slower.
If you've got the concept of a debug vs release build, I'd
suggest
using no compression when debugging, and high when doing a release.
In the interest
On 10 May 2009, at 13:38, Riyaz Mogharabin wrote:
Dear All,
You know we have 5 compression levels:
None, High, Low, MSZIP and medium.
Is it possible to use a third party compression code, such as 7-up
or rar?
And if it is possible, does it help to have faster and better
On 23 Feb 2009, at 11:03, Naga Ram .C wrote:
Hi,
I have some images (about 100+ files) that needs installed on target
machine
under a tree with user specified location something like
userloc/assets/images this user specified location need not have
to be the
program files location
On 23 Feb 2009, at 15:37, Naga Ram .C wrote:
Thanks Yen, I have read the manual, the only thing I am striving at
is that
to know how to add multiple files
The following script I can add a file
Component attrs=...
File id= mpapp.exe, source=C:\MyApp/MyApp.exe
/Component
I have more
On 13 Feb 2009, at 08:45, sandun css wrote:
Hi,
I need to create several folders, which don't contain any files at the
installation. Is this possible in wix? If so, how to do it?
Yes, just use CreateFolder/
See http://www.tramontana.co.hu/wix/lesson5.php#5.6 for an example.
Cheers,
Chris
On 8 Feb 2009, at 01:33, Rob Mensching wrote:
Not sure. Have you tried following the Property value changes in
the verbose log file to make sure it ends up what you want?
I'm seeing lines like:
AppSearch: Property: JDK15HOME, Signature: S_JDKHOME15
MSI (c) (74:D4) [13:19:54:468]: Note: 1:
On 8 Feb 2009, at 18:22, Bob Arnson wrote:
Chris Ridd wrote:
Is the ?component notation in control conditions supported by all
versions of Windows Installer?
Yes, but it might not work when you cross from the UI to the execute
and
back to the UI. There's no doc to say either way. I'd
On 5 Feb 2009, at 18:36, Rob Mensching wrote:
You need the *v to get it all. I never bother with logs any other
way. Nothing else (except the MSI itself to cross reference) is
usually necessary.
OK, I now have verbose logs of an install with Java and without Java.
I'm eliding all the
I've been bashing my head against this all day today :-(
We optionally install some shortcuts to things written in Java, and I
want to warn in the ExitDialog if those shortcuts were wanted but
could not be installed because Java's not there. To add complexity, we
allow the user to use
On 5 Feb 2009, at 17:54, Rob Mensching wrote:
Verbose log file should show you the states of everything.
I didn't see anything in the logs earlier, but then I didn't use /l*v.
Will try again tomorrow!
Do the component installation states get recorded automatically, or do
I need to arrange
In a mistaken piece of design, one of our MSI packages ends up
installing a file that we expect the user to then edit.
Unfortunately doing a package upgrade (or even just a repair of the
current package, I guess) loses those edits by replacing the file.
Are there any attributes that can be
On 28 Feb 2008, at 17:40, Alexander Shevchuk wrote:
Sorry, I misunderstood your original email. If you want to
uninstall previous component and install new one during upgrade
install you might want to use transitive components
On 27 Feb 2008, at 20:12, Alexander Shevchuk wrote:
Sorry, I don't have neither enough time to come up with the sample
nor ready sample.
One of the possible solutions for your problem is Qualified
components (http://msdn2.microsoft.com/en-us/library/aa370947.aspx)
and PublishComponent
On 27 Sep 2007, at 20:03, Kelly Leahy wrote:
Sorry for resurrecting an *old* old thread...
I think you want something like:
CustomAction Id=setJVMpath1 Property=JVMPATH
Value=[JDKHOME15] Execute=firstSequenceJDKHOME15 AND NOT
JVMPATH/CustomAction
CustomAction Id=setJVMpath2
On 13 Oct 2007, at 13:56, Mike Dimmick wrote:
The DigitalCertificate element is for:
a) validating signatures on external cabinets (presumably built
separately
with makecab);
b) (MSI 3.0 and later) indicating the set of certificates which are
allowed
to sign patches that can be
On 10 Oct 2007, at 11:55, Anton Filippov wrote:
Hi.
msiexec /i ...msi /quiet TARGETDIR=C:#Temp
?
Is that # meant to be a backslash?
Cheers,
Chris
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping
On 9 Oct 2007, at 15:49, John Vottero wrote:
The wix schema seems to have support for digitally signing packages -
the DigitalCertificate element, the DigitalCertificateRef element -
but I can't see how they're meant to be used.
Presumably light has to have access to the certificate's
On 4 Oct 2007, at 02:42, Kelly Leahy wrote:
Oh... If you're looking for OS = x64 or x86, rather than processor
x64 vs. x86, you'll probably want to look at VersionNT64 (also
requires version 4.0 of MSI).
Is there a list of known values for VersionNT64 anywhere? I couldn't
see
On 2 Oct 2007, at 18:54, Wilson, Phil wrote:
The only time I've ever seen this error message is when the shell
folders registry entries are incorrect. MSI checks every entry in
the Directory table for validity, so make sure you don't have a
directory/property name that is resolving to
On 30 Sep 2007, at 21:36, Bob Arnson wrote:
Chris Ridd wrote:
I'm probably the last one to spot this, but just in case - the
page describing Shortcuts in the website's Schema documentation
is completely devoid of information. Not even links to MSDN :-(
http://wix.sourceforge.net
On Friday, September 28, 2007, at 01:59PM, Srinivas Tirupati [EMAIL
PROTECTED] wrote:
How can we display a Text which has quotes in a wix dialog
Like -- Check for the section Trouble S hooting in Installation Guide
Tried using \ but no use:(
Thanks and Regards
Srinivas T
The WXS file is
On 28 Sep 2007, at 16:09, Kaveh Goudarzi wrote:
Hi Chris,
Thats interesting. Wow it's been a while since I thought of tcl/
tk (which I loved actually :-) ) ... While on the autogeneration
subject how do you deal with shortcut creation? do you exclude
files to which you
On Thursday, September 27, 2007, at 11:00AM, Kaveh Goudarzi [EMAIL
PROTECTED] wrote:
Hi All,
I want see if it's ok to use the md5 of a dir name relative to
INSTALL dir as its ID? I have written a tallow equivalent ant task
which automatically creates my fragment for me as part of my
Hi,
I'm generating a number of shortcuts to programs/scripts/etc that take
arguments. One tester has noticed that a shortcut set up like:
Shortcut Id=SHORTCUT_logconf Directory=ProgramMenuDir
Name=logconf LongName=Log Configuration Tool
Target=[INSTALLDIR]bin\wish.exe
On Thursday, September 27, 2007, at 12:35PM, Kaveh Goudarzi [EMAIL
PROTECTED] wrote:
Hi Chris,
Thanks for the advice :-) ... when you say with AUTO_ as documented
... where do you mean? I'm wondering if I missed some guidance doc
which I need to look at before I make this change.
It
On Thursday, September 27, 2007, at 01:00PM, John Vottero [EMAIL PROTECTED]
wrote:
Should something be properly escaping/quoting the argument? I can slip
a couple of quot;s into my arguments string, but that feels like a
layering hack.
WiX and MSI have no way of knowing that your argument
On Thursday, September 27, 2007, at 01:59PM, John Vottero [EMAIL PROTECTED]
wrote:
On Thursday, September 27, 2007, at 01:00PM, John Vottero
[EMAIL PROTECTED] wrote:
Should something be properly escaping/quoting the argument? I can
slip
a couple of quot;s into my arguments string, but
Hi again,
Some of my shortcuts call Java, and I need them to find the right one when
multiple versions are installed. So I set up 4 Property elements which set
JDKHOME15, JREHOME15, JDKHOME16, and JREHOME15 using RegistrySearch.
It looks like these properties are being set correctly when I
On 27 Sep 2007, at 17:59, Kelly Leahy wrote:
Oops. Sorry Chris for the duplicate - I forgot to reply to all on
the first one.
Not a problem - I'll put my reply to you below for everyone's benefit.
Here's what I sent to Chris - others, tell me if this won't work,
because I may need
On Wednesday, September 26, 2007, at 09:22AM, János Brezniczky [EMAIL
PROTECTED] wrote:
2007/9/26, Chris Ridd [EMAIL PROTECTED]:
On 25 Sep 2007, at 23:39, János Brezniczky wrote:
I would just add that it's easier to set Compressed=yes on the
Package instead of setting it on each
We're creating separate 64-bit and 32-bit packages, and so far my 64-bit
packages are refusing to install in 2003 Server. The most interesting of the
errors reported by Orca is:
ICE80ERRORThis package is marked with x64 but it has a schema less than
200.
How do I do that using wix2?
On Wednesday, September 26, 2007, at 02:45PM, John Vottero [EMAIL
PROTECTED] wrote:
We're creating separate 64-bit and 32-bit packages, and so far my 64-
bit packages are refusing to install in 2003 Server. The most
interesting of the errors reported by Orca is:
ICE80ERRORThis
I'm probably the last one to spot this, but just in case - the page
describing Shortcuts in the website's Schema documentation is
completely devoid of information. Not even links to MSDN :-(
http://wix.sourceforge.net/manual-wix2/wix_xsd_shortcut.htm
There's some material in the xsd file in
On 25 Sep 2007, at 23:39, János Brezniczky wrote:
I would just add that it's easier to set Compressed=yes on the
Package instead of setting it on each individual File element. (I
use WiX 2)
But does it also apply to merged in modules? We're merging in one of
the runtime modules for
Hi,
I'm in the process of altering our Windows package building scripts from
using Installshield to using WIX. So far (cross fingers) so good.
I'm having some conceptual problems with WIX's Components though, in
particular their GUID attributes. Curiously (for us) Installshield makes
*way* less
45 matches
Mail list logo
