from: http://msdn.microsoft.com/library/windows/desktop/hh825838.aspx
“You can develop applications by using the DISM API on any computer where you
have installed the Windows® Assessment and Deployment Kit (Windows ADK).”
So, I interpret that as saying that you can’t statically link the DISM
You always control the registry key? Do it like the property remember pattern.
Blair
From: Sean Farrow
Sent: Friday, January 24, 2014 8:23 AM
To: General discussion for Windows Installer XML toolset.
Hi all,
I'm in the process of refactoring an installer I wrote a while
Certainly it is possible using a custom BA from a bundle. Somewhat less so from
an MSI. One big advantage of the bundle, however, is that the entire set of
packages can be divided up between some arbitrary set of MSIs abstracted away
from the end user (in fact, the most logical would be to have
Personally I think it should have been implemented that way but it wasn’t.
Blair
From: Graham Allwood
Sent: Thursday, January 23, 2014 10:34 PM
To: General discussion for Windows Installer XML toolset.
Thanks Blair.
That did the trick.
I was trying to use element in t
I believe that is only true for versioned files, although I may be mistaken.
In this particular case (properly versioned .Net 3.5 executables) they were
unchanged and should not have been replaced according to my, and your,
understanding of the rules. Despite that, Windows Installer was killing
th
I believe Condition element only needs VersionNT64 to differentiate at runtime.
In 32-bit build, reference only Id_x86. In 64-bit build, reference both Id_x86
and Id_x64.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: Monday, January 27, 2014 3:00 PM
To: wix-use
1. $() are resolved and preprocessing, !() are resolved and binding, and #() is
resolved at runtime.
2. The latter.
-Original Message-
From: Jun Yin [mailto:jun...@microsoft.com]
Sent: Monday, January 27, 2014 5:04 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] !(loc.XXX) o
2014-01-27 Walter Dexter :
> Got it!
>
> I haven't worked out all the details but changing the MSIRMSHUTDOWN
> property to "0" makes it do what I wanted. Note that in this case the .exe
> files that I want to keep running aren't actually being modified. Our
> deployment folks just don't like to dea
In WIX, localization strings are referenced using the !(loc.xxx) syntax, and
defined in WXL files:
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html
However, I find to enable localization strings in a bundle using WIX standard
bootstrapper
Hi,
I didn't get much traction on my question or at least my last question...
ALL of my MSI use this format in a variable.wxi files I have:
Should I use:
and NOT ??
What about my wixlib where I have 2 files that have a 32 bit version and
To learn what features are being installed I try to examine ADDLOCAL which is a
standard parameter that can be passed to MSI. I use the following line in my
WiX xml to do that:
Then, inside InstallExecuteSequence element I am scheduling custom action which
uses my local FEATURELIST property.
With MSIINSTALLPERUSER=1 on Windows 7 and above the ProgramFilesFolder
location gets automatically rerouted to LocalAppDataFolder if running a
per-User install.
This MSDN article shows where all the folder locations point to in
per-machine vs. per-user installs:
http://msdn.microsoft.com/en-us/lib
I am trapped in a similar issue.
My custom bootstrapper is based on Net 4.0. As a prereq I want to install
Net 4.5 which does work, but since my app itself uses Net 4.0 I ran into the
restart-issue which is not usable for me.
If I got you right, Nicholas, setting my bootstrapper to 4.5 should for
If you're talking about this error from "candle," or a similar one from
"light":
error CNDL0200 : The Component element contains an unhandled extension
element 'Util:blahblahblah'. Please ensure that the extension for elements
in the 'http://schemas.microsoft.com/wix/UtilExtension' namespace has
Hello All,
I can do what I need to do using a custom action, but I am hesitating on
that route wandering if WIX has a built in mechanism for this.
Here is my situation:
On server 2008 I want to verify if the SSDP (Windows Service already
installer by the OS, not my own) is installed and re
No. That's a per-machine location.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Monday, January 27, 2014 7:54 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
So per users can inst
Try this Format:
http://schemas.microsoft.com/wix/UtilExtension";
User="Administrator"
ServiceChangeConfig="yes"
ServiceEnumerateDependents="yes"
ChangePermission="yes"
ServiceInterrogate="yes"
ServicePauseConti
Any idea how to get around the reference error to UtilExtension? Or, is there
a new/different way of setting a service failure action?
The ServiceInstall element contains an unhandled extension element
'util:ServiceConfig'. Please ensure that the extension for elements in the
'http://
Got it!
I haven't worked out all the details but changing the MSIRMSHUTDOWN
property to "0" makes it do what I wanted. Note that in this case the .exe
files that I want to keep running aren't actually being modified. Our
deployment folks just don't like to deal with distribution of patches;
they'd
So per users can installer to C:\Program Files\ ?
-Original Message-
From: Sascha Sertel [mailto:sascha.ser...@gmail.com]
Sent: January-24-14 6:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
No I did not
Blair/Rob
is this statement correct:
So are you saying I should use:
and NOT
What about my wixlib where I have 2 files that have a 32 bit version and a
64 bit version what is the proper way to say
32 bit file install on a 32 bit OS and 64 bit file install on a 64 bit OS
AND 32 bit file can
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.)
Hi,
I’m evaluating Wix and I hope someone can give me some clarification on a
question I have.
I have an installer configured using WixUI_Advanced but I want to extend it by
adding a new step to the middle of the setup process.
The idea is to have a new screen with two buttons, one of them
Thanks a lot for the useful reply and solution. I was in search of this... Be
happy forever..
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/customizing-burn-prerequisite-boostrapper-image-in-theme-tp7205852p7592105.html
Sent from the wix-users m
Hi guys,
I meet a problem when create a Wix bootstrapper project.
I need to localize the product name shown in the windows system uninstall
list. As I know, the name is decided by the Name attribute in Bundle element
in Bundle.wxs
Here is my bootstrapper project Bundle.wxs
http://schemas.micr
Hi guys,
I meet a problem when create a Wix bootstrapper project.
I need to localize the product name shown in the windows system uninstall
list. As I know, the name is decided by the Name attribute in Bundle element
in Bundle.wxs
Here is my bootstrapper project Bundle.wxs
http://schemas.micr
27 matches
Mail list logo
