OK... So this, I don't get...
Given:
Property Id='IT_EXISTS'
DirectorySearch Id=YEY Path=C:\
FileSearch Name='xxxasfsdfxxx.txt'/
/DirectorySearch
/Property
Which *obviously* does not exist :-)
Why does:
Custom Action=DoSomething Before=SomthingElse
Thanks for the clarification. Does that mean that the binder information is
only updated by light? If so what happens to a wixlib with embedded files, does
light extra the files to get the version information?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL
Hi Bob
Thanks very much for the reply.
I've submitted the installer (zipped) along with a message to the Tracker at
SourceForge (http://sourceforge.net/projects/wix/ - Tracker category Dark
and version 3.0).
Will also take a look at Setupbld.exe.
Regards,
Tony
http://www.58bits.com
Thanks Phil, You were correct the Warning shows up in Application Event Log.
I can now see what the problem is. After install finialise I delete two of
the files that are in my installer from the local drive when I run a
CustomAction. This is whats causing the repair, the two files are missing
Tony,
Also look into PaquetBuilder ( http://www.gdgsoft.com/pb/ ), it has features
that setupbld.exe doesn't provide. Depending on your requirements for
setup.exe / bootstrapper.
For example, PB provides a language selection dialog. It does have drawbacks
for automation (even when using directive
Fantastic Bob, Thanks.
- Original Message -
From: Bob Arnson [EMAIL PROTECTED]
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Sunday, July 13, 2008 7:26 PM
Subject: Re: [WiX-users] Conditionally show dialog box
John Daintree wrote:
Alright, here's the latest installment of my saga. It seems that I can
build my extension just fine, both x86 and x64 flavors... When I use the
extension in a project, it works if I use the x86 version, but the x64 fails
to load.
Here's the error from MSBuild. (I used Votive to create the
A WiX extension DLL is loaded into the WiX compiler process (candle.exe). Since
candle.exe is x86-only for now, all extensions must be x86 (or neutral).
Why would you need to compile the extension DLL as x64?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Hello Bob,
I'd suggest creating a separate component for the backup
and give it a condition of NOT PATCH.
Thanks for the solution. I added a new component witn CopyFile and
made it transitive. Now everything works as expected.
But, this solution looks like a workaround. Most likely this is
Hello,
I am completely new to Wix and i would like to have some advices from
experimented users.
My scenario:
We have each object of the database stored as a separated scripts in a
tree structure like
Create Scripts\Module\Tables
Create Scripts\Module\Views
Create
James Minnis wrote:
1) The text of error messages are not being displayed in VS 2005. When the
build fails, I have to build from a command line to actually read the build
error. This is a known bug that I read about in other messages in the list
archive, but it is extremely frustrating for
andywhitt wrote:
I can now see what the problem is. After install finialise I delete two of
the files that are in my installer from the local drive when I run a
CustomAction. This is whats causing the repair, the two files are missing
(they are not needed anymore after the CustomAction has
Neil Sleightholm wrote:
Thanks for the clarification. Does that mean that the binder information is
only updated by light? If so what happens to a wixlib with embedded files,
does light extra the files to get the version information?
Yes. When files are bound into a .wixlib, they go
Ilya Slobodin wrote:
But, this solution looks like a workaround. Most likely this is not
WiX but Windows Installer issue. Is this planned behavior or not?
I don't know -- I'm not on the Windows Installer team.g
That is correct. And I expect that since MoveFile record references
the
Because my extension includes a Custom Action DLL, and that needs to be
32/64 bit. They perform registry operations on installation, and need to be
64-bit aware.
My other option would be to make my extension platform aware, so it can
include the proper .DLL Have any suggestions for how to
Yes, making the extension platform-aware so it includes the proper DLL is the
way to do it. If your custom schema elements are tied to a component then you
should check the platform of the component. Otherwise check the platform of the
MSI being built or the value of candle's -platform switch.
I have a CustomAction rollback in my Wix File that looks like this:
CustomAction Id=Rollback FileKey=MyEXE ExeCommand=rollback
Execute=rollback Return=check Impersonate=no HideTarget=yes/
InstallExecuteSequence
Custom Action=Rollback Before=MsiUnpublishAssemblies/
This never gets
James Minnis wrote:
1) The text of error messages are not being displayed in VS 2005. When
the
build fails, I have to build from a command line to actually read the
build
error. This is a known bug that I read about in other messages in the
list
archive, but it is extremely
James Minnis wrote:
1) The text of error messages are not being displayed in VS 2005. When
the
build fails, I have to build from a command line to actually read the
build
error. This is a known bug that I read about in other messages in the
list
archive, but it is extremely
Jason Ginchereau wrote:
Yes, making the extension platform-aware so it includes the proper DLL is the
way to do it. If your custom schema elements are tied to a component then you
should check the platform of the component. Otherwise check the platform of
the MSI being built or the value of
What does a verbose log say for the action state of that component?
Attached two grepped logs with different arguments, with and without
REINSTALL=ALL REINSTALLMODE=omus
1. msiexec /update Patch\Patch.msp /lv* Logs\PatchGood.log
File Sample.txt is patched
File SampleDb.txt is not touched (as
I added the CloseApplication Wix feature to my install, but it doesn't
seem to be working. In the MSI log it detects my EXE is running, but it
doesn't seem to send the WM_CLOSE message to shut it down. I used the
old Spy++ tool to watch the window messages and I never see that
message. It does
Thanks Rob, that makes sense, I guess :)
Not sure if I should file something, but it might be nice to add that to the
examples on the WixVSExtension documentation page.
For anyone else facing this issue here's how I resolved it...
!-- Create dummy directories to assign the VS2005 directory
I'm trying to add a dialog to the uninstall sequence. The dialog allows the
user to select additional items to remove when uninstalling. I'm having
trouble getting the checkbox values to trigger a custom action. Here is the
xml i have...
?xml version=1.0 encoding=UTF-8?
Wix
That got me set up right.
For public reference... In order to get my extension to build using all
the work put into the WixBuild.Common.targets file, I had to move a bunch of
stuff around.
IMHO, It looks like that file was originally used for the additional build
tasks and new task types
Hi,
I'd like to ask users to enter product keys into the license key dialog,
and then validate them using a custom action, which calls a DLL written in
VB6.
I want to implement a generic validation mechanism that can validate
multiple product keys just like the way each Microsoft product
Anyone? HELP?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Amir
Kolsky
Sent: Sunday, July 13, 2008 11:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Another newbie question: condition on custom
action
OK... So
I think that having examples in the documentation would help out immensely.
On Sat, Jul 12, 2008 at 9:12 AM, Rob Mensching [EMAIL PROTECTED]
wrote:
Uhh, yeah. You asked how to condition a custom action and that says
specifies the condition of the action. Am I missing something? Is there
I can't see anything obviously wrong here, but my suggestion is to create a
verbose log and see what the property values are:
msiexec /i setup.msi /l*vx Install.log
Also, if you aren't using it
Wilogutl.exehttp://msdn.microsoft.com/en-us/library/aa372811.aspxis
a nice tool to analyze the logs
29 matches
Mail list logo
