Hello,
Can you install the Server by hand?
Iirc you do not need / should use XML entity escaping in variables. But perhaps
I am wrong. ( if I want a "&" inside the ``manufacturer``-Tag, I need to write
``&`` - but when I delegate that into a variable I can refer to the ``&``
symbol)
-Ursp
Thanks Bob.
The trick is how to get that localisation value into my project and have it
vary for two builds. I finally worked out a way.
The basic idea is to use the culture to providing wrapping of the language ID
for localisation and force generation of two cultures.
So I have two wxl files
On 03-Oct-12 21:24, DENT Andy wrote:
> I can get the projects to build for multiple cultures but how do I vary the
> Language attribute per-culture?
Use a !(loc.stringid) loc string for Language's value.
--
sig://boB
http://joyofsetup.com/
--
On 03-Oct-12 18:03, tom wrote:
> Is this make sense to change the package state in the
> PlanPackageBegin event? i did it and the event is called.
Yes, that makes perfect sense.
--
sig://boB
http://joyofsetup.com/
--
Do
On 03-Oct-12 16:12, garnold wrote:
> However, I can't see a way to show a Windows Installer dialog from a custom
> action.
See MsiDoAction.
--
sig://boB
http://joyofsetup.com/
--
Don't let slow site performance ruin you
On 03-Oct-12 06:40, Stelios Kyprou wrote:
> Strange right?
Indeed. Please file a bug.
--
sig://boB
http://joyofsetup.com/
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app
The Guide page
http://wix.sourceforge.net/manual-wix3/make_installer_localizable.htm shows an
example of how to localize strings but still hardcodes
Product/@Language="1033". I haven't found any other samples which differ in
this important aspect.
We have a fairly complex installer with 15 mer
I would look at how Wix did their custom BA.
IE, in your bundle chain..
And then include
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
http://downloa
Looks like /LaunchAction.Modify/ does not modify the package state
and it stay in a None state
(I think Rob also mentioned it somewhere)
The engine Process Package function check if the package should be processed
//If the package is in a requested state, plan it.
if (BOOTSTRAPPER_REQUEST_STATE
its a dependency of a MSI that I am installing, once I get it working
properly I can take out that condition in the MSI...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installCondition-vs-Product-wxs-Condition-tp7581071p7581073.html
Sent fr
Are you writing your own BA? IE, is it a BA prerequisite because you have a
MBA, or is it just a dependency of a MSI you are installing?
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: Wednesday, October 03, 2012 4:34 PM
To: wix-users@lists.sourceforge.net
Subject:
Sigh,
This is driving me nuts :(
I have a pre requesite of .NET 4.0 in my bootstrapper, so in bundle.wxs I
have:
doesn't work...
In my product.wxs I have a condition:
http://www.microsoft.com/en-us/download/default.aspx then restart the
$(var.ProductName) setup.">
NETFRAMEWORK40FULL = "
Here's an example to show the behavior described in the previous email.
The WiX project contains 2 Custom actions: C++ DLL and Javascript. Both of them
perform a simple WMI query.
Both work fine on Windows Server 2008 R2 (GUI)
Only the C++ one works on Windows Server 2008 R2 (Core)
Sources:
h
Hi Justin,
try using the following command to install msp:
msiexec.exe /p patch.msp /l*vx patch.log /qb REINSTALL=ALL
REINSTALLMODE=ecmus
this works fine for, because if i install the msp without running from
command line then the files dont get replaced, this is because my file
version is same f
You don't have to use a C# UI there is also a much more standard UI -
WixStandardBootstrapperApplication
http://wix.sourceforge.net/manual-wix3/wixstdba_intro.htm. From what I remember
of screen readers (admittedly based on work I did 20 years ago) I think they
should be compatible.
Neil
Implementing support for MSAA could be as simple as implementing IAccessable on
the interactive UI components, though I seem to remember some other framework
change that had to happen in order for the OS to interact with it.
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quans
It is possible to improve screen reader support by supporting Microsoft UI
Automation or Microsoft Active Accessibility (MSAA). Older screen readers
supported MSAA. Modern screen readers should support Microsoft UI Automation.
WPF has support for UI Automation but not MSAA.
Daniel Madill
Chief
You see, it's not a bug; it's a problem with screen readers being able to
communicate properly with the interface; custom controls are harder for screen
readers to recognize. I honestly don't know how to "report" this one since it
would require me to demo the issue; or else you wouldn't underst
So 99% of the files are 32 bit and if the Outlook bit is 32bit the 64 bit files
are not installed and it is installed to ProgramFilesFolder... if the Outlook
bit is 64 then the 99% plus the 3 64 bit files are installed to
ProgramFiles64Folder it seems silly to have 2 msi's for changing a path an
A follow up. When I build the patch, I get this message relating to the new
sub folders:
pyro.exe : warning PYRO1110 : Component 'U8_2_p02_0_oracle' was added to
feature 'oraUpgrade'. If you cannot guarantee that this feature will always be
installed, you should consider adding new components
I'd say it was more than a recommendation. The docs explicitly say that
32-bit packages can contain only 32-bit components, so with any 32-bit
components you're pretty well bound to making a package for 32-bit and
another for 64-bit.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa36745
32-bit MSI cannot install to a 64-bit location. It's a Windows Installer
limitation.
On Wed, Oct 3, 2012 at 9:38 AM, Steven Ogilvie wrote:
> The only difference between the two installers is 3 files... the 3 files
> are either 32 bit or 64 bit depending on the bit of Outlook seems to be a
> lot o
The only difference between the two installers is 3 files... the 3 files are
either 32 bit or 64 bit depending on the bit of Outlook seems to be a lot of
maintenance for something simple as changing the installdir from
programfilesfolder to programfiles64folder for two different features...
---
The usual recommendation is to create separate installers for 32 and 64 bit.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 03 October 2012 17:15
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] different features to differentProgramFilesFolder...
I re
I really need some help in this please...
I have 1 feature being installed to programfiles64folder (it depends whether
or not it gets installed to programfilesfolder or programfiles64folder) and
another feature to programfilesfolder
I haven't been able to accomplish this...
thanks,
Steve
--
I've run into a strange issue with a patch that maybe I can get some direction
from this group.
I generate a patch file (msp) performing the following commands:
"C:\Program Files\WixEdit\wix-3.0.5419.0\candle.exe"
"J:\Tw8-2z\Pro02\Disks\Xi\TabWareXiTools8202.wxs" -ext W
Your patch is fine.
The warning is just saying that if your new component is added to a feature
that isn't always installed, the user may get prompted to insert the
installation disk or browse to the original MSI under some circumstances.
A list of what you can and can't do in a small/minor upgr
Hi Peter,
thanks for kindly getting back to me, its a huge relief know that "Adding
files is possible".
Wow i just tried it now and it worked perfectly.
it gives me this warning tho: *"pyro.exe : warning PYRO1110 : Component
'cmpC6E1B04C03994D77B5ADB160491AD20E' was added to feature
'ProductFeat
Thanks Daniel I hadn't found that help topic. Seems to be correct. Super!!
:)
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: 03 October 2012 15:23
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Order Issue
>From the msdn h
You can add a file in a patch. You create a new component for the file in the
updated MSI and reference that component in your patch in the usual way.
-Original Message-
From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com]
Sent: 03 October 2012 15:17
To: General discussion for Wi
Only the changes you reference will be included in the patch, so
componentrefs for components and propertyrefs for properties. Just add
into your family.
-Original Message-
From: Kajal Kumar Biswas [mailto:kbis...@adobe.com]
Sent: 03 October 2012 14:32
To: wix-users@lists.sourceforge.net
>From the msdn help on the ControlEvent Table (see
>http://msdn.microsoft.com/library/aa368037.aspx):
"The exception to note is that each control can publish at most one NewDialog
or one SpawnDialog event. If you need to author multiple NewDialog and
SpawnDialog control events in this table,
I thought that but was told on this that it was the other way about..:/ no
wonder I am confused..lol
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 03 October 2012 14:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Or
1 would be first then 2 then 3 etc... order=1 order=2 etc...
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: October-03-12 9:32 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Order Issue
Am I right in thinking tha
Am I right in thinking that whichever action I add Order="1" element to it
will be run last?
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 03 October 2012 14:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Order Issue
Hi,
I'm creating a patch using the wix toolset (not using the pcp technique).
I can create the patch successfully and can orca the msi and view the contents
of the patch.
But the problem is the ProductVersion does not get bumpted up while I open the
patch over the target msi in orca.
Steps follo
Use the Order="1" element that way you can sequence the events you want to be
triggered...
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: October-03-12 7:23 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Order Issue
Hi can someone please e
Hi can someone please explain the way the ordering works in Wix. I'm unsure
about the logic and would greatly appreciate if someone could help me. I
have this next button:
1
I want these events to be
I narrowed it down to one use case, but I don't know why this is happening:
It's when I have a custom action project included in the MergeModule, and I
define a custom action that calls it (you don't even have to schedule it in the
execute sequence).
Then if I make an irrelevant property as Secur
39 matches
Mail list logo
