I'm a bit hesitant to post this, it seems so unlikely ...
I have a custom dialog that I've added to a WiX project, first 3.5 and now 3.7,
and it has a Next button. Sometimes, like 20% - 30% of the times I run this
install, the Next button doesn't respond to mouse clicks! I can click and click
This was not a problem in WiX 3.5, but apparently as part of 3.6 support was
added to the MSBuild targets for incremental builds by testing the
timestamps on all input files to the link task to see if they were newer
than the output files. I haven't been able to find any documentation - Bob
Arnson
Hi Rob, and thanks for your reply.
robmen wrote
Want to help us fix the root issue? If so, love to start a discussion on
wix-devs@.sourceforge
about the best way to fix the targets to correctly handle the situation.
First off, I tried answering via the [hidden email] link, but then I get
In my WiX 3.5 project I'm including a wxs file via a link. I.e., the wxs
file is not in the project folder, it is fairly far away in the folder
structure, and is included using Visual Studio's Add as a link
facility.
A specific example:
My project is here:
Hmmm, no answers ...
I'm wondering if someone could at least point me in the right direction
if I decide to take a look at the source code and see if I can fix this
myself.
Thanks.
-Original Message-
From: Rennie Petersen [mailto:r...@merlinia.com]
Sent: 16. marts 2011 15:35
To: wix
-Original Message-
From: Rennie Petersen [mailto:r...@merlinia.com]
Sent: Friday, March 18, 2011 7:21 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX creating obj file in strange place
Hmmm, no answers ...
I'm wondering if someone could at least
on one of the files to rename the
.wixobj
output) but that is where we are at right now. If someone wanted to do
the
MSBuild-magic to get the behavior I described above and contribute it,
that
would be quite fantastic.
On Wed, Mar 16, 2011 at 7:35 AM, Rennie Petersen r...@merlinia.com
wrote
I'm very new to WiX and Windows Installer, so maybe I'm doing something
dumb...
When the ALLUSERS property is not defined I get a per-user install.
But when I define ALLUSERS and give it a value of 0 then I get a
per-machine install.
I've checked the MSI with Orca, and the value of ALLUSERS is
.
Rennie
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 14. april 2007 20:58
To: Rennie Petersen
Cc: [EMAIL PROTECTED]
Subject: Re: [WiX-users] ALLUSERS=0 (or null) not working
Rennie Petersen
something I'd be very happy to hear about it.
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rennie
Petersen
Sent: 14. april 2007 21:19
To: [EMAIL PROTECTED]
Subject: Re: [WiX-users] ALLUSERS=0 (or null
Have you tried nesting Feature elements, instead of using
FeatureRef's?
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Julie Campbell
Sent: 15. april 2007 23:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature Ordering?
Are you sure you're using the Norwegian localization file during your final
link? (Are you saying some text is localized and some isn't?)
Rennie
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas
Bjørnsen
Sent: 18. april
I use SharpDevelop 2.1. Its dialog editor works fairly well with WiX
dialogs. Just be aware that all comments are deleted. :-(
There's also an open source program called WiXEdit. I tried it out but
ran into problems.
I've made a simple beginner's tutorial for using WiX (with
SharpDevelop). It's
Don't know if it's relevant for you, but I'm using an open source program
called dotNetInstaller to ensure .NET Framework is installed.
Rennie
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas
Bjørnsen
Sent: 19. april 2007
Stohlmann
Sent: 19. april 2007 17:34
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Dialog Editor
From playing around with it for 15min, SharpDevelop seems like a
pretty decent recommendation. Can you send a link to that tutorial?
On 4/19/07, Rennie Petersen [EMAIL
Yes, that is very easy, at least if you are working with the UI in
source form.
Just change the sequence of dialog boxes to omit the dialog box that
shows the license agreement.
But you do need to download the WiX source and work with the dialog
sequencer in source.
Rennie
-Original
You need to change some things in the WixUI_InstallDir.wxs file to
change the sequencing of dialog boxes.
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anthony Wieser
Sent: 20. april 2007 13:08
To: wix-users@lists.sourceforge.net
Julie,
Thanks for the Wiki.
To all interested:
I've published the first two pages (out of five) of my beginners
tutorial.
http://www.merlinia.com/mdt/WiXTutorial.msl
It's a lot more work than I expected. :-(
Corrections, suggestions, criticism, etc. very welcome.
Probably not of much
Are the files declared in the same Component?
They should not be. Files for different folders should be declared in
separate Components.
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jrcolons
Sent: 25. april 2007 20:59
To:
] Beginner's Tutorial, Books, Versions...
Just had a quick skim over it, and at the bottom of part 2
your link to part 3 actually points to part 2 again.
Following the link to part 3 gives a Requested page not found error.
Rob
Rennie Petersen wrote:
Julie,
Thanks for the Wiki
I too am using dotNetInstaller. Seems to work OK.
My understanding of the bootstrap program generated by VS is that it is
hard-wired to invoke the MSI after it has installed the prerequisites.
This is a disadvantage for me. My setup sequence is:
1. dotNetInstaller (renamed Setup.exe)
2. MSI
It doesn't evaluate correctly until after the CostFinalize action.
When does that happen?
My experience is that the Feature property is correct in the following
dialog boxes. I use that in my install sequence to skip a dialog box if
the corresponding feature is not selected, as demonstrated
I don't think Windows Installer can grant rights to users. That would be
a security violation.
Do you mean specifying which account an installed service is to run
under?
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL
Not sure I understand your question, but maybe try using dotNetInstaller
instead of the VS 2005 bootstrapper. With dotNetInstaller you can
specify any parameters you want when it starts the MSI.
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
one of the main issues is whats to stop the user just
starting the msi rather than the Exe you ask them to start
with an autorun..
Yes, it's difficult to make something fool-proof, because the fools are
so ingenious. :-)
You could try turning the bootstrapper and the MSI into a single
You can't launch one MSI from another one, and you can't bundle one MSI
inside another.
So I assume what Brett is saying is that you should make a Setup.exe
that first launches one MSI, and when that is complete, launches the
other.
I've actually written a program like that recently, an MSI
My beginner's tutorial shows how to do this, although for WiX 2.0.
(Don't know if the same techniques will work in WiX 3.0.)
http://www.merlinia.com/mdt/WiXTutorial.msl
See in particular the last section on this page:
http://www.merlinia.com/mdt/WiXTutorial3.msl
In part 5 (not on-line yet) I
Are you using WiX 2.0 or WiX 3.0?
Anyway, one MSI can only contain one language. To support 3 languages you need
to create 3 MSIs. You can then convert 2 of them to MSTs to reduce the final
size of your deployment package. (Or maybe 1 MSI and 3 MSTs - I'm not even sure
of that.) You then use
your bootstrap program to launch MSI with appropriate transform.
Best,
Igor
Rennie Petersen wrote:
Thanks for your feedback.
I'm afraid I still don't understand...
I've provided localization for ALL of the texts in ALL of the WiX
dialog boxes.
The error
I first tried using WiXEdit, but could never get it to work. (Maybe I
gave up too quickly.)
If you look at my tutorial you can see how to do it with SharpDevelop,
and using the WiX sample UI as starting point, but then modifying the UI
to be what you want. With everything localized.
Rennie
in your tutorial how
you specify which loc.wxs file to use either.
From: Rennie Petersen [EMAIL PROTECTED]
To: Pseudonymic Wannabe
[EMAIL PROTECTED],wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] WixLocalization, not quite getting it.
Date: Thu, 3 May 2007 11:29:48 +0200
I
I'm writing a little MSI Editor program.
The idea is to provide our customers with something a bit more intuitive
than Orca for modifying our MSIs before doing a group policies roll-out.
My program has a customizable GUI that can resemble the user interface
one sees if one does a non-silent
I need the Control in the WIX UI with Accepts the IP address,
What do you mean? What IP address?
If you just want to provide a field where the user can enter some IP
address, then use an Edit control. See the fourth dialog box in this
example:
There are programs available that can analyze DLL dependencies, for
example this one: http://www.dependencywalker.com/
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cathryn
Chamley
Sent: 7. maj 2007 00:24
To:
On this page you can see how to test for which features have been
selected, although here I use it for another purpose.
Hope this helps...
http://www.merlinia.com/mdt/WiXTutorial4.msl
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
See this page: http://www.merlinia.com/mdt/WiXTutorial4.msl
In particular, see the comments about
EmptyComponent_WindowsInstallerBugWorkaround
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Palmer
Sent: 10. maj
I believe that if you set the Level of the feature to zero
that it is not shown in the feature tree and is not installed.
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lewis
Henderson
You probably need a bootstrap program to run before your MSI gets
started.
Visual Studio's Setup projects can provide a bootstrapper.
I like one called dotNetInstaller.
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lewis
Sorry if I'm asking a silly question, but I assume you have specified
different disk numbers and included multiple media elements?
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Magus
Sent: 11. maj 2007 01:42
To:
I recommend using sharpDevelop. I've written a beginners tutorial that
includes information about this.
http://www.merlinia.com/mdt/WiXTutorial.msl
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Aaron Feng
Sent: 12. maj
I believe this is THE definitive list of built-in properties:
http://msdn2.microsoft.com/en-us/library/aa370905.aspx
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Burton
Sent: 15. maj 2007 17:26
To:
I've written a bit about using the Registry element here:
http://www.merlinia.com/mdt/WiXTutorial1.msl (near bottom of page).
Are you looking in the right place? (HKLM vs. HKCU?)
The Registry element has to be inside a Component element. The
registry entry should automatically be removed when
I know nothing about WiX 3, but here's how I do it with WiX 2, which may
help: http://www.merlinia.com/mdt/WiXTutorial3.msl
If the Common Public License text is being shown it sounds like you have
not actually replaced the file in the input to the WiX project...
Rennie
I believe that you will need a custom action.
WiX creates MSIs. It does not replace or enhance Windows Installer, and
it is Windows Installer that drives the UI during the installation.
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
I bought a digital certificate from GlobalSign a couple of months ago.
It cost approx. 1/3 what Verisign wanted, if I remember right.
http://www.globalsign.net/
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Pseudonymic Wannabe
Sent:
If you're totally new to WiX you might be interested in my (incomplete)
Beginners Tutorial for WiX 2.0 with sharpDevelop.
http://www.merlinia.com/mdt/WiXTutorial.msl
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Dale Quigg
Sent: 30.
Do you need to do it via an MSI? If so, I have no ideas.
If you just want to do it any old way, you use the web server's
management console. Can't remember the details off hand, but if you
confirm that that is what you want, I'll dig up the information.
Rennie
I do something similar, based (partly) on the UserLanguageID property.
I have a registry value, Name=Language, that should contain the code
en for English or da for Danish.
See here:
http://www.merlinia.com/mdt/WiXTutorial3.msl
In my MSI, the UserLanguageID property is only made use of if
@lists.sourceforge.net
Cc: Rennie Petersen
Subject: Re: [WiX-users] Conditionally installing components
based on user'slocale
Thanks, but I need to know the country and I don't really care
about the language. I will have many systems where the language may
Does this have to be done in the MSI?
It sounds like it would be more suitable to do it in a bootstrapper, and
then run your MSI.
Or else add the functionality to the application itself, on first
execution.
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
I'm doing a reinstall, but I don't want the existing registry entries to
be modified.
So instead of specifying REINSTALLMODE=vomus I specify
REINSTALLMODE=vos.
But the registry entries still get reset to the values in my MSI.
Is it possible to avoid this?
Thanks.
Rennie
Without including my own complete source for this dialog...
It's not such a big deal. I've written a step-by-step beginners guide to
how to do it, which you might find useful.
http://www.merlinia.com/mdt/WiXTutorial.msl
The problem is that the Browse button on CustomizeDlg is disabled but
Is this WiX 2 or 3?
With WiX 2 I would assume you should write
CustomAction Id=ValidInstall Error=$(loc.SomeErrorMessagLabel) /
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Cristian Baiu
Sent: 7. juni 2007 09:57
To:
modified anyway.
Any idea of how I can prevent this?
Thanks.
Rennie
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rennie
Petersen
Sent: 6. juni 2007 19:18
To: wix-users@lists.sourceforge.net
Subject: [WiX
?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rennie
Petersen
Sent: Friday, June 08, 2007 3:37 AM
To: Rennie Petersen; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Avoiding registry entries being
this source code be submitted to someone, and if so to whom?
If not, we're willing to host the source code on our own web site.
Med venlig hilsen / Best regards
Rennie Petersen
Manager
Direct: +45 46 92 94 71 - Mobile: +45 40 55 35 64
mailto:[EMAIL PROTECTED]
___
Merlinia
I believe that this sort of thing is best done with a bootstrap program,
before starting the Windows Install process, not with a Custom Action
during the install.
There are many bootstrap possibilities, including one included with
Visual Studio. I like the .dotNetInstaller program, which is open
Try giving the property name all capitals, i.e., MYPROPERTY.
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Craig Ward
Sent: 17. juli 2007 13:32
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] updating properties
I'm trying
58 matches
Mail list logo
