Question is if these machines don't have internet access, why is keeping them
up to date an issue?
If the answer is they have network access but not internet access then why not
just set up a machine to run WSUS for you ->
http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx It's pract
ever, in my specific case, I
get:
Condition 'Netfx4FullVersion AND (NOT VersionNT64 OR Netfx4x64FullVersion)'
evaluates to false.
Maybe the .NET Framework 4 Extended is not considered as a full version. I
don't know where I can find an exhaustive list of these conditions.
Pally
You should only need a check for the .NET 4.0 Client Profile. If the full .NET
4.0 is installed it should also return success since the full package upgrades
the Client Profile.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
I'd assume the full .NET 4.0 puts both keys into the registry for this type of
issue.
Have you actually tested this yet?
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Env
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012.aspx
http://msdn.microsoft.com/en-us/library/aa372495.aspx
http://msdn.microsoft.com/en-us/library/aa372497.aspx
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**
http://wixtoolset.org/documentation/manual/v3/wixui/dialog_reference/wixui_installdir.html
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Re
Rob M. wrote some articles on the subject a few years ago:
http://robmensching.com/blog/posts/2007/8/3/zen-and-the-art-of-custom-actions
http://robmensching.com/blog/posts/2007/8/10/zataoca-classes-of-custom-actions
http://robmensching.com/blog/posts/2007/8/17/zataoca-custom-actions-are-generally-
WiX doesn't have any such thing. Some WIX extensions such as NetFx have some
defined which are listed in their respective schemas but there's nothing in
'vanilla' WiX like what you're describing.
Windows Installer on the other hand has a whole bunch of properties any MSI can
use (such as the RE
You are correct, it's the web installer.
The full redistributable is named dotNetFx40_Full_x86_x64.exe & is 48.1 MB in
size.
Looking at the source for the WiX installer, in \src\Setup\Bundle\Bundle.wxs it
contains the following:
So /layout will always pull the web install
It'd be nice if there was some easy way to leverage the "redist" directory in
your own Packages without a massive effort.
Setting "Name" attribute of MsiPackage only works if you have the package
embedded in your bundle. It completely ignores it in the case of a DownloadUrl
e.g.
http://do
Your hunch is correct.
There are 2 main reasons for the use of Burn as far as I know.
1 - "dogfooding"
2 - WiX installs a bunch of packages now instead of one monolithic package. If
you look in \src\Setup\Bundle\Bundle.wxs you'll see it chains .NET 4.0 full,
ProjectAggregator.msi if you have Vi
ould be respected and it should
place that file in the redist\mpi_x64.msi folder relative to the output
bundle.exe.
On Fri, Oct 18, 2013 at 7:02 AM, Pally Sandher wrote:
> It'd be nice if there was some easy way to leverage the "redist" directory
> in your own Packa
This is covered on the "insignia" page in the docs ->
http://wixtoolset.org/documentation/manual/v3/overview/insignia.html
You'll need to manually add those Elements to the relevant .wixproj as last
time I checked there were no fields for them in the project view in Visual
Studio.
Palbinder Sa
arget would be
executed prior to building the msi.
On Tue, Oct 22, 2013 at 6:03 AM, Pally Sandher wrote:
> This is covered on the "insignia" page in the docs ->
> http://wixtoolset.org/documentation/manual/v3/overview/insignia.html
>
> You'll need to manually add
You don't need the 2nd entry in the InstallUISequence you pasted below. Remove
it as it's likely giving you false results.
The next button on your "GetRackspaceCreds" dialog is being mapped to something
called "PrepareDlg" which doesn't exist in your authoring. However that's a
problem you'll h
You can't. I feature requested this back in June 2012 ->
http://wixtoolset.org/issues/3659/
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited.
TARGETDIR is the root of your Directory Tree. It essentially represents
the root of the drive you're installing to (as in C: or D: or E: etc).
You shouldn't be trying to use TARGETDIR to install your product in a
standard installation. This is covered in the tutorial (see
http://www.tramontana.co
owing --
I would like to set the INSTALLLOCATION directory name dynamically at
install time.
Thanks,
Gregg
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, February 15,
1 - What I would like is for the extension installers to refuse being
installed if the main application isn't installed.
This is easily supported using LaunchConditions in an MSI. Simply use
something like a RegistrySearch to populate a property with something
your main product installs then use t
Also i read that max size of msi is 2Gb, so i can not embed all files
into single msi.
The Cabinet format has a max limit of 2 GB. That doesn't mean you can't
use multiple Media elements to compress your files into multiple cabs &
embed them into your MSI if you wish. I wouldn't recommend embeddin
You can set the minimum version of Windows Installer your package
supports using the InstallerVersion attribute of the Package Element ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm
Windows Installer v2.0, v3.1 & v4.5 are available as redistributables
from Microsoft which you can bo
http://wix.sourceforge.net/manual-wix3/wix_xsd_customaction.htm
See the "Impersonate" Attribute.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Li
MSIZap doesn't fix anything. All it does is remove the Windows Installer
entries so your installer doesn't show up in Add/Remove Programs.
Everything the installer did to your system is still there (files,
registry entries etc) & I've seen more than one occasion where a user
has screwed their syste
Virtual PC has been freely downloadable from Microsoft since 2006 as has
VMWare Server & I think VirtualBox may have been freely downloadable for
longer.
Bob A. wrote a blog post on using virtualization to test installation 3+
years ago ->
http://www.joyofsetup.com/2007/09/24/test-your-setups-virtu
Here is the best place for WiX help. The actual WiX dev's such as Rob M,
Bob A et al reply on a regular basis if other "learned" members haven't
responded to a query. We also have people like Phil Wilson whom I
believe (although he's never confirmed) wrote "The definitive guide to
Windows Installer
You need to use either [#fileid] for a long path or [!fileid] for a
short path. Since it's the same MSI there should be no need to mess
about with Properties just change the TargetProperty to reference the
File Id of the executable.
The ICE69 error is because there's no File with Id of "MAINEXEC"
Windows Installer should be requesting elevation when it tries to
install your MSI. Have you set InstallPrivileges="elevated" in your
Package Element? Is your MSI per-user or per-machine (InstallScope
attribute of Package Element sets that). I've only used per-machine
packages so if you're trying t
Use
See http://wix.sourceforge.net/manual-wix3/check_for_dotnet.htm &
http://wix.sourceforge.net/manual-wix3/wixnetfxextension.htm
You'll also need to add a reference to the WixNetfxExtension.dll in your
project or pass it to light.exe using the -ext switch to use those
properties.
Palb
y. Use Heat instead,
and if it does happen to be a per-user install then the registration
goes into HKCU for the installing user.
Phil Wilson
-----Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, March 15, 2011 10:13 AM
To: General discussion for Windows
http://msdn.microsoft.com/en-us/library/aa370852.aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Depends on what you're setting this "WIX_ACCOUNT_EVERYONE" Property to &
what you're actually trying to achieve.
Assuming you're trying to set permissions for the "Everyone" group &
you've arbitrarily picked the property WIX_ACCOUNT_EVERYONE out of the
air to mean that without setting it to anythi
If you want to do "what is right" you could start by not using
self-registration.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Register
You can't without writing your own External/Embedded UI. That control is
a SelectionTree http://msdn.microsoft.com/en-us/library/aa371604.aspx
which doesn't offer the customization you want.
Also attachments don't work on this list (probably by design) so either
paste stuff into your message or pr
Looks like you're missing the point here Tim. It's Windows Installer which
modifies the path when you're installing a 32-bit package. WiX has nothing to
do with it. Check a verbose log if you don't believe us & you'll see something
called WIN64DUALFOLDERS modifying your path for you.
As David s
You can also use WiXEdit (http://sourceforge.net/projects/wixedit/) to do that
but you'll need to use version 0.7.2.3 or older as they changed it to work as
per heat.exe from 0.7.3 onwards.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://
Don't install on Windows 7?
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix
dblock of dotnetinstaller fame created a bunch of standard properties in a WiX
include which you may find useful for this. See
http://code.dblock.org/ShowPost.aspx?id=101
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**De
You can hide the shield icon on the install button if you so wish but a
per-machine package is still going to prompt Windows Installer to
request elevation once you click that button.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesv
I'm guessing it's probably because there's no reference to the Fragment
so it's not including it. Try adding a ComponentGroupRef for FooFiles
under your FOO Directory or something else which links the Fragment to
your Module Element. That should sort it out.
Palbinder Sandher
Software Deployment
identify the link between the 2 files without having to add the
reference.
Or am I thinking the wrong way?
Thanks in advance,
Stel
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: 30 March 2011 16:02
> To: General discussion for Windows Insta
http://wix.sourceforge.net/releases/ work fine for me as do
http://wix.codeplex.com/releases/view/60102
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Soluti
MSDN appears to say you can't. See
http://msdn.microsoft.com/en-gb/library/aa368608.aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Re
http://wix.sourceforge.net/manual-wix3/heat.htm
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Regis
How about not using self-reg & harvesting the registration info from
richtx32.ocx using heat.exe?
That works perfectly fine for me on all OS from XP onwards.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulat
If you want to block installation of x86 MSI's on x64 platforms simply use a
LaunchCondition with "NOT VersionNT64" in the x86 package. Anything else is
pointlessly overcomplicating things.
That bug you refer to is in Burn, not candle /light. Seeing as Burn doesn't
exist in WiX 3.0 I'm not surp
Swapna is using WiXEdit which is a GUI for creating .wxs files. See
http://wixedit.sourceforge.net/
WiXEdit (and WiX) have nothing to do with getting a verbose log of your
installation. Your package is installed by Windows Installer, WiX simply makes
it easier for you to create the package in
Is your ProductCode different between packages? I suspect not as you've got it
explicitly defined it in your code below & the error you are seeing is commonly
caused by this. Try using Product@Id="*" to auto generate your ProductCode
every time you build.
Also try updating Package@InstallerVers
Take a look at SharpSetup -> http://sharpsetup.eu/ . It may help point you in
the right direction.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions
http://www.tramontana.co.hu/wix/lesson3.php#3.2
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Regist
Peter Shirtcliffe already pointed you at the tutorial page
(http://www.tramontana.co.hu/wix/lesson1.php#1.2) which explains this in
response to your earlier message. I suggest reading it (and the rest of the
tutorial) as you appear to be struggling with basic fundamentals of Windows
Installer p
" the installer doesn't need to know about the xml files or about COM
registration of the dlls"
Really? So what happens when the install fails & it has to rollback or the
super unlikely event that someone wants/needs to uninstall your application (or
you force an uninstall during a Major Upgra
Don't do anything which needs to access per-machine areas of the system &
you'll be fine =)
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited
We've upgraded our Salford Fortran compiler to version 6.0 & I'm now getting
the following warning for the run time DLL as it has no language specified in
its attributes:
warning LGHT1076: ICE60: The file SALFLIBC.DLL is not a Font, and its version
is not a companion file reference. It should
Re: [WiX-users] perUser vs perMachine and elevation (bestpractices?)
On Thu, Apr 7, 2011 at 12:18 PM, Pally Sandher wrote:
> Don't do anything which needs to access per-machine areas of the system &
> you'll be fine =)
I.e. tag my package as "perUser", and if that
The WiXUI ExitDialog already has support for this without needing all that
unnecessary code. See
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
Simply change the Value attribute in the WixShellExecTarget property in the
example to your URL.
Palbinder Sandher
Software Dep
http://lmgtfy.com/?q=REINSTALL+property
-Original Message-
From: Leo [mailto:dangle...@hotmail.com]
Sent: 16 April 2011 07:13
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] condition for feature being reinstalled or patch
Hi, what is the condition that cou
If you update to Windows Installer 4.5 is the same behaviour observed?
Why are you testing on Vista without any Service Packs installed anyway?
There's a reason why Microsoft issue service packs for operating systems, this
is one of them.
Palbinder Sandher
Software Deployment Engineer
T: +44 (
Yeah if OpenOffice use concurrent installations it must be totally safe
http://msdn.microsoft.com/en-us/library/aa368010.aspx
Stick with using the merge modules and/or a bootstrapper for the vcredist. If
you don't need to bootstrap any other pre-reqs the merge modules are the
easiest wa
The reason you see the AdvancedWelcomeEulaDlg a second time is because in
AdvancedWelcomeEulaDlg.wxs there is the following:
NOT
Installed
Hence it's showing up in the InstallUISequence.
What happens when you click Next on the WelcomeDlg is it does what you've set
tion necessary to get only one UAC prompt
If there exists a good bootstrapper for implementing it in a "chaining
way" I think to re-implement it that way.
Regards
Tobias
PS: I know this approach is somehow quick-and-dirty and not MSDN
compliant ... but it does a good job ...
2011/4/28
ough the
choices (so it was my error to try to use the AdvancedWelcomeEulaDlg in the
first place, but at least I learned something from you.)
Thanks again,
Dave
On Thu, Apr 28, 2011 at 4:39 AM, Pally Sandher wrote:
> The reason you see the AdvancedWelcomeEulaDlg a second time is becau
Firstly a verbose log would tell you exactly what the problem is.
Secondly run the following command msiexec /i setup.msi INSTALLPATH="C:\Cool"
SUBFOLDER="C:\Cool\Ice" and I suspect it'll work as you expect.
SUBFOLDER refers to a Property being used as a Directory Identifier. It still
needs to
http://msdn.microsoft.com/en-us/library/aa368010.aspx
Use a bootstrapper instead of trying to shoehorn a whole other install into a
custom action. It works perfectly fine for your product when delivered through
Steam.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +
Use a bootstrapper.
I've not said it this month as yet so I guess it was inevitable at this point.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions
If by "I have created a bootstrapper using WiX" you mean you're using Burn,
then check the bug tracker & report your issues if they're not already reported
as Burn is still in active development.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
h
How do you mean test exactly? If you only want to check the text & layout of
dialogs you can preview them using Orca or InstEd!
The recommended approach for installation testing is to use virtual machines ->
http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
In addition to the produ
It looks completely fine to me & should work.
I just tested
Which is fine & almost identical to your code.
The only thing I can think it could be is some formatting characters are
present in the Identifier but even that would show up in the error message. You
could try pastin
You can't use Votive to build patches as there's no "patch" project type (or
there wasn't last time I checked) which is why Visual Studio is erroring.
Post your patch.wxs & the commands you're running which give you that error as
the error & information you pasted is too vague to diagnose.
I've
Yes that's how patching works certainly using the patchwiz method which from
your other message is what you're attempting.
PatchWiz method creates a patch using a base package & an updated package. Only
what has been changed between the base package & updated package is included.
Note it's meth
Using WiXUI in WiX 3.5 it should go from WelcomeDlg directly to VerifyReadyDlg
when applying a patch. Have you customized the WiXUI or written your own UI?
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate +
Are the config files being included in the patch? Patchwiz log should tell you
what exactly what it is choosing to include.
If so it's overwriting them with what it thinks are newer files which is what I
suspect is the case as Windows Installer won't overwrite updated files with
older ones in m
code change to
have a difference. Features are all the same. Any other ideas?
I'm using 3.5.2519
-Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, 12 May 2011 11:02 p.m.
To: General discussion for Windows Installer XML toolset.
Subject: Re:
>From the manual page at
>http://wix.sourceforge.net/manual-wix3/wix_xsd_file.htm no it doesn't appear
>to do so, however without looking through the WiX v3.5 source or testing it by
>building a package it's not easy to be sure. If it doesn't do what you want,
>it would be a reasonable Feature
As repeated many times on this list, it's not possible with Windows Installer
therefore it's not possible with WiX.
Windows Installer requires MSI's to have a platform specified which is
generally either Intel for x86 platforms and either AMD64 or x64 for x64
platforms. x86 MSIs will install on
Make sure the machine you build your package on has that version of Visual
Studio installed & it will have the corresponding merge modules in the Common
Files area then just link them as usual.
Visual Studio installs the same version of merge modules as itself. It doesn't
keep a repository of pr
I'm curious as to why people encounter issues with this. I've never had to do
anything special for Windows Installer to do this automatically for our
packages. Unfortunately I have run across situations where upgrade or uninstall
of someone else's product prompts Windows Installer to request the
our 3rd-party tools. That's about the only
> reason.
>
> Given a particular .msm file, how does one "inspect" the file, to
> determine the version in particular?
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: We
Simply wrap the MergeRef's in a Feature then use a FeatureRef ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_featureref.htm
Don't worry about HTML e-mail, the list bot strips formatting & sends as
list mail as plain text.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
Create a copy of SetupTypeDlg.wxs, remove the Typical button from your
copy & replace all references to SetupTypeDlg in your copy of
WiXUI_Mondo with references to your modified SetupTypeDlg.
Neil Sleigtholm's blog article on this subject may help get you further
along with this ->
http://neilslei
I suspect the following manual page is what you're looking for ->
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
All of what you're trying to achieve sounds eminently possible using
Windows Installer. I'm not sure if non-MSI setup systems can even
support advertised installation using advertised shortcuts.
With regards to "putting the entire app into the users profile area if
on Vista+[1], or program files f
unchFile' FileKey='FoobarEXE' ExeCommand=''
Return='asyncNoWait' />
but I don't know how.
Is this LaunchFile CA is windows installer predefined CA?
thanks,
William L.
On Mon, May 23, 2011 at 5:34 PM, Pally Sandher
wrote:
> I suspect the following manual
1456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Chris [mailto:h48c...@werritech.com]
Sent: 23 May 2011 11:57
To: General discussion for Windows Installer XML toolset.
Cc: Pally Sandher
Subject: Re: [WiX-user
False to the best of my knowledge. The Visual C++ merge modules put an
Uninstall Custom Action (SxsUninstallCA) after InstallFinalize & the WiX
tutorial uses a Type 2 Custom Action after InstallFinalize to show how
to launch an installed executable.
Palbinder Sandher
Software Deployment Engineer
Can you send a link for the custom action in the Wix tutorial?
Thanks.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, May 23, 2011 5:33 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Elevated Custom Actions
Easy solution would be to have base-config.xml & extras-config.xml
installed by their features using those filenames. In your base Feature
add a Component with only a CopyFile element which copies
base-config.xml to config.xml & Condition the component so it is skipped
if your extras Feature is sel
Ah I missed Rob's reply before I posted my own. I agree with Rob if you
don't need the original config.xml file(s) to exist for the user simply
skip the copy & use mutually exclusive Component Conditions to install
either file to the desired location.
If you do need the base-config.xml & extras-con
http://msdn.microsoft.com/en-us/library/aa370882.aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
rectory/Component
>> pair
>> must be listed in the CreateFolders table.
>>
>> I haven't seen any examples of using CopyFile that specified anything
>> about
>> a KeyPath, so am somewhat at a loss for how to proceed here. Any
>> suggestions?
>
http://msdn.microsoft.com/en-us/library/aa370322.aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Votive was very experimental/unfinished in WiX 2.0 so I would be very
careful about re-using v2.0 .wixproj files. They're pretty quick to set
up so you may be better off creating new v3.5 ones from scratch to save
yourself any issues in future.
There is no specific v3.5 WiX manual, the v3.0 pages
http://wix.sourceforge.net/manual-wix3/util_xsd_user.htm
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC15145
Your .wxi file should have the tag at the top level element
not
http://wix.sourceforge.net/manual-wix3/wix_xsd_include.htm
You add directories in a .wxi the same way you add them in a .wxs, use
Directory or DirectoryRef elements.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 94
Regarding your VBS custom action, see
http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx (pay
special attention to the 3rd point Rob M. makes).
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + I
Pre-req's should be implemented using bootstrappers not MSI packages.
See Burn, dotnetinstaller (http://dotnetinstaller.codeplex.com/),
SharpSetup (http://sharpsetup.eu/) etc.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
*
ssion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting user privileges
How do you set a certain privilege with the user element?
Am 21.06.2011 12:00, schrieb Pally Sandher:
> http://wix.sourceforge.net/manual-wix3/util_xsd_user.htm
>
> Palbinder Sandher
> Software De
Just an FYI, to use Environment Variables as Properties you need to
pre-pend them with % e.g. %USERDOMAIN (or [%USERDOMAIN] if using it in a
string of the Formatted type).
See http://msdn.microsoft.com/en-us/library/aa368012.aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8
ilege, but the user must not be an administrator. So I cannot
add it to this group.
Am 21.06.2011 12:22, schrieb Pally Sandher:
> http://wix.sourceforge.net/manual-wix3/util_xsd_groupref.htm
>
> It's listed right there as a Child Element of the User Element.
>
> Palbinder
http://wix.sourceforge.net/manual-wix3/WixUI_index.htm &
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
both posted many times to this list. I suggest searching in future
before posting.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 14
You could use the optional checkbox on the ExitDialog which would be the
quickest way. See
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm Instead of
using [#myapplication.exe] in the example give it the full path to your log
file.
Palbinder Sandher
Software Deployment En
1 - 100 of 1015 matches
Mail list logo
