To display the version you need to set
(I think this is documented in the help file but if not let me know and I'll
add it.)
Neil
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 13 August 2013 23:08
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Th
Is there a quick way to check this? I'd like to warn my users that a restart
is needed before they try to install my software and it fails.
I'm using the customBA so I'd like to get access in the RootViewModel.
Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.68
Hi all,
my next problem is this:
I have to deal with MSIs that are out in the wild (created with Wise); our next
MSIs will be created
with Wix since Wise doesn't exist anymore.
These old MSIs have installed an inifile that needs to survive a major upgrade
coming from the new
Wix based MSI
Here's what I remember about 3.7, I haven't used 3.8. The m_fPrereq variable
is associated with a managed bootstrapper. m_fPrereq is essentially a boolean
specifying whether the magic Burn variable WixMbaPrereqPackageId is set (that
variable specifies the PackageId for .NET). Since you're not
Affirmative
On Wed, 2013-08-14 at 14:27 -0700, Phill Hogland wrote:
> Question ?
>
>
> Is "galileoGlobalProject" your file extension like .doc or .png (without
> the period)?
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-a-Targ
Question ?
Is "galileoGlobalProject" your file extension like .doc or .png (without
the period)?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-a-TargetProperty-in-a-Verb-in-a-ProgId-for-file-association-tp7588039p7588042.html
Sent from the
I do not feel qualified to answer your question, which is why I did not
comment earlier. I am not using heat (or rather I used it to make my first
wxs and then decided to do a lot of editing) and I got the file association
stuff working a few weeks ago, for the first time. I started from a sample
There are some samples on the extended BA site that should help - if you have
any problems it would be preferable if you posted questions there.
Neil
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: 13 August 2013 22:47
To: wix-users@lists.sourceforge.net
Subject: Re
I am using wix-3.7 on windows7, to associate my program (Compass.exe)
with file-names ending in galileoGlobalProject.
I can build the msi and install it, but double clicking a file raises
error dialog: "Windows cannot access the specified device, path, or
file. You may not have the appropriate pe
but I wouldn't encourage this solution until the actual problem has been
found. The common issues with failing upgrades that result in two
Programs/Features entries seem to be:
1. A per-user install won't upgrade a per-system install, and vice versa.
2. Forgetting something like a majorupgra
If a patch is installed without custom actions altering feature install states
the patch will only repair the features already installed that contain patched
components.
What happens to your feature states if you simply run "repair"?
How are you running your patch?
> Date: Wed, 14 Aug 2013
As I step through the Wix 3.8.722 code I observe in:
src\ext\BalExtension\Wixstdba\WixStandardBootstrapperApplication.cpp
at line 916
"
LoadBootstrapperBAFunctions();
if (m_fPrereq)
{
hr = ParsePrerequisiteInformationFromXml(pixdManifest);
BalExitOnF
Hi all,
my problem is this:
I have to deal with MSIs that are out in the wild (created with Wise); our
next MSIs will be created with Wix since Wise doesn't exist anymore.
These old MSIs have installed an inifile that needs to survive a major
upgrade coming from the new Wix based MSI.
>From dec
Thanks everyone for your help with this. For future reference:
Using WiX 3.7
Typo in directory name (Resources/Resource)
Removed this line:
Changed BuildAction to None and Copy to Output Directory to DoNotCopy
These actions solved the errors.
Thanks,
Marlos
2013/8/14 Phill Hogland
> Also I
A windows service always has an associated registry key under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services
Then use the method detailed here:
http://wix.sourceforge.net/manual-wix3/read_a_registry_entry.htm
--
View this message in context:
http://windows-installer-xml-wix-toolset.687
Also I am using Wix 3.8.722, which I assume from your question you are also
using 3.8. The concept in 3.7 is the same, but it has an issue detecting
the correct language, and the syntax of these statements is a little
different.
--
View this message in context:
http://windows-installer-xml-wix
Regarding this comment:
>>>I was looking at wixstdba.vcxproj in WiX source and these files are
included as None and with flag CopyToOutputSubDirectory, but we don't
have this option in C# (or we do?).
My bundle project is a WiX bootstapper project,, not C#. Originally I did
not add any of thes
I am doing this in my WixStaBA. The error implies that your project file
structure is not:
\Resource\RtfTheme.xml and RtfTheme.wxl
One thing that caused a problem for me initially was that I used a folder
name "Resources" but used "Resource" in the Wxs file. A simple typo as some
examples use "
Hi,
I have done exactly the same. Just put the WixVariables before the
BootstrapperApplicationRef and it should work.
Bernd
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-theme-in-Bundle-how-to-add-xml-and-wxl-tp7588021p7588022.html
Sent
I had this or a similar problem with InstallShield. The previous version
was upgraded but the entry wasn't deleted. So I created a cleanup Component
to delete the old registry key. Just check if the previous version was
correctly uninstalled during upgrade.
Here is my code:
WIX_UPGRADE_DETEC
Hi,
I'm trying to create a custom theme for my Bundle using this:
I added the files from WiX source code, so no error in them, but I
keep receiving error "The system cannot find the file
'Resource\RtfTheme.wxl". They are set in VS as None. If I change to
EmbeddedResource, the error changes to "
Thanks David for your response.
Wix automatic behaviour works for Typical installation and complete
installation and not for Customize installation. Looks like Wix patch
does not remember what features were installed using customize option
and it is installing all the features during the deploymen
And version changed from 1.0.0.0 to 1.1.0.0
On Wed, Aug 14, 2013 at 3:26 PM, Alain Forget wrote:
> Are you using the MajorUpgrade element?
>
> -Original Message-
> From: Андрій Цьок [mailto:andrey.t...@gmail.com]
> Sent: Wednesday, August 14, 2013 08:23
> To: wix-users@lists.sourcefor
Are you using the MajorUpgrade element?
-Original Message-
From: Андрій Цьок [mailto:andrey.t...@gmail.com]
Sent: Wednesday, August 14, 2013 08:23
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix and backward compatibility with Visual Studio setup
project.
After installing n
After installing new version app using Wix installer I see duplicate app in
"Program and features".
Can Wix installer remove previous Visual Studio Setup project (with
installed app files) before installing the app ?
PS: UpgradeCode is the same as in "VS setup project" and "Version number"
is grea
Try the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/wix-users
-Original Message-
From: Mike Scott [mailto:mike.sc...@bbc.co.uk]
Sent: Wednesday, August 14, 2013 07:44
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] unsubscribe
http://www.bbc.co.uk/
Thi
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor
The latter behaviour is automatic, only installed features are patched.
-Original Message-
From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com]
Sent: 14 August 2013 10:12
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom installation in Wix Patch
In the wix major upgrad
When we release side by side versions of products we have to
reversion/relocate(re-guid if com) all our shared components.
e.g.
All file major versions are increased and we install into different
locations.
All com components have version dependent naming and are reworked to not
clash with previo
In the wix major upgrade, I have a set of features and the end user has
the option to install either typical, custom or complete features.
In case of wix patch release, is it possible to give the user the same
option of typical, custom or complete installation type.
Else during the deployme
yes, features can be used that way.
You can also have a feature you don't show for your common elements that is
always installed, or you can reference your common elements in both of your
features. It'll work either way.
> From: kpet...@otaksoft.com
> To: wix-users@lists.sourceforge.net
> Dat
31 matches
Mail list logo
