Hi, I am new to WIX
I am executing a batch from wix and that batch file which actually installs
some other application so if that installation is failed the batch file will
be sending appropriate error code why it got failed. How to get those
appropriate error codes from that batch file to wix and
Hi guys,
I'm having an issue with components with feature conditions not being actioned.
My feature tree is:
The installer is intended to configure a web.config connection string for the
first installation
Hi Pally,
I understand that would be the expected outcome, but where are those components
defined? My understanding is the heat uses these references to dynamically
determine the components and their contents at compile time based on the
contents of the referenced project. I can't find any actu
To contribute it back, you have to execute an assignment agreement with the
project's owner (standard procedure with most OSS projects) which happens to
be Microsoft in this case. The biggest downside is that while the agreement
is nothing out of the ordinary, it sometimes seems to take them foreve
No, not at all, but if you add the property IncludeSearchPaths that contains
a semi-colon delimited list of paths to search for .wxi files to the wixproj
that fails that might resolve the issue.
-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
Sent: Tuesday, Ma
In my VS2008 solution I have three wixproj. One of these projects
contains a file called Restrictions.wxi. The other two projects
reference the existing Restrictions.wxi file as a link so that there is
only one actual copy. One project referencing the file as a link
compiles ok. Another project
I re-installed and everything is working fine now. Thanks!
A
On Mon, May 24, 2010 at 11:22 AM, Blair wrote:
> The RTM 3.0 wix.targets file contains the element for that
> task.
> Verify that your wix.targets file is not corrupted.
>
> -Original Message-
> From: Andrew Hammond [mailto:a
Thanks for the pointers Phil!
I would just like to clarify that the root of the problem that I'm having seems
to be in the fact that nothing gets installed, not even the policy files. I
looked into the manifest of all of my executables, finding entries like:
That is expected since I am inde
Thanks!
Jeff
> Not in the stock WiXUI's. You'll have to add your own Dialog to gather
> that information from the user.
>
> See the last section at ->
> http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141
The issues are typically:
Debug vs Release builds with different CRT requirements in the manifest (debug
not same as release).
People using merge modules, but not the policy merge modules that redirect old
versions of the CRT up to the newer one. That means that sometimes you get
inconsistent
Not in the stock WiXUI's. You'll have to add your own Dialog to gather
that information from the user.
See the last section at ->
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8
Is it possible to present the user with the option to install for everyone
or just the current user? I know there is the option to explicitly set
the option:
...I just realized that my old installer (built using a VisualStudio
Deployment Project) gives the user an option to pick between inst
Thanks everyone, I got it working now. It turns out it was a combination
of two things:
As Chris suggested, I checked and didn't have an ALLUSERS setting. Since
my previous installers defaulted to "Everyone" I added
And as Neil pointed out, I needed to match the UpgradeCode but the Product
Does this thread help?
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Windows-Service-not-removed-on-Uninstall-td710002.html
What is the "Action" of the component with your service, from the uninstall
log?
--
View this message in context:
http://windows-installer-xml-wix-toolset
Jeff,
What does the verbose log say?
Chris
On 05/25/2010 02:55 AM, s...@pacaccess.com wrote:
> Prior to my upcoming release I used a VisualStudio deployment project to
> create the installer. For my upcoming release I've built an installer
> using Wix. Everything seems to be working with the e
Not yet, for the following reasons:
a) quite a few times on this forum I read people recommending vcredist_x86.exe
over MSMs, claiming that MSMs are buggy and that vcredist_x86.exe does a lot
more than MSMs.
b) re-implementing the install to use MSMs, instead of an exe, may be a day or
two of w
As an aside, check if your old install and new install have the same ALLUSERS
setting. A per-machine install cannot upgrade a per-user install. Also if
you are looking at a log file, FindRelatedProducts is going to be more
interesting to look at since it's the once that looks at all the s
ComponentRef's & ComponentGroups are used in your Feature Tree not your
Directory Tree. If you want stuff to be in one place rather than another
simply move the Component Elements & everything inside them to where you
want them in your Directory Tree.
See -> http://www.tramontana.co.hu/wix/lesson1
>> I've double-checked and the Product ID and Upgrade Code both match
what was used in the previous versions
Only the UpgradeCode should match, Product ID should be new.
Neil
-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com]
Sent: 25 May 2010 07:56
To: wix-users@l
Prior to my upcoming release I used a VisualStudio deployment project to
create the installer. For my upcoming release I've built an installer
using Wix. Everything seems to be working with the exception of
installing the new version on top a previously installed version.
When I run my new insta
Thanks for the reply!
#2 does not seem viable. See:
http://stackoverflow.com/questions/2882963/xslt-adding-elements-on-the-s
ame-path
I edited the IL code of the WixUtilExtensions.dll. I'd happily just
recompile the WiX source code, but that requires 1GB of SDK and I'm
still in the process of dow
21 matches
Mail list logo
