@ Bob: you said:
You can add your own localization strings to add a text style.
Otherwise, no; the strings in the subtitle don't have a text style so
they get the default style.
But you don´t say how I get it work.
Can you tell it?
--
View this message in context:
I do not have direct experience with this, but from studying the source code
for another purpose, I think you need to do something like:
Fragment
ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER
Component Id=ProductComponent
File Id=VSIXProject.vsix
You probably need to go into the WiX source (found here:
https://wix.codeplex.com/downloads/get/58) and get the a copy of the .wxl
and .xml files of the theme your installer uses. In my case, these were the
RtfTheme files in the BalExtension. You can then edit these local copies
however
I have one product under development where that would be very useful since I
need to know the state on repair to fix up permissions on multiple databases.
Currently, I work around it by detecting the WCF service assemblies for each,
but detecting the Upgrade Code for each would be much cleaner
Thanks Blair...
When i apply the patch. I don't see the changed .dll applied. On going
through the logs i see below log.
MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't
Overwrite;Won't patch;Existing file is of an equal version
Do I have to change version
Add a Tag in Property tag
Property Id='REINSTALLMODE' Value='amus'/
On 13-11-2013 20:46, Nagesh Hora wrote:
Thanks Blair...
When i apply the patch. I don't see the changed .dll applied. On going
through the logs i see below log.
MSI (s) (14:74) [23:44:05:695]: File:Component Name;
You need to increment the file versions for patched files, basically
because updates are based on them.
http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx
Something like REINSTALLMODE=amus is not a good idea. If you have included
merge modules from 3rd parties, or Microsoft merge
Is there any way to unsubscribe from this mailing list?
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Wednesday, November 13, 2013 10:39 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Creating multiple Minor Updates
You need to
At the bottom of every e-mail, there is this link where you can do it:
https://lists.sourceforge.net/lists/listinfo/wix-users
See the bottom of the page; put your e-mail address there and unsubscribe.
-Original Message-
From: Jacky Liang [mailto:jli...@kierantimberlake.com]
Sent:
I have been testing the 2 patching methods for WiX:
Using Patch Creation Properties
Using Purely WiX
I have created basic samples for both and got both of them working okay so I
am now try a real install upgrade patch.
So I get the .msi and .wixpdb files for say version 1.0 and for version 1.1
Hello,
We are writing a Visual Studio 2013 extension and would be very grateful if we
could get the awesome changes on your wix38 branch. Are you looking to
release off that branch soon?
Thanks for the fantastic work you guys have done so far on Wix Toolset!
Chirayu
Yes,
http://www.joyofsetup.com/2013/10/31/wix-v3-8-rc-available/
-Original Message-
From: Chirayu Shishodiya [mailto:chirayu.shishod...@red-gate.com]
Sent: Wednesday, November 13, 2013 1:45 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Request for release of wix38
Here is part of my build log and all are referring to binary and merge Id's
that are listed in fragment files and referencing the path that our build
machine created for the build:
D:\BuildAgent72\work\9f69624fb270635f\BoardSW\install\win\SMART Product
Drivers
\Core_x86PNPDrivers.wxs(158) : error
Thanks Blair for the quick response.
I should have been more clear.. What i meant was that all of the .msi
installers were configured for major upgrades.
I figured out the problem. The problem is with the bootstrapper C++ code.
One last thing: With AlwaysInstallElevated, when the installer runs
For MSI UI, Text Styles are described in the following paragraph from the page:
http://msdn.microsoft.com/library/windows/desktop/aa367524.aspx
Controls can have a predefined font style. To set the font and font style of a
text string, prefix the string of displayed characters with {\style} or
Nagesh, Phil is correct. See the file versioning rules on MSDN.
http://msdn.microsoft.com/library/windows/desktop/aa368599.aspx
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Wednesday, November 13, 2013 10:39 AM
To: General discussion about the WiX
That looks like a melt bug to me. Please file it and if you can please link a
copy of the/a repro.
Blair
Date: Wed, 13 Nov 2013 14:05:11 -0800
From: timmay...@smarttech.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating Wix Pure patch with Melt.exe and Pyro.exe
There are several possible things that can lead up to a 1625 (forbidden) error
code (only way to disambiguate them is via a verbose log) and by definition if
two MSI files share the same ProductCode it is NOT a major upgrade.
Date: Wed, 13 Nov 2013 20:21:00 -0800
From: kirann.he...@gmail.com
Hi,
IMO, useful thing to check minimal free disk space for whole burn bundle,
running before installation start as condition.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-disk-space-usage-calculation-td6984846.html
Thank you for answering!
@ Blair: Where and how can I edit the TextStyle table? I tried it in the
localization wxl file, in the file where the dialogs are defined and also in
the normal wxs file. But nothing worked.
--
View this message in context:
20 matches
Mail list logo
