Check a verbose log?
Is your MSI built for the x64 platform? Open it in InstEd/Orca & check
the Summary Info. The Platform property should be set to x64 or AMD64
(both are the same thing, latter is deprecated by the former).
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141
Windows 8 should have .NET 3.5 (and 4.0) support built in. I think the
WiXNetFxExtension you're using hasn't been updated to take this into account
when setting those properties. If you're using WiX v3.7 bug report it at
http://sourceforge.net/p/wix/bugs/
To work around it in the meantime, chan
My Burn bundle is 105 MB (110,669,784 bytes) when built however the 3 MSI's
which go into it total 108 MB (113,602,560 bytes). I assume Burn is compressing
the MSI's to account for the smaller size of the bundle compared to the
individual MSIs (I use 'high' compression on my embedded cabs, might
The tutorial explains how to use WiXUI_InstallDir ->
http://wix.tramontana.co.hu/tutorial/user-interface/ui-wizardry
Do you have an INSTALLDIR under your TARGETDIR or are you simply setting
WiXUI_INSTALLDIR to TARGETDIR?
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F:
http://wix.tramontana.co.hu/
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. Registered in Scotland No. SC151456
Registered Office - Helix Bu
Download the WiX sources, find the HyperlinkTheme.xml file & modify it to your
needs.
You can then supply it using
Works for me.
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 **
Int
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm
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. Registered in Scotland No. SC151456
t;http://schemas.microsoft.com/wix/2006/wi";> > Name="Bootstrapper" Version="1.0.0.0" Manufacturer="" UpgradeCode="">
> >> Id="WixStandardBootstrapperApplication.RtfLicense"/>
> >
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm
...your msi stuff goes here...
End.
Yes it's that simple using WiXNetFXExtension. All the extra code you have is
just duplicating effort & causing you problems.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 85
and not display any thing to the user if all is Okay (.NET version
are the right.).
Thanks!
//Sam
On Tue, Feb 12, 2013 at 3:37 PM, Pally Sandher wrote:
> You need 2 projects. You have 2 outputs, an MSI & a Burn executable
> which wraps the MSI and deals with your pre-reqs. You c
Probably because WiXUI doesn't have any idea what your INSTALLFOLDER property
is or does.
If you're trying to set the contents of the PathEdit in InstallDirDlg you
should probably use the WIXUI_INSTALLDIR property associated with it as
detailed in the manual ->
http://wix.sourceforge.net/manual
ered which could cause problems if they attempt to
> reinstall or install a newer release at a later time etc."
>
> How do I specify that?
>
> //Sam
>
>
> On Tue, Feb 12, 2013 at 6:04 PM, Pally Sandher wrote:
>
>> For MSI UI ->
>> http://wix.sourcefor
No, that's what requesting elevation exists for.
You should be asking why you need to turn UAC off in the first place which I
suspect we can't answer.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innova
Personally I find a wixlib is mostly only useful if you're going to be sharing
them with a third party. They're effectively WiX's own version of merge modules
(but without a bunch of the problems merge modules have).
If your products A & B are being built from the same solution then feel free to
Create [INSTALLLOCATION]\Website\App_Config in your Directory Tree & use the
DestinationDirectory attribute instead of DestinationProperty.
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
Use WiXNetFXExtension ->
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm
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. Registere
Burn's standard BA can be very minimal if you configure it to be. Mine is
simply a dialog with some images/text and install & cancel buttons. Clicking
install will attempt to install .NET 4.0 client profile followed by my MSI(s).
Use something like
Since LicenseUrl is empty, i
There's more than just Install, Uninstall & Repair to consider for your custom
actions. dblock (creator of dotnetinstaller) has a handy WiX include you can
use to save time writing all the conditions yourself ->
http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maintenance
See
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registration-of-COM-Executable-Server-td6557760.html
or any of the other dozen or so times this has been asked & answered on this
list.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 850
You're missing the .NET Framework. You need to install it from the Features
add-in in the Management Console on Server 2008. It's not enabled by default.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Inno
http://msdn.microsoft.com/en-gb/library/windows/desktop/aa368009.aspx
Found under Operating System Properties in the Property Reference at
http://msdn.microsoft.com/en-us/library/aa370905.aspx
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://ww
Without seeing your Upgrade or MajorUpgrade code it's hard to say what it's
actually doing. As Rob says, I suspect it's upgrading when the versions are
equal due to the way your Upgrade table is laid out.
Have you tried installing 4.1.1.8896 first and then trying to install
4.1.1.8878 & seeing
Because the WiX team wrote the WiX pre-processor syntax & kept it to regularly
accepted coding standards (hence != for 'not equal to' as per every other
modern programming language) while the Conditional Statement syntax was written
by the Windows Installer team back in the mists of time?
Palbi
BTW this is covered in the WiX manual under the how to's ->
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm
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 Environm
The proper approach would be to not use regsvr32 to register DLL's & OCXs &
author the registration info yourself.
If you want to make this a lot simpler, use heat.exe to generate the Class,
TypeLib & Interface elements for you instead of having reams of RegistryValues
-> http://wix.sourceforge.
l?) "not equal to", so maybe
> > that's where it came from?
> >
> > -Original Message-
> > From: Pally Sandher [mailto:pally.sand...@iesve.com]
> > Sent: April 18, 2013 06:42
> > To: General discussion for Windows Installer XML toolset.
> &g
Rob the RSS feed for WiX 3.8 hasn't been updating since the 8th. I don't have
the WiX 4.0 feed subscribed to check it.
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 Enviro
I noticed this earlier in the week & I'm using v3.6.
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. Registered in Scotland No. SC151456
Regi
Which Temp directory are you looking in?
The TempFolder property page on MSDN says Windows Installer uses the
GetTempPath function to retrieve the path
->http://msdn.microsoft.com/en-us/library/aa372067.aspx
GetTempPath retrieves the first valid path stored in certain environment
variables in t
1 - use the -suid flag with heat.exe to make your id's more readable.
2 - what's the Component throwing that error actually contain? The opening tag
doesn't actually give enough info by itself.
3 - heat.exe isn't designed to be used directly after generation. You will more
often than not have to
I think you'd need to pass the property to a Custom Action to check that. The
only things you can do in Conditional Statements are listed at
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012.aspx and I
can't see anything which you could use there to test for the length of the
Pro
Try building your Bundle using the x86 platform rather than x64.
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. Registered in Scotland No. S
http://msdn.microsoft.com/en-us/library/aa372835.aspx says error 2727 is " The
directory entry '[2]' does not exist in the Directory table."
Without the log entries relating to this error there's only speculation and
conjecture.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945
No it's not a bug.
See #3 from my previous message. Then read it again until you understand it.
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 Limit
>From your InstallExecuteSequence code it looks like the Custom Actions should
>be called after the file is written to TempFolder. InstallFiles should be long
>before your Custom Actions but I would double check by opening the generated
>MSI in InstEd! or Orca (or any other package which you can
" What I mean: the application is based on MSYS and when a new user starts the
unix shell, he needs write access to folders like /home, ... . And /home is
contained inside the Programfiles\aplications folder."
No it's not. On Windows the equivalent of Unix "home" directory would be the
location
Use WiXNetFxExtension instead of reinventing the wheel ->
http://wix.sourceforge.net/manual-wix3/wixnetfxextension.htm
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 Envir
Change your condition to "SitBundleInstalled OR Installed"
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. Registered in Scotland No. SC15145
https://lists.sourceforge.net/lists/listinfo/wix-users
It's appended to the end every single post to the list. Even your own & this
reply.
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
FYI I bug reported this back in August 2012 ->
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=3557976&group_id=105970
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 **
Inte
WiXNetFxExtension will check a sub-directory called "redist" where your bundle
is for the package then download it if it doesn't exist at that path e.g.
"redist\dotNetFx40_Client_setup.exe".
This is standard Burn behaviour.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F
This is a known issue with *Windows Installer* patching & upgrades.
Windows Installer & WiX are not the same thing.
I'm guessing you're using Major Upgrades to upgrade (correct me if I'm
wrong). Take a look at a verbose log when upgrading or uninstalling &
see where it's taking so long. My guess wi
d the application's
elevation manifest prevents execution.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, July 05, 2010 4:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problems launching an application
Public Properties
ICE99: Created 06/18/2004. Last Modified 06/18/2004.
ICE100: ICE100 - Validates the MsiEmbeddedUI Table, checking for duplicate
filenames and validity of order values, attributes, etc.
ICE100: Created 04/02/2007. Last Modified 04/02/2007.
Laying out media.
Cordialement / Best
and put them in foo.config.
Following the WiX tutorial at:
http://www.tramontana.co.hu/wix/lesson6.php#6.10
did not really help with my senario...
Any ideas?
Stelios
Pally Sandher wrote:
> If the file is installed as part of your installation you can simply
> use it's Id as a Property e.g
d or not.
- if yes, do not install constant.msi. install variable.msi only.
- if no install both msi files.
Pally Sandher wrote:
> This is a known issue with *Windows Installer* patching & upgrades.
> Windows Installer & WiX are not the same thing.
> I'm guessing you're
An x86 MSI will install on x86 & x64 platforms.
An x64 MSI will only install on x64 platforms.
You cannot write to x64 locations in an x86 MSI. Windows Installer
simply does not support it & will stop you in your tracks if you even
try it.
Essentially your question is far too vague for a simple an
*Windows Installer* can't do that by default due to the dynamic nature
of the problem.
One way you could solve it (but would require a fair chunk of coding)
would be to do all your UI externally before launching the MSI & then
add the required rows to the Directory & File tables in your MSI before
: Re: [WiX-users] installer for both platforms(32 bit and 64 bit)
Okie...
simple and direct question
what is the default value of 'platform' attribute in Package element ?
Thanks for all your help.
Pally Sandher wrote:
> An x86 MSI will install on x86 & x64 platforms.
> An x64
dark.exe can decompile an existing MSI but the output from it is overly
complex & includes everything in every table in the MSI (including UI
which often you don't want/need as the WiX UI will be more than
sufficient). It also doesn't "clean up" the code it decompiles so you
will find a lot of Regi
Doesn't matter which version of WiX you're using, it's not possible
using Windows Installer. heat.exe or some other custom solution in your
build process will be required. If you're using Windows Installer, you
have to explicitly list each file & directory you want to create on the
target machine.
Don't waste time reinventing the wheel. See
http://wix.sourceforge.net/manual-wix3/qtexec.htm or
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, Simulat
http://msdn.microsoft.com/en-us/library/aa370579.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 Scotland N
I use
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---
Wouldn't it be better to ask the user the configuration questions during
the UI Sequence & make the modifications to the app.config using
XMLConfig as part of the install process? That way you could condition
when your dialog is shown more appropriately instead of needing multiple
ExitDialogs and y
e installation, or prior installation, OR,
branch off and edit the entries, and submit to update the deployed
app.config file...
On Wed, Jul 14, 2010 at 11:29 AM, Pally Sandher
wrote:
> Wouldn't it be better to ask the user the configuration questions
> during the UI Sequence & m
http://www.tramontana.co.hu/wix/lesson4.php#4.1
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
CONFIG button from
the MyExitDialog given a REMOVE path... I think the point in the
installation at which this button is shown that REMOVE="ALL" and things
aruond installation are no longer "checkable"... I think I may need to
save another Session Property to set at a certain ti
VC++ 2008 redistributables are available as merge modules in C:\Program Files
(x86)\Common Files\Merge Modules\
Simply consume them in your MSI using Merge Elements. Unless you have other
pre-requisites which don't supply merge modules e.g. .NET Framework then you
shouldn't need any extra code.
The stock WiX UI's are found lacking when it comes to MSP support.
You'll find a lot of the text controls on certain dialogs e.g.
ProgressDlg is conditioned with "AND NOT PATCH" so you end up with blank
dialogs which you'll need to customize to fix anyway.
I've never got around to fixing it myse
1 - Free more space on your C: drive or fill your D: drive.
http://msdn.microsoft.com/en-us/library/aa371372.aspx
2 - Author your directory structure correctly? Code samples are a big
help when you're asking vague questions like "why doesn't this work".
Palbinder Sandher
Software Deployment & I
Try removing the Name attribute from the ProgramMenuFolder Directory
element & try giving your RegistryValue a Name attribute.
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 *
"heat.exe /?" or http://wix.sourceforge.net/manual-wix3/heat.htm or
http://www.tramontana.co.hu/wix/lesson6.php#6.1 might be good places to
start.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate +
This link may be of use to you
http://catb.org/~esr/faqs/smart-questions.html#before
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 Limi
You'd need a per-machine installation to do that anyway (see
http://msdn.microsoft.com/en-us/library/aa370882.aspx)
The "How to" guide at
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm works
pretty well as long as your package has ALLUSERS set to 1.
Palbinder Sandher
So
Why don't you try & resolve your linking errors when trying to build
wix-contrib instead of trying to reinvent the wheel & failing?
Also why are you storing user specific data under the installation
directory instead of somewhere like My Documents or CommonAppData as per
Microsoft's platform guide
I doubt it's possible without modifying the WiXNetFxExtension code.
Use a bootstrapper to sequence your pre-requisites. Concurrent
installations are *very* dangerous & highly unsupported by Windows
Installer. Also consider how your scenario would support basic or no UI
levels (/qb or /qn).
dotnet
or 64-bit and then install the correct .NET Framework?
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, July 21, 2010 10:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Re-evaluate NETFRAMEWORK20 Property
I
not supported, but it was from a
long time ago, so I was just wondering if support has been added for
this.
Thanks for your help. I have been struggling to find a solution for
this issue for several days now and your help is much appreciated.
Katelyn
-Original Message-
From: Pally Sand
When cancelling the installation process the dialog launched is the one
in the InstallUISequence with sequence -2 (UserExit in the standard WiX
UI).
I don't think you can have multiple entries in the Sequence tables with
the same sequence number so providing another appropriately Conditioned
dialo
MSI (c) (74:80) [21:07:26:477]: Doing action: ValidateProductID Aktion
21:07:26: ValidateProductID.
That's the InstallUISequence not the InstallExecuteSequence.
WiX doesn't "ignore InstallExecuteSequence" as the InstallExecuteSequence is
just another database table to WiX. WiX is a way for you
If you read my reply you'll see I never mentioned "user accounts"
anywhere. My questions was "Why are you storing user specific data under
the installation directory instead of somewhere like My Documents or
CommonAppData as per Microsoft's platform guidelines?".
Palbinder Sandher
Software Deploy
You need to add a TargetImage Element for the 1.0.1.1 package to your
UpgradeImage Element as you have done for the 1.0.0.1 package
Without that the 1.0.2.1 patch knows nothing of the existence of the
1.0.1.1 package.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 85
http://dotnetinstaller.codeplex.com/
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
Regist
You need an x86 package and an x64 package which consume the correct
merge modules.
You can't use x64 merge modules in an x86 package, that's what the error
is trying to tell you.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://w
I would like to also strongly recommend Peter's advice on only using
Windows Installer clean up utilities as the very last resort when
everything else fails. We've had to rebuild a users Vista SP2 machine
recently because he took IT matters into his own inexperienced hands,
googled MSICUU.exe & bro
Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: 23 July 2010 13:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] InstallExecuteSequence completely ignored
Dear Pally,
Am 23.07
InstEd is a much better (free) tool than Orca if you absolutely have to
open up MSI's -> http://apps.instedit.com/
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 **
Integrat
http://www.tramontana.co.hu/wix/lesson6.php#6.7 &
http://msdn.microsoft.com/en-us/library/aa367593.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 Environme
You could add a second EULA dialog after the dialog with the FeatureTree
which only shows when the Feature or Features you need to show it for
are selected. The user guide page on Customizing the WiX UI should help
you get started ->
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
Y
http://msdn.microsoft.com/en-us/library/aa370859.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 Scotland No.
FileVersion.fileId) , because I can't change my file version. Is
there any other way to update the version number of the MSI
automatically? is it possible to read it from a file ?
On Tue, Jul 27, 2010 at 6:10 PM, Pally Sandher
wrote:
> http://msdn.microsoft.com/en-us/library/aa37085
version
number automatically now that i cannot use !(bind.FileVersion.fileId).
Thanks for the "Where's Wally" stuff though.
On Tue, Jul 27, 2010 at 6:41 PM, Pally Sandher
wrote:
> OK you clearly missed the point on the page linked so I'll do you a
> favour & copy
s like a good starting point. Forgive the stupid question,
but how do I then remove things from the feature tree due the responses
on a dialog? Ideally I'd also want it in maintenance mode - display it
again if maintenance mode is started if it's not already been accepted.
__
No but you can use heat.exe to achieve a similar result. Plenty of
discussing on this list how to do exactly that, search the archives.
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 w
Try something like
I think that should work but it depends on when (if?) Windows Installer
re-evaluates the &Feature Properties. It normally checks that stuff
during CostFinalize which runs before the WelcomeDlg shows up in the
InstallUISequence so I'm not sure if it will re-evaluat
You can use an XSLT to transform the output from heat.exe by supplying
it with the -t parameter without any need for a custom application if
you need that functionality.
Bear in mind that heat.exe isn't a substitute for actual setup
development. It's a tool to make doing things (initially) easier
I was looking at a log of one of my installers while poking around with
something in the InstallUISequence & noticed that the longer it sits in
the InstallUISequence, the bigger the log file became. Looking through
the log I found there are repeated instances of "Note: 1: 2727 2: "
throughout it s
You could find out what's causing the problem & fix it as those modules
uninstall completely fine for hundreds if not thousands of other peoples
products without any issue so it's highly likely the problem is being
caused by your installer code.
Or you could remove the consumption of the VC++ merg
The only difference is one is named INSTALLDIR & the other is named
INSTALLLOCATION.
It's the same as doing
string xyz;
string abc;
It matters not which you choose just make sure you're consistently using
the same one or you'll trip yourself up. MSDN page on Properties is ->
http://msdn.microso
Firstly don't use TARGETDIR as a ConfigurableDirectory as TARGETDIR is
the root element of your directory tree & used for other things such as
administrative installations (see ->
http://msdn.microsoft.com/en-us/library/aa372064.aspx). You main issue
seems to stem from confusing TARGETDIR with INST
It indicates you have an error somewhere earlier in your install
process. Search a verbose (/l*vx) log for the actual error.
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 **
You could achieve that by simply scheduling RemoveExistingProducts
before InstallInitialize ->
http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx. "normal"
usage placement tends to be after InstallInitialize as the WiX
documentation suggests ->
http://wix.sourceforge.net/manual-wix3/major
http://wix.sourceforge.net/manual-wix3/wixnetfxextension.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 Scotl
1 - update your WiX toolset. v3.0 has been final for a year & a month & you're
using a really old pre-final development build ->
http://wix.sourceforge.net/releases/3.0.5419.0/ or
http://wix.codeplex.com/releases/view/44406
2 - The documentation is correct. Your problem is the Property Element
olset.
Subject: Re: [WiX-users] Note: 1: 2727 2:
Hmm, random guess. How many Directory elements do you have with no
parent?
Just TARGETDIR or others...?
On Wed, Jul 28, 2010 at 9:27 AM, Pally Sandher
wrote:
> I was looking at a log of one of my installers while poking around
> with something
http://catb.org/~esr/faqs/smart-questions.html#beprecise
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 N
Tried using the "Linker" box under "Additional Parameters" in the "Tool
Settings" tab of your .wixproj Properties page?
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 **
Integ
Or see the WiX documentation ->
http://wix.sourceforge.net/manual-wix3/major_upgrade.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
Heat.exe doesn't create Features, you'll have to do those manually. You
can however use the -cg option to create a ComponentGroup Element which
you can reference using a ComponentGroupRef Element in your Feature
which does almost all the work for you.
I also recommend using the -suid option as the
401 - 500 of 1015 matches
Mail list logo
