I cant remember ever seeing a
specific UK version of any software that I've installed
Install anySerif http://www.serif.com/ App (you get a choice).
--
Write once. Port to many.
Get the SDK and tools to simplify
call the main installer
wixproj you get the defaults). Is this feasible, or is there a better way
to do this?
Thanks
Matt O'Connell
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate
, or is there a better way
to do this?
Thanks
Matt O'Connell
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced
Use NOT VersionNT64 as below:
Condition Message=!(loc.CONDITION_Message1)
!-- OS must be Windows XP (32-bit) SP3 OR 2003 Server (32-bit) SP2 OR
Vista and above --
(VersionNT = 501 AND ServicePackLevel=3 AND NOT (VersionNT64))
OR (VersionNT = 502 AND ServicePackLevel=2 AND NOT
Sorry that's wrong please disregard.
On 15/01/2014 14:50, Matt O'Connell wrote:
Use NOT VersionNT64 as below:
Condition Message=!(loc.CONDITION_Message1)
!-- OS must be Windows XP (32-bit) SP3 OR 2003 Server (32-bit) SP2 OR
Vista and above --
(VersionNT = 501 AND ServicePackLevel=3
Many Thanks. The new WiX home page is great (as WiX deserves). Just in
case you don't know already (non www) wixtoolset.org still points to old
redirect page.
Matt O'Connell
On 21/01/2012 07:51, Rob Mensching wrote:
Just: http://robmensching.com/blog/posts/2012/1/20/The-wixtoolset.org-online
WholeFilesOnly=yes change to no
Order=2 change to 1
patch runnup issue - did you change the package code for the updated msi?
On 18/07/2012 12:34, Farrukhw wrote:
Thanks all for your replies. I've just posted my resultant patch script here:
Small updates do not require changing the product code! This forces a
major update and thus your update is massive:-) . All msi file have a
package code which should probably be left to generate automatically.
This should be changed in any event.
As an aside, if you can find a reason to update
Hi WiX users
I've got a product B that shares a (hidden) feature with it's
predecessor A. If I install A over B the registry we use toggles back
the the old app location. Since we may want to have update B's feature
at some point this is bad.
My company doesn't like to uninstall the old
are often susceptible to this
problem. Although, I can't say I quite understand your upgrade path if you
don't use major upgrades. Is the user expected to remove the old product on
their own?
On Tue, Aug 21, 2012 at 3:09 AM, Matt O'Connell
techsupport...@gmail.comwrote:
Hi WiX users
I've got
That's not what I've found. I've got a custom action running which
changes our ProductName at install time in WiX 3.5. It is one our first
actions in our InstallExecuteSequence and seems to work. All the Actions
before it need to not reference [ProductName] or else get the 'wrong'
result. Can
I have a 64-Bit MSI that needs to set reg permisions on some keys via
the LcokPermissions table (my 32-Bit MSI still uses subinacl in a CA).
It is having a reproducable error that I need to fix.
I have 2 registry entires in referenced in my LockPermissions table.
Both set to 'Everyone' with
Use the version lying technique: Change the version of this FileId to
10.1.1 in your patch upgrade image by editing the msi in orca. Then
re-build the patch pointing to your edited MSI.
When the patch installs on top of the localised version it won't matter
that the transform has removed this
FYI, I had to this issue today and copying the ProjectAggregator2.msi
next to my wix3.7.exe worked. (I have both VS 2005 and 2008)
Log entries for failure:
[105C:11BC][2014-03-28T15:42:31]i000: Caching bundle from:
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of antivirus
and we presumed it's some kind of conflict with that but we've had no
success with disabling Anti-virus with
:47:26:862]: SECREPAIR: Failed to create hash for the
install source files
MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in
progress.'
On 26/08/2014 11:05, Matt O'Connell wrote:
We've
of a Bundle, some other mechanism?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Matt O'Connell [mailto:techsupport...@gmail.com]
Sent: Tuesday, August 26, 2014 3:35
For those without a support contract, where's the most visible place to
post? msdn forums (clickonce and setup deployment projects, I've never
found an MSI one...) or microsoft.public.platformsdk.msi newsgroup? The
installer team blog would've been a good place but its not updated anymore..
Create a stub msi and merge into that?
On 06/10/2014 19:07, shannon wrote:
Using an msi output only, is it possible to install prereq's first via wix?
Specifically, I need to install the VC2008/2013 runtimes, and these must be
completed before the product install begins or the install will
http://wixtoolset.org/documentation/manual/v3/xsd/wix/file.html
(use Hidden attribute)
On 09/10/2014 07:55, Fabrice MAUPIN wrote:
Hello everybody,
This is an extract of my WXS configuration file :
DirectoryRef Id=APPLICATIONFOLDER
Component Id=MyFileId Guid=.
Many moons ago we stopped adding a 'launch the installed app' check box
to our final dialog as we had intermittent issues with the launched app
window appearing behind other windows as per this WiX mailing list issue
from 2005:
http://sourceforge.net/p/wix/mailman/message/11428915/
We didn't
I've got a third party exe with 2 versions to bootstrap based on OS
bittage, our current setup code only does this for MSIs. I've found how
to do this with burn bundle but don't need the bundleness of it as per
this
advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.
-Original Message-
From: Matt O'Connell [mailto:techsupport...@gmail.com]
Sent: 09 July
(and conditionalise) the exes but
hide the bundle's ARP entry and expose the third party exes ARP entries? If
so could the user could use that to repair/uninstall so it effectively
wouldn't appear that the package had been 'bundled'?
Many Thanks
On 17 June 2015 at 12:36, Matt O'Connell techsupport...@gmail.com
question would be why. What do you need to do that you can't at
least allow your bundle be in the chain and let burn do its work before
deferring to your final exe installer?
-Original Message-
From: Matt O'Connell [mailto:techsupport...@gmail.com]
Sent: Wednesday, July 08, 2015 7:41 PM
Building, West Of Scotland Science Park, Glasgow
G20 0SP
Email Disclaimer
-Original Message-
From: Matt O'Connell [mailto:techsupport...@gmail.com]
Sent: 09 July 2015 11:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage
Thank David yes I
26 matches
Mail list logo