http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx
Based on the feedback left by those of you here and elsewhere, I've posted some
proposed adjustments to our current roadmap. I am curious what people think
about trimming the next releases
Hello all.
I've written a standalone GUI to spawn the install of 3 separate MSIs. The
gui is called setup.exe. Whenever I run setup.exe on a Vista machine I get
the UAC elevation prompt. If I rename the gui to jd.exe I do NOT get the UAC
elevation prompt.
If I rename the file install.exe I
Yes, this is expected. If the file looks like its an installer, then Vista
will elevate it unless
the manifest says otherwise. This was to try and aid migration to Vista.
Rob
John Daintree wrote:
Hello all.
I've written a standalone GUI to spawn the install of 3 separate MSIs. The
gui
Bootstrappers - how to and why. Seems a very common question.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: 05 June 2008 22:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] What kind of How To docs would you like to see?
OK Rob, thought so. Thanks.
- Original Message -
From: Rob Hamflett [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Friday, June 06, 2008 10:02 AM
Subject: Re: [WiX-users] Setup.exe UAC elevation on Vista
Yes, this is expected. If the file looks like its an installer,
Hi folks,
I'm using WiX 2.0.5805.0 on Windows XP and facing a crash of light.exe
when using Merge Modules and Shortcuts together. If I omit the Shortcut
definition everything runs fine.
The error message from light.exe is:
light.exe : error LGHT0001 : Beim Aufruf einer COM-Komponente wurde ein
Can you try grabbing the mergemod.dll out of the latest drop of the WiX v3
toolset (http://wix.sourceforge.net/releases)? There was a bug recently found
in mergemod.dll that the VC runtime merge modules seem to have uncovered.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Now I have tried the Property LogonUser and that works great. This
property was exactly what I have been looking for. Thank you so much.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Rob
Mensching
Gesendet: Donnerstag, 5. Juni 2008 19:13
An:
Thank you for your help. I will try this proposal immediately. But, where do
I find the documentation of all build in properties? The manual of wix at
sourceforge seems to be offline for some days.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
Do you think it would be better to add this information to the Wiki
(http://www.wixwiki.com)?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
From: [EMAIL PROTECTED] on behalf of Neil Enns
Sent: Thu 05/06/2008 22:04
To:
That did the trick. It also fixed my problems with Shortcuts installing
from merge modules. I would not have thought it to be that easy.
Thank you for your immediate response and your wonderful WiX toolkit! I
enjoy working with it.
Keep up the good work,
Cheers Volker
Rob Mensching schrieb:
* Xenia Holtmann [EMAIL PROTECTED] [06.06.2008]:
Thank you for your help. I will try this proposal immediately. But, where do
I find the documentation of all build in properties? The manual of wix at
sourceforge seems to be offline for some days.
on the msdn, see
Thank you. I have saved the link to my bookmarks.
Mit freundlichen Grüßen,
Xenia Holtmann
Projekt-Managerin
BRAVIS GmbH
--
BRAVIS GmbH, Gerhart-Hauptmann-Str. 15/Süd 9, D-03044 Cottbus
Tel. : +49 (0) 355 / 28 91 82 - 20, Fax: - 29
WWW : http://www.bravis.eu
E-Mail: [EMAIL PROTECTED]
BRAVIS:
I think so... would be nice to have it all up-to-date, in one place.
2008/6/6 Neil Sleightholm [EMAIL PROTECTED]:
Do you think it would be better to add this information to the Wiki (
http://www.wixwiki.com)?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL
I've just began to work on on installer with WIX 2.0.5805.0 version. And
I've got some questions related:
1. Localize the UI. I've added the . I've already find on this forum
that this could be solved by adding to the command line the .wxl file
needed (-loc %WIX%\WixUI_en-us.wxl). But my
I wouldn't mind seeing some kind of small tutorial that shows how to create
upgrades...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: 05 June 2008 23:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] What kind of How To docs
When I do it that way, I get a compile-time Error 1 When nested
under
a component, the sql:SqlDatabase element must have one of the
following attributes specified: CreateOnInstall, CreateOnUninstall,
DropOnInstall or DropOnUninstall.
Is the v3 WixSqlExtension ready, or should I be
I would like to see all custom actions and wcautil functions documented
*with an example*.
One can argue that they are just the wrappers around MSI functions and
thus : read the documentation!
However, initially one approaches these functions in the hope of making
sense out of SDK documentation
I have recently converted a custom action in my install to use DTF and
C#. This specific custom action is launched from a dialog and confirms
various things about SQL Server credentials, permissions, version etc.
that were entered by the user on that dialog.
When I execute this install on a
Hi,
I have a package in which the MFC and MSVCRT runtime libraries are
needed. So I decided to use Microsoft's merge modules... so far so good...
The problem is that I have a custom action that calls an executable
which needs these MFC and Runtime libraries to be installed.
I'm calling the
I have:
Feature tree and custom action list. Minimal example:
Feature Id='Complete'...
Feature Id=CoreFeature...
...
/Feature
Feature Id=OptionalFeature ...
...
/Feature
/Feature
CustomAction Id=InstallOptionalFeature BinaryKey=.../
CustomAction
What is the value of MYPROPERTY ( msi log ) at the moment that you attempt to
get it?nbsp; I'd like to see if I can mock this up and debug it.nbsp; Perhaps
there is some kind of escaping problem.
nbsp;
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or
I fixed a bug this week in the managed CA remote-invocation channel that is
probably the cause of the exception you're seeing. Can you check if you can
still reproduce the problem on today's build 3.0.4206? (It's not published yet,
but should be there soon...)
-Original Message-
From:
Riyaz Mogharabin wrote:
//
//
Condition WIXUI_INSTALLDIR something - will not gerenrate
error, but the conditon is not working. (it is always true)
Then you might not be able to check that property; there's no
documentation how to do an indirect property lookup. Try directly
Volker Enderlein wrote:
i came across the idea of making the ProgramMenuDir configurable as
InstallShield and other installers do. You can give a different name to
the program group. Is that possible in WiX and if yes how?
Create a subdirectory of ProgramMenuFolder and you can give it
Evans, Jim wrote:
This is sorely disappointing to me personally. Quite frankly, I need the
bootstrapper. I hate that I'll be waiting for WiX v4 to get it.
It's unlikely to change the date when the bootstrapper becomes
available. Working on it in the v4 branch gives us the flexibility to
ship
Laplante, Patrick wrote:
- find all 3 application and locate their plug-in folder (probably
reading the registry).
- display the 3 application in a listbox where the user can
select/deselect into which application it must install
- and install the plugin in the user's selected
Mole, Chris wrote:
In the util:FileSharePermission element, there's no Domain attribute. Is
there some other way to grant fileshare permissions to a domain account?
Use DOMAIN\username for the User value.
--
sig://boB
http://joyofsetup.com/
Ryan O'Neill wrote:
Ah, I was using
?define Version=!(bind.FileVersion.MyFile) ?
When it should have been
?define Version=!(bind.FileVersion.MyFile) ?
Hmmm, I'd say either should work. Can you open a bug that includes the
error message you got?
--
sig://boB
http://joyofsetup.com/
Christopher Painter wrote:
You know Bob, I've read that before but didn't think about how that could
solve another pain point. getting around the fact that the ShortCut
table doesn't format the shortcut name when dealing with multiple instance
installations.
WiX already supports
Natxo Mateos wrote:
2. Which would be the best planning to define a multilanguage installer?
Define a dialog with all the possible languages and depending on the
selection, execute one or another executable file (that would imply
having as many .msi files as languages). Or it would be
Frédéric Viollet wrote:
Are the merge modules installed after 'StartServices'?
No. It's a limitation of how the CRT installs the DLLs into the WinSxS
store. See the MsiAssembly Table doc in the MSI SDK:
The assemblies are not committed until successful execution of the
InstallFinalize
Wow very cool :) Well as I noted down, the URL has a good start on UI
modification.
Also, a big one for many is Localizations. Localizing properties (for UI)
and how to compile/link them in the project can be hard to figure out.
This is a great amount of effort and you would help out a lot of
Good to know, only I wasn't using WiX at the time. :-)nbsp;nbsp;nbsp;
Any idea on why the column was formattable in the first place?nbsp;nbsp; Was
it just a `we didn't think you'd want to do that` thing or is it limited by
some advertisement problem?
nbsp;
Christopher Painter, Author of
Christopher,
The code that throws the exception is
string serverToTest = session[SERVERTOTEST];
session[LASTSERVERTESTED] = serverToTest;
From my install log...
Property(C): SERVERTOTEST = sqlserver
Property(C): LASTSERVERTESTED = tion
Jason,
I'll be on it the moment it's available, and I will let you know.
Amy
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
Justin Chase wrote:
I am getting one last error about an ErrorDialog property not being set and
I can't for the life of me figure it out. I have created a Dialog with
ErrorDialog=yes and I have added a DialogRef pointing to it in my main
UI... what am I missing?
You need to set the
If you place the SqlDatabase element under a Component element that will
attempt to create the database. My SqlDatabase element is a direct child of
one of my Fragment elements. It is a little confusing but that causes the
SqlDatabase element to search for an existing database. Unfortunate
Thanks for the confirmation. We're going to be releasing a very tiny update to
WiX v2 with the fixed mergemod.dll very soon.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Volker Enderlein
Sent: Friday, June 06, 2008 04:42
To: General discussion for
Hi,
I'm getting this error..
error LGHT0094 : Unresolved reference to symbol 'User:test' in section
'Product:{A50A3A25-28AA-40D0-97B7-63091A3723D9}'
code as follows..
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id=apps_d Name=.
Component Id='apps_d'
You are hitting one of the less consistent parts of the WiX toolset. The
FileSharePermission/@User element creates a reference to a standalone User
element. The PermissionEx element has the @Domain and @User elements to define
the user inline. Unfortunate merger of design by different people
To provide a bit more detail on what Bob said, the biggest difference between
the planned WiX bootstrapper and the other bootstrappers discussed here is to
create something with built in layers so that you can use only the
functionality that you want. Additionally, the hope is to make the
Personally, I'd hope to see this in the WiX.chm so that it can then get
published up on the http://wix.sourceforge.net site. Is there an advantage of
spreading the documentation all around?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil
Actually, now that I am looking at it, it succeeds through both of these
lines and then fails on the next attempt to access a property.
string sqlServer = session[SQLSERVER];
from the log...
Property(C): SQLSERVER = PETER
It's at this point an exception is thrown and I end up in my catch.
Amy
Bob Arnson wrote:
It's unlikely to change the date when the bootstrapper becomes
available. Working on it in the v4 branch gives us the flexibility to
ship it in stages and not be forced to do a more limited release
just
to ship v3. Also note that there's nothing that ties the bootstrapper
There is a feature planned to provide progress to parent processes of the
bootstrapper. The .NET Framework does this already, we'll probably do the
identical thing (presuming it is rich enough). I don't know if SQL Express
does the same... if not, then the progress for that component will be
RE: SQL Express installer progress:
I only recently learned of the .NET Framework's installation progress
solution, and am planning on using it. As near as I can tell, SQL
Express does not provide a similar solution, so I guess we should start
working on that letter. grin/
-Original
If you write it, I'll add my name. I'd even be happy to try to find the right
people to send it to. smile/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:16
To: General discussion for Windows Installer XML
Bob Arnson schrieb:
Volker Enderlein wrote:
i came across the idea of making the ProgramMenuDir configurable as
InstallShield and other installers do. You can give a different name to
the program group. Is that possible in WiX and if yes how?
Create a subdirectory of ProgramMenuFolder
Volker Enderlein schrieb:
Bob Arnson schrieb:
Volker Enderlein wrote:
i came across the idea of making the ProgramMenuDir configurable as
InstallShield and other installers do. You can give a different name to
the program group. Is that possible in WiX and if yes how?
Create a
There's some documentation here, scroll down to Installer Detection Technology.
http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70e-b18ff918c2811033.mspx?mfr=true
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
1) The code will be different for immediate and deferred custom actions.
Immediate CAs can get properties directly, deferred ones need to use
CustomActionData. This may be something to do with what you're seeing.
2) RemoveExistingProducts will work fine after InstallInitialize, but note the
I just installed the new Wix3_x64.msi (v3.0.4206.0) today, and now I get
this:
Error1The specified task executable could not be run. Could not load
file or assembly 'wconsole, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The system
cannot
Oh yeah. I'm running this under VS2005.
On Fri, Jun 6, 2008 at 3:48 PM, Christopher Karper
[EMAIL PROTECTED] wrote:
I just installed the new Wix3_x64.msi (v3.0.4206.0) today, and now I get
this:
Error1The specified task executable could not be run. Could not
load file or assembly
Ah, if you look at the last three characters in the public key you can see
why.
PublicKeyToken=ce35f76fcda82bad'
Sorry, that just tickled me!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: 06 June 2008 20:48
To: General
Jason,
I just installed and tested this again with the new build of wix
v3.0.4206.0. On Windows Server 2003 SP1 I do not see the exception, and
all the code I wrote executes correctly and detects the various things I
have written it to detect (can it connect to the database server, does
the
That's the SN token that gets consumed if you build yourself.nbsp;nbsp;
Official MS builds use a different ( not distributed ) key.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On
That would suggest that there has once again been a ship errata.
nbsp;
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Fri, 6/6/08, Christopher Karper lt;[EMAIL PROTECTED]gt; wrote:
Volker Enderlein wrote:
I knew I was missing some fundamentals of WiX. I found the answer
reading the wix tutorial a second time more carefully.
Right. Windows Installer requires you to name files and directories
explicitly; a custom action is needed to use embedded properties.
--
Christopher Karper wrote:
Error1The specified task executable could not be run. Could not load
file or assembly 'wconsole, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The system
cannot find the file specified.C:\Program Files
Christopher Painter wrote:
Any idea on why the column was formattable in the first place?nbsp;nbsp;
Was it just a `we didn't think you'd want to do that` thing or is it limited
by some advertisement problem?
Shortcuts are files; MSI requires static names for files.
--
sig://boB
That all sounds fine to me personally, as long as I can start investing
my time in refactoring all of our installers with WiX v4 (and its
bootstrapper!) sometime around the time you would said it would be
available.
Joel
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
I like the new plan, let's get it done! :D
On Fri, Jun 6, 2008 at 3:34 AM, Rob Mensching
[EMAIL PROTECTED] wrote:
http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx
Based on the feedback left by those of you here and elsewhere, I've posted
Where is this ErrorDialog property? There was one on the dialog itself but
that was just a yes/no value. What object has the ErrorDialog property that
wants the ID?
On Fri, Jun 6, 2008 at 11:12 AM, Bob Arnson [EMAIL PROTECTED] wrote:
Justin Chase wrote:
I am getting one last error about an
Ok actually I think I figured it out by adding the following line above my
InstallUISequence node:
Property Id=ErrorDialogFatalError/Property
Where fatal error was the name of my dialog. But now I get the following
error:
Error 8 ICE20: Specified ErrorDialog: 'FatalError' not found in Dialog
Hi I am creating a wix installer using the code below. Although I am using the
UpgradeCode , the msi does not replace the already installed web service code
with the new one. Is there something that I am missing? Please help.
?xml version=1.0?
Wix
Hi I am creating a wix installer using the code below. Although I am using the
UpgradeCode , the msi does not replace the already installed web service code
with the new one. Is there something that I am missing? Please help.
?xml version=1.0?
Wix
So here is a question. I've seen the default projects that come from Visual
Studio and seen the site selection for Vdirs appear. How would one go about
that through WiX? Any pointers?
Thanks
Pierson
-
Check out the new
68 matches
Mail list logo