I think you want to use VersionNT64, as VersionNT is 'undefined' on WS2008R2
or later.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372495(v=vs.85).aspx
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/install-only-on-server-2012-and-s
If you change the version (manually or via a auto increment), AND you change
the Product Code (which is what Product Id="*" does) then you will be able
to do the Major Upgrade. In my prior post I was responding to this comment:
"That is ok, but then when I rebuild the installer (without any chang
I'm sure there are many different ways to go at this. I was originally using
Wix 3.7 when I was using the WixExtededBA and the bal:autoversion. If I had
stayed with Wix 3.7 I would have used the source code at
http://wixextba.codeplex.com/ to create a wix extension and modify the auto
version alg
I have seen the response to this issue previously in this list, but basically
IIRC the version needs to be available at compile time. The binder writes a
bind variable after the linker completes, so that information is not
available when it is needed.
Get the Wix source download and look at WixBu
Originally I created a bundle (with Wix 3.7 and the WixExtendedBA) which I
later converted to use Wix 3.8 and the BAFunctions. I also compiled a debug
version of Wix 3.8 which my project links too. By setting a break point in
the BAFunction.DLL I can step into the Wix 3.8 burn engine code and see
Open the app.exe in a text editor and search for the 'manifest' (or use a
manifest viewing tool), generally close to the end of the PE file. The
embedded manifest should declare any SxS dependencies. When the windows
loader cannot find one of the SxS assemblies declared in the embedded
manifest i
You might find catest.dll a helpful tool in this situation.
http://blogs.msdn.com/b/astebner/archive/2005/03/07/388739.aspx?Redirected=true
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Execution-order-issue-tp7588998p7589366.html
Sent from the w
I spent some time working on this issue also. I focused on my wixlib project
first, then the msi project, and then the bundle project, tracking down the
various reasons as to why I could not do an incremental build. I resolved
the problems in each level of building before trying to solve the prob
I have a MBA which I modeled after the Wix installer code. I am trying to
add localization to it. I did a lot of reading on different approaches and
then installed NuGit and WPFLocalizationExtension.
http://wpflocalizeextension.codeplex.com/
I have this implemented like the sample that is at tha
Look at WixBA.cs line 147 and it (I think) does what you are wanting to do
after the install in the mba right before the BA exists.
this.PostTelemetry();
this.Engine.Quit(WixBA.Model.Result);
You would probably want to change the 'Telemetry' code to create a http post
that
There have been problems with the wixtoolset.org site. There was a hardware
crash a few weeks ago and it has been up and down. I would retry the wix
setup (which hits the wixtoolset.org site) again from time to time.
--
View this message in context:
http://windows-installer-xml-wix-toolset.6
Yes I also observed a few weeks ago when there were web site issues that the
3.7 installer would not run but the 3,8 would.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-I-find-the-reason-WiX-install-fails-tp7589584p7589639.html
Sent from
For MajorUpgrade behavior you must change both the Product ID and the
version. The UpgradeCode should remain unchanged. Also the version of the
MSI must change in the first three quad-dots. The version of the bundle can
be changed in any part of the version string.
http://wixtoolset.org/documen
I have a MBA which I am trying to localize. The MBA is structured like WixBA
in the Wix source. The MBA has been functional until I tried to add
localization. I installed the WPFLocalizationExtension and followed samples
from that site (https://wpflocalizeextension.codeplex.com/). I am having a
It sounds like, rather than deleting ARP entries or using MSP, that you need
to use the MajorUpgrade element and set the scheduling so that
RemoveExistingProducts is scheduled after the install of the new version, to
preserve user data. but it would be wise to look at this blog.
http://www.joyofse
wix37.exe /quiet
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix37-exe-unattended-installation-tp7589794p7589830.html
Sent from the wix-users mailing list archive at Nabble.com.
-
The CHM, the Wix tutorial, and searching this list, cover this subject.
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html
http://wix.tramontana.co.hu/
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multilanguage-install-td6161
If I understand the issue, I would go to each of the two project files
(Prod.*proj and TEST.*proj), right click on each file and select 'Unload',
then right click and select Edit Prod.wixproj (or TEST.wixproj). Then
compare the working to the non-working file. It sounds like your OutputName
eleme
This is a general question that I have run into several times. I understand
how to author an element like ComponentGroup as a child of a Fragment, and
then reference that fragment using ComponentGroupRef, as one example.
However I came across several elements that do not have a corresponding
Xxxx
Thanks for the explanation.
Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-reference-elements-in-a-Fragment-which-do-not-have-a-XxxxRef-construct-tp7590454p7590462.html
Sent from the wix-users mailing list archive at Nabble.com.
Tom;
No I did not try that. I saw the bootstrapperApplicationData="yes"
attribute. I was not sure why it was there or how I could take advantage of
it.
I appreciate Rob's explanation which made sense. My goal was to create a
WixExtension and do a data driven CA similar to the Difx extension in
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:
or something like this:
Maybe this answers your question:
http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-avoid-bundle-registration-as-installed-tp7590928p7590943.html
Sent from the wix-users mailing list arc
I do not know too much about this, but the code that was posted has the * for
'site 2' but not for 'site 1'. Is that a typo in the code?
>
>
>
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-7-iis-WebAddress-IP-works-but-generate
Sorry, please ignore my last post.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-7-iis-WebAddress-IP-works-but-generates-different-config-entries-tp7590938p7590968.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Generally yes, although you might not specify all of those attributes. Each
MSI needs some information instructing it how to process upgrades, which is
independent of how the MSI is launched, as part of a bundle chain or
directly.
--
View this message in context:
http://windows-installer-xml-w
I do not know the answer to your question directly. But I think I would try
something like the following, assuming that I was looking for a particular
version of java:
Do something like this:
ROOTDIR, can be changed by the user, and the subfolders will always be
appended. MyProductDir is not public so it cannot be changed externally.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabb
I just noticed that:
http://timestamp.comodoca.com/rfc3161
is returning:
000.0% #Bad request format or system error.
I do not know if this is related to your issue.
Using /t "http://timestamp.comodoca.com/authenticode";
seems to work for me.
--
View this message in context:
http://wi
I think the behavior could be implemented easily in WixStdBA using a BA
Function (in Wix 3.8 or in Wix 3.7 with WixExtendedBA). I went down that
route before I, for other reasons, decided to implement a mba. I actually
prefer the wixStdBA and BA Functions, but the business wants XAML in a mba.
h
Yes I understand the difference between /t and /tr. They are two different
methods of getting the time stamp which means that comodoca (and each of the
other time stamp vendors) actually have two timestamp servers (authenticode
and rfc3161). I was just pointing out that for me when I tested it a
>>The service runs under a user who is in the local administrators group. The
BurnBasedSetupKit.exe could very well be invoked by the service when the
machine is running but there is no user logged in. [Note: When the
BurnBasedSetupKit.exe kit is invoked interactively, everything works fine.]
I k
That is very interesting. Thanks for the details. Code running in a service
context would typically call LoadUserProfile prior to trying to access the
user areas of the registry. The notes on this function provides more
details.
Another area where I would expect issues is related to the fact th
I don't mean to add any confusion to this thread, but I am curious. If
keypath="no" in the above code, what is the keypath in this situation?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-a-registry-key-to-HKLM-tp7591371p7591443.html
Sent
Aside from all the other good points which folks have made, if there was some
reason to do the following:
'/k "[INSTALLDIR]"/myprogram.exe'
Is the second double quote above in the wrong place, and should be moved to
the end of the path?
'/k "[INSTALLDIR]/myprogram.exe"'
--
View this message in
I think there are several factors to the issue being observed:
1) the PrintUI /dd (delete driver) command does not remove the driver, but
in quiet mode 'succeeds', IF there are any 'printers' objects which depend
on the driver. They need to be removed first. I use the /dl command after
I enumerat
FYI Devcon.exe is not redistributable. You might want to consider a
different approach.
http://support.microsoft.com/kb/311272/en-US
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Invoking-batch-file-tp7591572p7591577.html
Sent from the wix-user
The way I do it is to create each MSI ('setup' project in VS) without
defining a UI. I just focus on getting the functionality of each MSI
working. Then create a 'bootstrapper' project (or bundle) and add the
MsiPackage element for each MSI into the chain.
--
View this message in context:
h
Niel provides the infor in his blog.
http://neilsleightholm.blogspot.com/2012/05/wix-burn-tipstricks.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-NET-3-5-in-Burn-tp7591622p7591696.html
Sent from the wix-users mailing list archive a
As Tom indicated I added custom tables with BootstrapperApplicationData="yes"
and then the following link was helpful in deserializing the data.
http://stackoverflow.com/questions/12846421/getting-display-name-from-packageid
--
View this message in context:
http://windows-installer-xml-wix-tool
I implemented the approach to passing data from my bundle via the
BootstrapperApplicationData.xml to the mba some time ago. But today I came
across a much easier approach. I commented out the custom table and the
BootsrapperApplicationData class (which I had modified from the sample code
in the l
>>>Wish someone would help improve the WiX toolset instead of everyone doing
workarounds.
I am very interested in doing that, however aside from some sickness in the
family that took me offline last week, I am still struggling with
understanding the git push - pull process. I hear that the way I
This does not answer your question about WixBundleOriginalSource, but the
approach that I took was to modify the project file directly, creating a
MSBuild task, which takes seed information generated elsewhere in my build
process and writes a wxi file (to generate the version string specified in
my
Can you post relevant sections of code and verbose logs (from your %temp%
folder)?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-web-setup-Directory-name-tp7591768p7591823.html
Sent from the wix-users mailing list archive at Nabble.com.
Sorry I see that you did post code in another thread.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-web-setup-Directory-name-tp7591768p7591824.html
Sent from the wix-users mailing list archive at Nabble.com.
-
If you are trying to do a major upgrade, then the new setup needs to have
both a different ProductCode and a different version (in the first three
positions).
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-entries-in-ARP-while-upgrading-a
I suspect what you need to do is to localize your setup for polish so that
you have a english wxl and a polish wxl file (or the language of concern).
And also specify the multiple cultures in your project file. If you don't
really want to translate the dialogs then use english strings in the poli
I am not sure if what I suggested would solve your problem, but what I
noticed from your earlier message, when you use that polish string, you had
an error which indicated that the characters were not in the code table.
The polish wxl file would specify the correct code table.
--
View this mess
I have noticed this behavior with other command line tools like when Rundll32
printui.dll,PrintUIEntry. I just thought it was common behavior unrelated
to wix.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Fx40Client-installation-error-message-t
I am still learning this stuff myself, so I may misunderstand the problem,
but in your MBA, typically in PlanComplete you would have code which calls
this.root.PreApplyState = this.root.State;
this.root.State = InstallationState.Applying;
myMmbaClass.Model.Engine.Ap
The link provided by eyoung100 was helpful to me in packaging some printer
drivers, using a single MSI project with different build configurations to
produce x86 and x64 packages. The bundle then includes both packages and
installs the one which is appropriate for the architecture of the target
sy
Pre-vista OS the name of the account for sid S-1-5-18 was "NT
AUTHORITY\SYSTEM"
http://support.microsoft.com/kb/163846
Post-XP/2003 (and possibly on XP/2003 with a SP level, I do not recall,) the
name of the same S-1-5-18 sid "\Local System"
http://support.microsoft.com/kb/243330
When working dir
I above been reading up on the dism api, and while I have not gotten very
far, one thing that confuses me is the requirement stated in the following
link of:
"The binary files for your customized solutions must be saved in the same
directory as the DISM binaries installed by the Windows ADK. For ex
To use any of the WiX extensions you need to do two things.
1) Add the schema statement as you originally had.
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";
xmlns:bal="h
I'm sorry I misread part of your post. I do not know about the schema issues
if you are on a closed network, how that should be handled. Maybe someone
else can comment on that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Visual-Studio-2012-Do
Is this what you are looking for?
#if defined _WIN64
#define PLATFORM_DECORATION(f) f ## L"_64"
#elif defined ARM
#define PLATFORM_DECORATION(f) f ## L"_ARM"
#else
#define PLATFORM_DECORATION(f) f
#endif
from src\ext\ca\inc\caSuffix.h
--
View this message in context:
http://windows-installer-x
I do not have the ADK or the path either. And the API docs talk about
creating a 'application' which will modify /online images. Here is a
sample:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh824804.aspx
I am preparing a CA to test pieces of this code relating to the query of a
feat
The WixExtension 'references' should be added to the Wix based 'Projects'
which are using the particular extension. So your Bundle 'project' should
have a 'reference' collection and you will almost certianly need to add a
reference to the WixBalExtension.
If you are using code for the WixFirewall
CreateFolder in the chm?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-instalers-not-installing-empty-directories-on-target-computer-tp7592032p7592067.html
Sent from the wix-users mailing list archive at Nabble.com.
-
The privilege SE_CREATE_SYMBOLIC_LINK_NAME is required.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa363866(v=vs.85).aspx
The following link has some ideas on how to grant the privledge and I think
there are some other approaches which could be implemented in a CA with
win32 calls, b
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html
In the above link (or in your chm file) there is an example of localizing
the Name attribute. (It happens to be in a MSI Product element but also
could be implemented in a Bundle element.)
Use MsiPackage/@Name or ExePackage/@Name and specify the folder tree.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Create-Subfolder-for-each-Element-in-Bootstrapper-Chain-tp7592152p7592157.html
Sent from the wix-users mailing list archive at N
Yes, that would be my feeling as well. However it looks like dismapi.dll is
included in Windows 8 or later. But for pre-Windows 8, it seems that the
ADK must be installed, which won't fly here either. I'm still
experimenting.
--
View this message in context:
http://windows-installer-xml-w
Sorry, caSuffix.wxi is at src\ext\ca\inc\ in the source tree. It contains
the following:
http://schemas.microsoft.com/wix/2006/wi";>
--
View this message i
The code listed in this thread is for a (bootstrapper) bundle.exe project and
not for MSI project, so if you renamed your bundle project's output file to
*.msi, I would expect the error that you indicated.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabbl
How did you get the source files? When I tried to use the source zip
download I had similar problems and was told that it is intended only for
reference and not fro actually building the code. The source is up on the
codeplex site.
--
View this message in context:
http://windows-installer-xml
There are other similar reports on the internet which are not related to Wix,
so the root problem is probably more along the lines that Christopher
suggested. When you recompiled did you consider using
MsiPackage/@SuppressSignatureVerification?
--
View this message in context:
http://windows-i
The CP210x driver is a onn-msi difx API/setup API application. Silicon Labs
has application notes which explain how to install these drivers in a
background (quiet) thread (AN335 i think). I install this driver, in the
background, in setups I created with a different tool, before I started
using
I am probably over looking something simple, but in a Wix Custom Table Row
element, how do I indicate that I want the data in that row (to be passed
to a CA) to be a component's attributes?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Compone
I understand that component attributes are bit flags. I want to test for the
64 bit flag in my immediate CA, which schedules a deferred CA, so that I
know whether the CA is running on a x64 architecture. There are several
examples in the source code of testing the component attribute flag in
secu
I am not sure, but I think a bafunction.dll with WixStdBA (3.8) could be used
to change the behavior of UI controls. I started down that route based on
information at http://wixextba.codeplex.com/. Then several months ago I
also decided to create a mba, so my memory about bafunctions may be getti
I do not have experience with WFP callout drivers, however I observe that
msdn indicates that they are non-PNP drivers. The DifxApp by default
installs PNP drivers. I assume that the basic process of installing the
driver by right-clicking the INF is successful. If setting the legacy flag
for Di
Thanks for the ideas. I will study them.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-Attributes-tp7592263p7592319.html
Sent from the wix-users mailing list archive at Nabble.com.
-
While I am not doing what you are doing, and I have a lot to learn about
wix/msi, when I tried to install several different pnp printer drivers, each
of which install using non-msi setup by calling the Difx API (or by using my
SetupAPI app), I could not get them to install using DifxApp in wix. I
I have not worked with callout drivers, but your comment that the INF does
not have a SourceDisksName section and yet you get a file not found error
implies that the Class setup application processing the INF file is trying
to do a file copy. In looking on msdn at "INF Files for Callout Drivers" i
FYI The following thread also discussed 'confusion' on testing for a empty
string in Burn conditions.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ExePackage-DetectCondition-syntax-td7588157.html#a7588171
--
View this message in context:
http://windows-installer-xml-wix-toolset
I want to thank Bob and Phil for the interaction and suggestions, and the Wix
contributors for the Wca library. I reevaluated what I was trying to do and
found that by calling WcaIsPropertySet("System64Folder") I was able to
detect the platform (x64 or x86) from within my CA. I had originally tr
Another observation that I wondered is, 'Is the
"C:\Temp\wxs\IRAdmin.connections.Config.wxs" on the remote server where
candle.exe is being launched?'
Mapped drives only exist in the context of a particular user. So I find
that when folks try to use windows services (which we deploy) with mapped
I have not used C# CAs or DTF, but I launch a third-party package which has a
CA that must have a dependency on .Net 2.0. If .Net 2.0 (or NetFx3) is not
installed on the target system when this third-party is launched, I get the
same error that you quoted. I added code to my bundle to make sure t
I am trying to learn WiX (and MSI, with a background in non-MSI setup
development). I hope to contribute to the WiX community at some point, but
for now I am experimenting with heat.exe and dark.exe as I learn.
There are various examples of using heat.exe which have command line
switches that ar
Well Bob is correct those switches are documented. I am not sure now what
document I was looking at yesterday which seemed to be missing this
information. I have 3.7.1224 installed on several systems as I experiment
and learn the details and I thought I had checked the CHM carefully prior to
post
If you know basic information about the child process (such as a window
title), then after your setup launches the exe package, and the package
returns successfully, launch a tool which calls FindProcess (or equivalent)
and get the PID, and then wait on that PID until the child process
terminates,
I came across this broken link in the help, both on the web and in the
3.7.1224 chm, on the page titled "Code Pages" the link named 'localization
files'.
I tried to go to the bugs link on SourceForge but did not understand how to
report this bug. Sorry. (I want to get up to speed and help out on
Using Wix 3.7.1224 I created a setup and localized it. I can build it in
each language based on the string(s) that are entered into the Project
properties 'Cultures to Build' text entry. When the 'Release' configuration
is built, light.exe is called multiple times, for each culture, appending
th
I have been studying the Setup source code for WiX 3.7 and working on the
payload packages for a bundle which will do web downloads. However the
payload will not be hosted on a web site that exists when the package is
created. Rather the bundle package and all related files will be included
in a
That is the challenge I am trying to understand.
The setup which creates the web site could write URL information to a file
that in with the bundle exe, and maybe generate a self-extracting exe. Then
the user might download the two files or something along that line, and the
bundle exe would then
Or the BA is downloaded and launched presenting a dialog to a user (or a
command line property) allowing the user to specify a URL to look for the
payloads. Is this possible, I assume with a custom BA?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.c
Thanks very much for the information and the various ideas. Knowing that it
is possible to change the URL at run time is a big help. I will work
resolving the 'known unknowns' issue and may be able to take advantage of
another feature of our product to discover the web site. I am having a lot
of
On a 64 bit machine the key is at:
HKLM\SOFTWARE\Wow6432Node\Microsoft\DevDiv\vs\Servicing\11.0
So I wonder if when you indicated that it succeeded if it actually found the
key under the 32 bit registry node and you checked under the 64 bit node
which does not have the relative path of .\vs\Servi
I do not know, but what is the requestedExecutionLevel in the manifest for
'MyExe'?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAction-elevated-not-working-tp7592486p7592489.html
Sent from the wix-users mailing list archive at Nabble.com.
As a child to your BootstrapperApplicationRef elelment, use a Payload element
(or a PayloadGroup or PayloadGroupRef element) to define the depend files
that need to be cached and extracted to the temp folder with your mba. The
name attribute defines the subfolder tree relative to where your mba is
Take a look at this thread:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installer-upgrade-does-not-work-td7589150.html#a7589177
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Read-a-value-from-a-text-file-and-use-it-in-WIX-s
Take a look at this thread:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installer-upgrade-does-not-work-td7589150.html#a7589177
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Set-Product-version-in-Product-wxs-file-tp7592487
Looking at the issue from a different perspective, if you refference anything
that is in a fragment, then everything in the fragment is added to the
package. Many elements, like Component (for example) have a corresponding
XxxxRef element, which you use to reference the element in another fragment
I am trying to create a Compiler Extension. I started by studying the
WixContrib project along with various extensions in the Wix source, like the
Gaming extension. I had previously created my CA and wixlib projects using
a custom defined table in the wsx, and now I have the WixExtension working,
The Compiler Extension code is basically from Wix-Contrib with modifications
that I added by studying the wix tools. (I added an attempt to get the
InnerText of an element and use it as a condition. That change is not
working yet. But in these examples I do not have any InnerText and
'condition'
Yes Jacob you are correct. Thanks to both of you for poking me toward the
correct direction. I really appreciate the good examples in the source
code that you folks have put together and I am trying to get up to speed so
that I can contribute back. Thanks.
--
View this message in context:
h
I am getting the same error. In my case I have several projects, of
different architectures, in the same solution. I only see the problem when
I try to build the projects using a batch script and msbuild to build each
project. The C++ CA project can be built as either Win32 or x64. The
wixlib p
101 - 200 of 790 matches
Mail list logo
