To redistribute 3rd party installation packages you will need to use a
bootstrapper. WiX v3.6 has Burn in development which some people are
already using but the other options I can think of off the top of my
head would be dotnetinstaller (http://dotnetinstaller.codeplex.com/) or
SharpSetup (http:/
You could cover that scenario by checking if USERDOMAIN = COMPUTERNAME.
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 Scotl
Sounds a lot like this ->
http://sourceforge.net/tracker/index.php?func=detail&aid=3131700&group_i
d=105970&atid=642714
Try using XMLConfig instead as suggested on that bug report & see if it
fixes it for you.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141
Error Code 2228 is according to MSDN " Database: [2]. Unknown table
'[3]' in SQL query: [4]." ->
http://msdn.microsoft.com/en-us/library/aa372835.aspx
The only difference I can see between your PathEdit control & the one in
the WiX UI source for InstallDirDlg is the WiX UI source has
Indirect="yes
According to my Google this has been discussed on the list many times.
Set the Control's Property to whatever you specify in CheckBoxValue to
check it, set it to "{}" to uncheck it.
Perhaps try Bing next time if Google is failing you.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141
I don't use Burn but I would check why it's using the path
"\.\Packages\X.msi" as the "Note: 1: 1324 2: . 3: 1" in the log refers
to an invalid character "." in a path & that's the only path I can see
in your log which has a "." in it & it appears to start rolling back
right after that.
Palbinder
Seems eminently possible using ServiceInstall if you use one Component
with one File as the KeyPath & multiple ServiceInstall elements. However
if your Services need to be in separate Components then I think you'll
need to use Custom Actions.
Unfortunately Windows Installer is the weak link here r
custom action during
upgrade.
Do you think this might have caused the issue?
@Pally Sandher
I have tried using XmlConfig but in the following manner. When I am
installing freshly, that package uses XmlFile, but I have replaced that
with
XmlConfig in upgradeable version package and tried upgradin
You do have a choice. dblock has already done the hard work of writing
appropriate Conditions for you ->
http://code.dblock.org/ShowPost.aspx?id=101
You can use those Properties in your Conditions & thus you no longer
need Custom Actions to work around something which doesn't need a work
around.
P
For your RemoveFile element to work you'll need to specify ".lnk" as part of
the filename otherwise Windows Installer won't find the file.
However you shouldn't need a RemoveFile to remove a Shortcut which your
installation creates unless it's modified in some way after installation. Same
goes f
Why not use the well documented method built into the ExitDialog as
listed in the WiX 3.x manual? ->
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
**Desig
Why not use WiXUI_InstallDir instead of reinventing the wheel as it does
exactly what you're describing ->
http://wix.sourceforge.net/manual-wix3/WixUI_installdir.htm
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design,
Check a verbose log.
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 Buildin
You can find links to RegSpy2 at
http://www.installsite.org/pages/en/msi/tips.htm (scroll down to the heading
"Capture Self-Registration Information")
Use it to generate .reg file which you can then pass to heat.exe to transform
into a WiX fragment. You will probably want to clean up the WiX fra
al show us two different way, any Pros vs Cons?
> thanks!
> William L.
> On Mon, May 23, 2011 at 6:09 PM, Pally Sandher
> wrote:
>>
>> LaunchFile is used as an identifier. It means nothing outside the
>> context of that package. It could be called
>> Supercalif
I don't think there is an upgrade from v2.0 .wixproj to v3.x. Votive was very
much experimental & unsupported in WiX v2.0.
You're probably better off creating new .wixproj files in v3.5 as it's pretty
quick to do.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (
All files need to be in Components & all Components need to be in Features ->
http://msdn.microsoft.com/en-us/library/aa368003.aspx
Add it to a Feature & the error will go away.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
Set the Platform attribute on your Package Element to "x64" rather than "x86"
and/or create an "x64" platform build configuration in your .wixproj to build
an x64 MSI. You need separate x64 & x86 MSI's if you want to target x64
locations on x64 systems.
Palbinder Sandher
Software Deployment En
Alternatively
http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/
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. Registe
You could try to fake it by having 2 text controls on top of each other & use
the RadioButtonGroup Property as a Condition to Show/Hide the appropriate one.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate
You could use the Upgrade element rather than MajorUpgrade. That would give you
a Property you can use in a Condition to display a dialog asking the user if
they want to continue with the upgrade or exit the installation process.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945
Your code snippets look perfectly fine to me. I use code which is identical to
all intents & purposes which works fine.
However I would check a verbose log to see what's actually happening. Are you
trying to install an x86 MSI to an X64 location (as in "Program Files" rather
than "Program Files
Yes it's possible, see http://msdn.microsoft.com/en-us/library/aa368010.aspx &
http://msdn.microsoft.com/en-us/library/bb204770.aspx#concurrent_installs but
you shouldn't do it for the reasons listed on those pages.
Use a bootstrapper to sequence your pre-requisites. WiX v3.6 ships with Burn or
Because you posted a new topic to the list & someone doesn't know how to set up
his or her out of office properly so it doesn't spam list e-mails with replies.
It's worse when the actual list itself gets spammed by the autoreply like a
couple of weeks ago.
Palbinder Sandher
Software Deployment
I'd echo Peter's sentiments of WiXEdit. I used it a lot when I was learning WiX
& Windows Installer (back in the v2.0 days) & it was invaluable as a teaching
aid alongside the WiX tutorial. However I find Votive (WiX native plug-in for
Visual Studio 2005/2008/2010) a far better solution all roun
No, you'll need to create a separate CopyFile element for each subdirectory.
The directory paths need to exist in the Directory Table otherwise Windows
Installer doesn't know anything about them. You can't put completely unknown
stuff on to the target machine in the first place to use the CopyFi
1 - wrong list, this is the users list. This sort of post belongs on the
WiX-devs list.
2 - you'd be better placed submitting a feature request on SourceForge (or
CodePlex if the issue tracker has been migrated over, last time I checked we
were still using SourceForge for issue tracking).
3 - if
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
Sounds to me like you're drawing a second bitmap on top of the already existing
one. Don't do that just change the image the built in one uses.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141
What's the question? There is no earlier messages to the list this year with
this subject.
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.
Or sanitise the output from heat before you use it to build your MSI.
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 Scotlan
I use Votive in WiX v3.5 with VS2010 SP1 without any issues. I would assume
Votive in WiX v3.6 follows suit. No idea about Burn, haven't had time to look
into using it yet.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Des
Old bug with FileSearch which has been "closed" but never actually fixed as far
as I can see ->
http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1648267&group_id=105970
&
http://sourceforge.net/tracker/index.php?func=detail&aid=1273447&group_id=105970&atid=642714
Palbinder Sandher
?
And most Windows Installer paths end with a \ too, in the path properties.
Phil Wilson
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, November 07, 2011 6:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
One thing to keep in mind is that if you're targeting Windows Installer 5.0
it's only available on Windows 7 & Server 2008 R2.
4.5 is the latest available redistributable for earlier Windows versions.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F:+44 (0) 141 945 8501
ht
First you need to target Windows Installer 4.0 (or later which means 4.5 on
pre-Vista platforms) if you want to make a single package which can do per-user
& per-machine installations. This will involve bootstrapping the 4.5
redistributable for pre-Vista SP2 platforms.
The code you pasted shows
WiXUI_Advanced allows switching between a per-machine & per-user installation.
I would take a look at the sources for it. Bear in mind there are a lot of
caveats & limitations when creating such a package.
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 85
One of the problems I've noticed from using the redistributable of the Visual
C++ runtimes is that when there are updates released by Microsoft, the next
build of your application needs to be shipped with the new version of the
redistributable.
If you only ever use major upgrades this shouldn't
Server 2008 is x64 only (unless you're using an Itanium system which is
rather unlikely). Try looking in C:\Program Files (x86)\Windows
Installer XML v3\bin\
Does WiX show up in the ARP list?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 850
in the designated
folder, go figure. Must've been a bad drop. Sorry.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, January 07, 2010 11:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] HELP ...
Serv
Sounds like the user is downloading your MSI from a web page using Internet
Explorer & clicking "Run" rather than "Save" in the download prompt. The MSI is
being run from the users Temporary Internet Files & when the time comes for
them to install the later version, the old MSI simply doesn't ex
Use Win64="yes" in your RegistrySearch Elements to force them to check
the normal areas of the Registry rather than the WOW6432Node. You will
get ICE warnings for this in an x86 package.
However you can't have one MSI which works natively for both x86 & x64
platforms.
An MSI has a platform attribu
ing, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Jeremy Farrell [mailto:jfarr...@pillardata.com]
Sent: 14 January 2010 04:23
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to handle Registry Redirec
That is all you should Ricky need assuming you're using the VC++ 7 merge
modules provided with Visual Studio 2003. Your convoluted directory
structure is totally unnecessary as the merge module is going to put the
files into the WinSXS area regardless of where you
The following string format was not expected by the external UI message
logger: "The Windows Installer Service could not be accessed. This can
occur if you are running Windows in safe mode, or if the Windows
Installer is not correctly installed. Contact your support personnel for
assistance.".
ms
Until Burn is feature complete I'd recommend looking at dotnetinstaller
(http://dotnetinstaller.codeplex.com/). Been using it for a while now &
it's quite easy to configure & build in my experience.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 9
Regarding the ICE38 errors, it sounds like the directory your Component
is under is a per-user location. Try moving the Component to a
per-machine location like SystemFolder (even though you're not writing
any actual files or folders to the location in your Component) if it's
not there already. If
Looks like it's a bug in ICE61.
According to the MSDN documentation, VersionMin & VersionMax both "must
be a valid product version as described for the ProductVersion
property." See ->
http://msdn.microsoft.com/en-us/library/aa372379(VS.85).aspx
ProductVersion properties are valid if "The third fi
Post the relevant sections of code e.g. the dialog where you ask the
user for the installation directory, any associated properties and/or
custom actions & the section of the directory tree it relates to so we
can try & see what's going wrong. Also looking at a verbose log (msiexec
/a /l*vx ) migh
Have you tried using the -cc and -reusecab switches with light.exe?
Palbinder Sandher
Software Deployment & IT Administrator
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 i
If you want your users to do the work you could use a simple
LaunchCondition in Product B which checks something that indicates
Product A is installed before it will allow installation of Product B.
However if you want automation with separate packages you're going to
have to bundle Product B with
Looks like the weekly releases only keeps the last 2 for the active
development branch -> http://wix.sourceforge.net/releases/ &
unfortunately for you 3.5.1309.0 is 3 versions old.
If you're lucky someone might have 3.5.1309.0 lying around which they
can upload somewhere for you. Other than that i
LaunchConditions are package wide & hence are an all or nothing solution
(either you pass the LaunchConditions & can attempt an install or you
trigger one or more & don't get install anything). You can have Feature
Conditions or Component Conditions as Cody has shown below.
A Condition Element in t
http://msdn.microsoft.com/en-us/library/aa372457(VS.85).aspx
Palbinder Sandher
Software Deployment & IT Administrator
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 Scotla
http://wix.sourceforge.net/manual-wix3/heat.htm
Palbinder Sandher
Software Deployment & IT Administrator
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.
SC15
Either use something like dotnetinstaller
(http://dotnetinstaller.codeplex.com/ plenty discussion on this list of
it), wait for Burn to be "feature complete" or roll your own
bootstrapper.
Until Burn is ready I'm happy using dotnetinstaller & it appears I'm not
the only one on this list. There are
http://wix.sourceforge.net/manual-wix3/shellexec.htm
Palbinder Sandher
Software Deployment & IT Administrator
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.
Regular list contributor Neil Sleightholm wrote a pretty good article on
this topic ->
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Desig
InstallUISequence runs before InstallExecuteSequence. If you change something &
don't have a time machine handy would you expect to see it change before you
changed it?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve
Have you tried using heat.exe in WiX 3.0? The post you're referring to
is 3 years old which is very much pre-WiX 3.0. Unless there's some
requirement which means you can't upgrade to WiX 3.0 I'd strongly
suggest migrating. If you can't you could still try to use heat.exe to
generate the .wxs for yo
Unless you're pushing out .NET 4.0 Framework betas, you can't install
any earlier .NET Framework on Windows 7, they're already embedded into
it. I suggest looking at what your bootstrapper is trying to do when
it's launching your MSI as it sounds like you're attempting to do
something impossible fi
Install WiX 3.0 & run WiXCop.exe on your .wxs files to upgrade them to
the WiX 3.0 schema.
Shouldn't need to do anything more than that although I would recommend
looking at the things WixCop.exe changes as you could potentially clean
up/tighten your code by removing and/or replacing some things.
, this
error detail may be helpful to d iagnose the failure: Unable to load
file: c:\TEMP\station.dll, error: 193.
Thanks
Lian
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, February 11, 2010 3:12 AM
To: General discussion for Windows Installer X
Download WiX 3.5 & take a look. See http://wix.sourceforge.net/releases/
for the latest releases.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental So
In the words of Chandler Bing.
Can open, worms everywhere.
Palbinder Sandher
Software Deployment & IT Administrator
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 Scotl
That's not what merge modules are for. Remove them from your installer &
bootstrap the redistributable instead.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated En
Sounds like a bug in signtool.exe or one of its dependencies (if any) if
it works OK on smaller MSIs on the same machine.
Which version of the Windows SDK are you using? I'm using signtool from
the v6.1 SDK (have installed v7.0 but I've not gotten around to
modifying my build scripts as yet) but t
Hi,
I've unfortunately made a bad decision a few months ago which is the
cause of this query.
We have an installer which we've released 3 versions of in the past. All
cosmetic changes to UI etc, components were unchanged between all 3
versions.
V1.0 & v1.1 have product code A.
I (stupidly) released
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 Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
Fro
Are File Id's unique?
I'm impressed you can even get as far as light running the ICE's if you
have the same file in 2 components although quite how you managed that
is beyond me. Code snippets would be a big help as would pasting the ICE
errors from the build log.
Your approach sounds fine from yo
and No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 04 March 2010 02:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating a Major Upgrade
Package Elements are children of Product Elements
(http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm). That's
what the error is essentially saying. You've tried to put a Package
Element under the WiX element.
You may want to get a basic knowledge of WiX before you try building
entire inst
Windows Installer won't allow concurrent installations as it's a
transactional system. Use a bootstrapper.
Also WiX != Windows Installer. WiX is a tool for making MSI's. Windows
Installer does all the actual installation work.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 1
If you want to ship updates as MSP's (Small Update or Minor Upgrade in
Microsoft terminology) don't use auto-generated GUIDs. If you're only
ever going to ship updates as MSI's (Major Upgrades) you need to change
the Product Code every time anyway so auto-generating is fine. See ->
http://msdn.micr
The CopyFile element should do what want.
http://wix.sourceforge.net/manual-wix3/wix_xsd_copyfile.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmen
I've seen people pushing MSI building packages which have buttons on UI
pages to launch stuff like .NET Framework installers, XNA etc. during
the InstallUISequence to bypass this issue. Personally I'd never do this
as when a sys admin pushes your package out across their domain your app
could insta
Make sure your RTF is a 'plain' RTF. Easiest way to do that is open it
in Wordpad & save it. If you created or edited it in Microsoft Word it
will have a load of extra formatting all over it which causes problems
in ScrollableText Controls.
Are you using a stock WiX UI or a Custom/Customized one?
You're basically asking if the Component Rules exist & if so how do they
work.
See http://msdn.microsoft.com/en-us/library/aa370561.aspx & the pages
its last paragraph links to.
Rob M wrote some very good blogs regarding the above which I'd recommend
as "further reading"
http://robmensching.com/bl
ALLUSERS="2" is a valid setting.
http://msdn.microsoft.com/en-us/library/aa367559(VS.85).aspx
As Thorsten said on his reply, don't worry too much about locking that
type of thing down. If a user is competent enough to mess with your MSI
to engineer a per-user installation rather than a per-machine
The stock UI's only have one as described in the How To page
(http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm)
however there's nothing stopping you modifying the ExitDialog in the
stock UI you're using to add anything you would like. Neil Sleightholm
wrote a blog post on Custom
Add WiXUtilExtension as a Project reference (or supply it to light using
the -ext switch if you don't use a wixproj in Visual Studio) & remove
your Binary Element below as it's not needed in WiX 3.0/3.5.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0)
Upgrade to WiX 3.0/3.5 or write your own ShellExec custom action.
Palbinder Sandher
Software Deployment & IT Administrator
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
Not without using a Custom Action to do it out with your installation
sequence. ExitDialog is shown after InstallFinalize (assuming successful
installation), WriteRegistryValues must be between InstallInitialize &
InstallFinalize.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (
I'd suggest looking at what's causing the problem rather than assuming a
blanket upgrade to Windows Installer 4.5 as being a solution since
Windows Installer 4.5 isn't even pushed to Windows XP machines by
Windows Update, it's a manual upgrade. Considering I have people
complaining about things lik
I'd do something similar to the checkbox on the LicenseAgreementDlg. You can
find it in the WiX sources at
src\ext\UIExtension\wixlib\LicenseAgreementDlg.wxs (WiX sources distributions
can be found on SourceForge).
Disable the "Next" button on the dialog page where they select the installation
It's been a while since I used WiX 2.0 but I would check what your
Execute & Impersonate attributes are for your custom action. AFAIK you
should set Execute="deferred" & Impersonate="no" but I may be wrong as
it's been a long time since I've messed with UAC & Custom Actions (Rob M
& others on the l
Not using the standard Windows Installer UI. ScrollableText controls
don't have that sort of functionality.
You'd need to write your own UI replacement to achieve that.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.co
If you want it to run during the UI you need to sequence it in
InstallUISequence not InstallExecuteSequence. From that code it's not
running at the end of installation, it's running at the start of the
InstallExecuteSequence which is when Windows Installer actually does
your installation. See ->
ht
1 - correct but by Vista you actually mean Windows Installer 4.0/4.5 as this
also applies to Server 2008 (Vista/2k8 RTM & SP1 ship with Windows Installer
4.0, SP2 ships with Windows Installer 4.5).
2 - correct but again by Windows 7 you actually mean Windows Installer 5.0.
Same thing in practice
See the CopyFile Element ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_copyfile.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions L
No.
What's the error heat.exe is giving you?
Palbinder Sandher
Software Deployment & IT Administrator
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
Yes.
Remember to use -svb6 though.
Palbinder Sandher
Software Deployment & IT Administrator
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
Register
Verbose log will show what msiexec is doing between clicking "Repair" or
"Remove" & when it shows the Progress Dialog.
My guess is it's doing the stuff in InstallExecuteSequence before
"InstallInitialize" but I could be wrong. Since your installer appears to be
pretty large, checking all the st
Works fine for me in all our MSI's & I don't do any special ARP property
settings for it unlike a lot of the other items on that dialog.
Are you setting the Version attribute correctly on your Product element?
It should be something like 1.2.3.4 & I think the maximum value you can
use for any of t
http://msdn.microsoft.com/en-us/library/aa369759.aspx
Use a type 51 custom action to set that & condition it with "PATCH AND
Installed".
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovat
So how would you automatically include everything in a directory where the
filenames of those files can change from 1 build to the next?
WiX does have a way to handle this, it's called heat.exe. There are people
using it as part of an automated system to generate fragments, there's even
been cha
Set the default path for it to be AppData & add a Type 51 Custom Action
to change the path to your .exe's directory when the main feature is
selected for install.
Simplest option would be to modify your app so it always loads the
config from AppData regardless & just put it there. Actually why doe
Sent: 17 March 2010 16:46
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Disable UI in patch by default
I've tried to add following code
PATCH AND Installed
But it does't work (((
I've never worked with IIS but that's how I'd write my Launch Condition
in this case. That is assuming your RegistrySearch logic is correct for
the IIS_METABASE_COMPAT Property.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://w
rom this "loose file structure". However, I want a
hybrid solution where some of source installation files are taken from a
CAB file and others are taken from the source location as "loose files".
Is that possible?
Thanks
sanjay
> -Original Message-
> From: Pally
Were you using Components containing single files as generated by
heat.exe? Can you explain how you modified your File Id's to streamline
the sequencing? What's the average size of your installer when built &
what's the size of the files when installed?
I'm interested in cutting down installation
101 - 200 of 1015 matches
Mail list logo
