Hi,
I am looking to put a check in my wxs file to detect if a windows service is
installed and if not fail the installation. Is there any in-built support to
achieve this (other than a Custom Action) ?
Regards,Surya
Thanks to all for the feedback.
I do agree with the consensus that Product1 is broken and should be fixed with
an upgrade or patch. However, in the real world, that isn't going to happen in
this case. As I said, Product1 and Product2 are side-by-side installs of the
same application, where ther
Hi all,
we deploy two MSIs to our customers which are almost identical.
The only difference is that 4 executables are slightly different (also named
differently) - all
other files are the same. The 4 executables also differ in their menu & desktop
shortcuts.
Could we use the feature element
Just like with JavaScript variable and method names, there are few rules and
lots of conflicting conventions.
Other than avoiding naming things with any case variation starting with the
three letter sequence M,S,I just be consistent within your organization.
Be aware of which namespaces overl
I need help creating a file association though a wix installer, where
heat generates the file list wxs (so ID's are dynamic), and I don't want
to rely on transforming that file.
I understand I am effectively adding a area to the component
area for my exe in the heat generated wxs.
I haven't foun
I agree. A common shared component has been updated and it needs fixing in
all the products because it can no longer be shared properly.
Phil
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Tuesday, August 13, 2013 10:14 AM
To: General discussion for Windows Instal
I was using WixExtendedBootstrapperApplication.HyperlinkLicesne and I
upgraded to Wix 3.8.722 and am using
WixStandardBootstrapperApplication.HyperlinkLargeLicense. I had perviously
(in 3.7) captured the thm.xml file from the \ba1 folder and added it to my
project, and then edited it. Prior to ed
Thanks Neil,
Before I look at moving over to 3.8 could you let me know what I would have
to do to use the extended BA to test how that works with 3.7. Basically what
changes do I have to make and if there are any files I have to be editing to
actually make it work?
I have not done alot of Win 8 t
If your trying to be minimalist you could try distributing the votive msi from
the Wix setup exe (run the /layout switch to download the msis) but there are
other benefits to just installing all of Wix using the exe.
"Drake, David" wrote:
I'm just about to start checking in WIX installer pro
True, and assemblies in the GAC too, this:
http://support.microsoft.com/kb/905238/en-us
I believe it's fixed in Windows 7 and 8, and there's a hotfix for it, I
think this is it:
http://support.microsoft.com/kb/972397/en-us
But it's not redistributable - customers need to install it, not setup
I think Windows 8 might be introducing a new variant, I have only tested
Windows XP and 7.
In the past I have only tested local language variant by installing the local
OS version (this is not WiX specific I have done a lot of UI localisation). Now
with the multi-language OS option in Windows
I believe I have fixed this with the extended BA I wrote and then I applied the
same code to WiX 3.8 - so the options would be to use WiX 3.8 or the extended
BA but reading Phil's comments regarding Windows 8 there may be more to it.
>From my testing I thought I had the correct solution but I am
I stand corrected.
Rob Mensching wrote:
No, don't force features to not be uninstalled when uninstalling. Crazy
things will happen. In general, don't mess with feature selection lightly.
Michael, I misread the word "dependency". I think you have analyzed the
math on this correctly. This is one
Are there any naming conventions for the different parts to a WIX
application? Components, File, Directories etc - Everything seems to vary I
find on the internet, and even to the book I have.
Thanks,
Chris Bunn
214-250-5602
---
Neil, thanks for pointing out what the code does.
I am running WiX 3.7 on Win 7 64 bit the problem is that when I have the
System OS set to French, the current language that I have been testing, and
run the burn wrapper .exe the burn UI will only appear in English.
When I add the -lang 1036 to th
OK I unravelled the Windows 8 configuration issue. This test system I
thought was configured for German and English and I thought that I was
setting both the System Default and the User Default to 1031 for these
tests. I would change the order of the list under Language Preferences
(based on vari
Hi all,
we currently produce 2 MSIs that differ only as follows:
4 executables included in both MSIs have different names and slightly
different functionality and also different menu & desktop shortcuts. All
other files are identical.
Could these be delivered in one MSI and the feature element b
Too clarify my comment about not being able to see what the result is for:
langid = GetUserDefaultLangID() (in locutil.cpp)
The issue is that LANGID langid is a type that WinDbg cannot interpret,
however when I step into the call with the disassembler I can see that
Windows 8 is returning 0x0409
I don't mean to side-track Tim's question but to clarify I was (and I think
Tim is) running under Wix 3.7 and for me under Wix 3.7 on Windows 8 I never
saw it select one of my wxl languages without me using the -lang switch.
Neil said earlier that there was a bug in Wix 3.7 so I updated to Wix
3.8
Great - Thanks!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, August 13, 2013 12:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Display value in message - Burn
"[ServicePackLevel]"?
On Tue, Aug 13, 2013 at
The code does the following:
1. Read the -lang command line
2. Call
GetUserDefaultLangID()http://msdn.microsoft.com/en-us/library/windows/desktop/dd318134(v=vs.85).aspx
this should get the current users language.
3. Try the current user langid but without the sub language.
4. Call
GetSystemDefau
"[ServicePackLevel]"?
On Tue, Aug 13, 2013 at 9:57 AM, Christopher M. Bunn <
cmb...@torchmarkcorp.com> wrote:
> Is there a way to display the actual value of ServicePack embedded in the
> message in Burn? Thanks!
>
>
>
> (VersionNT >= v5.1 AND ServicePackLevel >= 3) OR (VersionNT64 >= v5.1
> AN
This is now a bug in product1. It needs fixing at a priority that your
product owner decides. You must have an update strategy for that product,
what if it has a critical security issue/flaw?
You could release product2 as a burn bundle and include a fix in it for
product1 by adding a major upgrade
Rob, excuse a non-experienced programmer here.
I was looking at the code for the LocProbeForFile function was wondering
about it. In the first if statement you are checking to see if a language
was specified. Is this coming from a language selection dialog box and/or
from the -lang LangID cmd line
Is there a way to display the actual value of ServicePack embedded in the
message in Burn? Thanks!
(VersionNT >= v5.1 AND ServicePackLevel >= 3) OR (VersionNT64 >= v5.1 AND
ServicePackLevel >= 3)
Thanks,
Chris Bunn
---
I have my bundle building under WiX 3.8 and yes on Windows 8 Professional
with German selected as the default language, the bundle showed my localized
German strings without the need for the -lang switch.
I have yet to implement Neil's suggestion to create a localized variable in
my wxl files whic
I'm just about to start checking in WIX installer projects into some of my
developers VS2012 solutions, but before I do that, I want to make sure they can
still open them themselves without getting the error about unknown project
types.
I have the WIX binaries checked into source control and ea
Tim, I'm still working on it, but with other responsibilities here at work
have not made much progress yet. I do not have my project building under
3.8 yet. Last week I went down the route to change from using
WixBootstrapperApplication.HyperlinkLicense to
WixExtendedBootstrapperApplication.Hyper
PS: The code you are interested in is in
src\ext\BalExtension\wixstdba\WixStandardBootstrapperApplication.cpp,
LoadLocalization(). That uses the helper function LocProbeForFile() that is
in src\dutil\locutil.cpp
On Tue, Aug 13, 2013 at 7:17 AM, TimM wrote:
> So Phill, did you have a chance to t
So Phill, did you have a chance to try any of these suggestions and/or WiX
3.8 to see if you can get the Burn wrapper .exe to launch correctly in the
language of the OS?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi
No, don't force features to not be uninstalled when uninstalling. Crazy
things will happen. In general, don't mess with feature selection lightly.
Michael, I misread the word "dependency". I think you have analyzed the
math on this correctly. This is one of the scenarios where the Component
Rules
Brian,
I currently already have English MSI and supported language .mst's in my
Burn Wrapper .exe. I generated the language .mst in my VS 2010 project by
running the PostBuildEvent Torch.exe -t language command on each of the
language .msi file compared against the English .msi.
So the Burn Wrapp
run light with the verbose switch and see what it says.
I would recommend not changing CabinetCachePath from the default (unless you
are placing it on a different volume or some other location outside of your
build tree's objects).
> From: j...@jeffnevins.com
> Date: Tue, 13 Aug 2013 00:30:41
You could put D2.dll into its own feature, and force that feature to not be
removed on product removal if product 1 is still installed. You get the same
"effect" of D2.dll getting orphaned but at least you don't perpetrate the
problems of sharing binaries in the same component in all other scena
There is a gotcha to be consider if you incorporate any Win32 SxS (such as
using the Visual Studio runtime MSMs) in your MSIs it is possible for "early"
RemoveExistingProducts to "forget" to reinstall the SxS (a subsequent repair
does resolve that, but it is quite annoying when it happens).
>
A very good feature request would be a validation that the schema of those
files is correct at build time.
A very good bug would be to get an error message at runtime that the failure is
(or even may be) due to problems with the contents of one of these files (in
addition to 0x80131902).
> D
36 matches
Mail list logo
