I solved it by scheduling the RemoveExistingProducts standard action after
InstallFinalize and I used RemoveRegistryKey element to remove registry keys
that contain version information.
Thanks
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 9. december 2009 07:56
To:
Hi,
I'm using WIX3 and try to make an installer package for our software.
The software contains lots of files and folders, and some of them have to
be treated specially (one for installing a Windows Service, several config
files which should be preserved).
Now I'm using heat to generate the
I'm getting some behaviour which surprised me... if I have the following
in a merge module
Directory Id=CommonFilesFolder
Directory Id=CommonFilesFolder_A Name=A
Directory Id=CommonFilesFolder_B Name=B
Component Id=test.txt Guid=*
File Id=test.txt
Fyi, there's an immediate CA that extracts a binary stream into a file in
http://msiext.codeplex.com/.
CA_API UINT __stdcall BinaryWrite ( MSIHANDLE hInstall )
Saves a binary stream into a file.
Parameters:
BINARYWRITE_PROPERTYNAME The name of the Binary property that contains the
Hello All
After playing two more days I made no progress.
I tried all the advises I got, including rewriting the wxs file
following the example in Neil Sleightholm's blog.
I got the same two results:
Major upgrade: (Using '*') every thing works but I got two entries in
the Add Remove Programs.
Hello,
My first version of my installer has created a duplicated 'Default Web Site'
on client server. I made changes to use Web Site locator, but now throw
error (Failed while processing WebDirs). After some attempts I found that
the error occurred because the IP Address was not set to 'All
Hi,
I've used the information contained in the following posts:
http://n2.nabble.com/Multiple-Instance-Transforms-Walkthrough-Proposed-Simple-Addition-to-WiX-to-Make-Them-Easier-td708828.html
The functionality that I'm after is as follows:
-user installs instances by choosing from a list of
All the CommonFilesFolder values in merge modules are by convention appended
with a mangled guid, but as far as I can tell the mechanism that rationalizes
all the folder name properties from merge modules (such as
CommonFilesFolder.guid) at merge time is indiscriminate. If the folder name
from
I'm creating a merge module for inclusion in another company's msi package.
It does not appear to be possible to put conditions (such as checking
operating system version or .net installed version) in the merge module.
How is that generally handled?
Thanks.
How you condition the Japanese and English resources are up to you. Both
must be in the CAB(s) if you intend to use a transform to supply the
translated installation package that way, and so the file table must be
the same for both original packages.
You could make them separate features, or you
dB, do you have a commit/rollback action that will subsequently erase that
file from the disk?
-Original Message-
From: dB. [mailto:dbl...@dblock.org]
Sent: Wednesday, December 09, 2009 6:21 AM
To: General discussion for Windows Installer XML toolset.
Cc: Vladimir Iahnenco
Subject: Re:
Are you talking about LaunchConditions, Feature conditions, or Component
conditions?
You can't isolate your merge module parts in a final MSI very easily, but
you should be able to condition any/all of your components and/or custom
actions your merge module contributes.
-Original
Bootstrapper.
-Original Message-
From: Kevin Garman [mailto:gar...@scadaware.com]
Sent: Wednesday, December 09, 2009 8:30 AM
To: wix-users
Subject: [WiX-users] Multiple installed instances and maintenance mode
Hi,
I've used the information contained in the following posts:
Well ya...I'm really trying to keep everything contained in a single
file (ie. the msi).
Thanks though.
On Wed, 2009-12-09 at 10:38 -0800, Blair wrote:
Bootstrapper.
-Original Message-
From: Kevin Garman [mailto:gar...@scadaware.com]
Sent: Wednesday, December 09, 2009 8:30 AM
To get a feel for how wix works, I created an installer project which
produces an .msi file. It includes conditions at the Product level (are
those launch conditions?) that check for os version and .net version,
exiting the install if the condition is not met. I'll convert that project
into a
This is actually another cry for help on what's probably a related issue with
installing a patch when users install to an alternate directory. The
original issue was that when patching our product the patch only works when
the user installs to the default directory, if they choose their own the
Hi Blair!
Those directories contain many files and I don't want to specify them by hand.
And if I want to ignore .svn directories, I'm fully out of luck.
Additionally, I tried to split up my project into several trees like that:
- framework\bin (common binary files, xml schema, ...)
-
When you refer to the currently installed location, are you referring to
the location that my product installs to by default or the location selected
by the user. If the latter, then the patch should be installing to that
location.
Blair-2 wrote:
Are your patches MSP files performing either
One file? Then use a self-extracting bootstrapper :)
On Thu, Dec 10, 2009 at 6:19 AM, Kevin Garman gar...@scadaware.com wrote:
Well ya...I'm really trying to keep everything contained in a single
file (ie. the msi).
Thanks though.
On Wed, 2009-12-09 at 10:38 -0800, Blair wrote:
How do you program WIX to display custom dialogs during an uninstall ?
I'm uninstalling my app from the Control Panel and I want to give the user the
ability to keep or drop
A database.
Rob Hermann
Senior Software Developer
Niceware International, LLC
10437 Innovation Drive
Suite 147
Unless there is a much more elegant method, you may try a good ole' Win32
method:
- use Spy++ to find the dialog ID of the control (s):
- use Setup Window title to find the dialog HWND (you may be doing this already
to parent your message window)
- get HWND of the control using GetDlgItem
- call
The current custom action code is in C#.
Any chances for setting the focus through managed code :(
--
View this message in context:
http://n2.nabble.com/Validation-on-UI-dialogs-tp4141605p4142556.html
Sent from the wix-users mailing list archive at Nabble.com.
You create /local/ accounts and groups, not domain accounts. If you
also need domain permissions, then your installation instructions
specify what local accounts/groups need to be added to what domain
group.
--
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
In article 481222.60726...@web30401.mail.mud.yahoo.com,
Sankaranarayanan loony...@yahoo.com writes:
For validating the fields in Custom UI for empty / null values - I am calling
a Custom action on DoAction event of the Next Button and spawing a new dialo
g if all the input values are
Is there a way to change the style of a Control in WixUI?
For example, background color, foreground color, font size, font type (bold,
italic), font name (Tahoma, etc)..
I want to change this per control, not the per dialog or the whole WIX UI.
eg:
Control Id=OrgNameLabel Type=Text X=20 Y=93
How do I go about adding an import to WiX project file in VS? I'm writing a
solution wizard which creates several projects and one of them is WiX project
for which I need to add one more import tag. I have access to EnvDTE.Project
object named proj. I tried adding import using
Nope, this an immediate CA, that's all it does.
You can use another immediate CA to delete the file or with some more code
build a deferred CA and/or a wix extension that has this behavior.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Blair
Correct. And my installer requirements is to validate that the accounts
specified happen to meet certain requirements, such as being a member of a
specified group. My requirements say to check for this error condition and do
not allow the installer to modify the system if the user specified bad
In article
fc8c44cef7807d4bbb771659436fd8445e39b60...@wa1annxvs011.redppe.local,
Baris Taze bt...@microsoft.com writes:
Is there a way to change the style of a Control in WixUI?
For example, background color, foreground color, font size, font type (bold,
italic), font name (Tahoma,
Hi All,
In the exemple in the SDK to use the AdvanceUI:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=APPLICATIONFOLDER Name=My Application Folder
...
/Directory
/Directory
/Directory
Property
shrug I don't think I would try to cram this into the installer.
If the installer isn't going to change the group membership, then it
shouldn't be gathering the information to query the group membeship.
Do it after installation time with a standalone configuration
utility. That way they can
Enter Requirement X: There should be no post-install configuration.
I tell you, these requirement peoples just love to get in the way! ;-)
BTW: I completely agree with you. I'm just pointing out that sometimes we get
forced to implement ugly requirements. I have to choose my battles. This one
Here's the key point from the SDK:
* To keep the nonfile data of each instance isolated, the base package
should collect nonfile data into sets of components for each instance. The
appropriate components should then be installed based on conditional
statements that depend on the instance
WiX exposes (for the most part) all of the power of native Windows
Installer. LaunchConditions are exposed by the Condition elements under the
Product and Fragment elements and result in entries into the LaunchCondition
table (http://msdn.microsoft.com/library/aa369752.aspx) which is processed
by
Two ideas that come to mind: One is to use msbuild to call heat (or some
other system that can calculate a list of files given an exclusion pattern)
and the other is to write an extension to heat.
-Original Message-
From: Markus Gaugusch [mailto:w...@gaugusch.at]
Sent: Wednesday,
The location that the components you are patching are already installed.
Could you share a log that shows it not working in that circumstance?
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Wednesday, December 09, 2009 1:55 PM
To: wix-users@lists.sourceforge.net
Symbols are not created for primary keys in tables unless the
tableDefinition/@createSymbols=yes.
On Mon, Dec 7, 2009 at 6:33 AM, Maciej Oszutowski im...@post.pl wrote:
Hi,
I'm developing WIX extension which creates number of custom tables. One of
them is similar to InstallExecuteSequence,
Wow, that's trippy. The table name *and* the action name are both blank. The
mergemod.dll (from the Windows Installer team) is responsible for populating
that data. You might try building the MSI then using Orca to merge in the
module and see if it comes up with a better error.
On Mon, Dec 7,
Nope.
On Tue, Dec 8, 2009 at 9:42 AM, Tony Juricic tjuri...@tradestation.comwrote:
I verified that WcaInitialize() is called. This is immediate CA that is the
target of a control event :
Publish Dialog=InstallDirDialog Control=Next Event=DoAction
Value=CAValidateFolder Order=21/Publish
I usually just write an XSL transform. heat supports that.
On Wed, Dec 9, 2009 at 9:45 PM, Blair os...@live.com wrote:
Two ideas that come to mind: One is to use msbuild to call heat (or some
other system that can calculate a list of files given an exclusion pattern)
and the other is to write
The APPLCIATIONFOLDER Directory will end up resolving to ProgramFilesFolder
with this code. Why do you want to install straight into ProgamFilesFolder?
That seems odd.
On Wed, Dec 9, 2009 at 6:06 PM, Andres Juarez andresj_...@hotmail.comwrote:
Hi All,
In the exemple in the SDK to use the
Windows Installer doesn't support that in the standard UI (it runs the
uninstall in basic UI). You'd have to write a bootstrapper and take over the
ARP registration yourself.
On Wed, Dec 9, 2009 at 2:23 PM, Robert Hermann rob.herm...@nicewareintl.com
wrote:
How do you program WIX to display
42 matches
Mail list logo
