Wow people still do that?
I'm using VMWare ESXi on a dedicated machine and it's a hell of a lot
faster than imaging a drive when all you need to do is click on a
snapshot, click on the "Go to" button & it's ready for use in literally
a couple of seconds. I've got our QA guys using XP32, XP64, Vist
You're referencing something which only exists in MSI 4.5 & later.
Don't do that if you want it to work using MSI 3.1.
Also more information on your problem e.g. code snippets of the
offending custom action would assist people in helping you.
Palbinder Sandher
Software Deployment & IT Administ
Your question is a bit vague (and contradictory). What do you want to do
with these "support" files exactly?
If they're required for your product then use a bootstrapper to install
them before your product. Since you have a merge module for the XML
Parser simply merge it into your MSI using the Me
http://wix.sourceforge.net/manual-wix3/qtexec.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
add DllEntry="CAQuietExec". How can I use QtExec?
Furthermore, I don't know how to add -ext WixUtilExtension.dll To project
property in Visual Studio.
Do you have some experences how to use QtExec?
Regards,
Chunyan
-Ursprüngliche Nachricht-
Von: Pally Sandher [mailto:pall
As you say the Module element doesn't seem to have the Media child
element (http://wix.sourceforge.net/manual-wix3/wix_xsd_module.htm) but
it doesn't really matter. When the merge module is consumed into an MSI
its files will be compressed into the media table of the MSI and
therefore use the same
http://msdn.microsoft.com/en-us/library/aa367548.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
http://wix.sourceforge.net/manual-wix3/wixcop.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. SC1
Sounds like you want to do what Windows Installer terms a "Minor
Update". See http://msdn.microsoft.com/en-us/library/aa370579.aspx &
http://msdn.microsoft.com/en-us/library/aa370037.aspx
Creating Patches is covered in the WiX docs at
http://wix.sourceforge.net/manual-wix3/patching.htm. Personal
http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.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 S
http://www.codeplex.com/dotnetinstaller/
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
R
Personally I wouldn't worry too much about anything caused by VC++
redistributable merge modules. Any problem you find will be replicated
by the stand-alone redistributable installer & both were authored by the
MS Visual Studio dev's.
When I build my MSI's without the VC++ 8 merge modules included
What is the property MSSQLSERVER set to? You appear to have omitted this
from your code fragment.
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 S
Depends what you're trying to achieve.
You could write a bootstrapper that parses your XML file to generate the
required properties to pass to your MSI. This would be how I would try
to achieve this because I have had "Custom Actions = very bad" drilled
into me over the years by Rob M, Bob A et al
oolset.
Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ
value
MSSQLSERVER Is not a property, it is a literal string that should exist
within the Registry.
I'm essentially trying to check if 'MSSQLSERVER' exists within the
multi-string SQLSERVER.
-Origina
I need is some kind of conditional code the does the equivalent of
a "Does this SQLSERVER property *contain* MSSQLSERVER"
Dominique.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 14 September 2009 13:15
To: General discussion for Windows Insta
"This unfortunately produces WiX 2 Rigistry code that is now deprecated
in WiX 3. :( I then wrote an XSLT to transform the WiX 2 code to valid
Wix 3."
http://wix.sourceforge.net/manual-wix3/wixcop.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 14
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.
SC151
fficial
documentation showing exactly how each operator is used in a conditional
situation would be really, really useful at this point. At the moment I
feel like I'm walking through the woods, blind folded.
Dominique.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesv
ny?
As I mentioned in my original post, some kind of website or official
documentation showing exactly how each operator is used in a conditional
situation would be really, really useful at this point. At the moment I
feel like I'm walking through the woods, blind folded.
Dominique.
-Ori
I'd try changing
LicenseAccepted = "1"
To 'Order="1"' as from looking at the WiX v3.0 sources, WiXUI_Mondo.wxs has the
following:
LicenseAccepted = "1"
So it they could be conflicting.
Your code looks absolutely fine, other than this nothing jumps out as a
possible cause here.
If this fixes
Looks like a problem with your bootstrapper. Try running it in a debug
session.
It shouldn't be affecting your installer though. Once msiexec has been
called to run your MSI your bootstrapper *should* have nothing more to
do with the whole process.
Palbinder Sandher
Software Deployment & IT Admi
Give both app.exe unique File Id's & I suspect the shortcuts won't appear.
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. Regi
1.22159 if that is any help to anyone.
Is putting my CustomAction before LaunchConditions the best place to run
my vbs, or would there be another more appropriate place?
Dominique.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 15 September 2009 10:23
To:
That means Windows Installer is "thinking". We get it with patches when
you click on the Next button on WelcomeDlg as at that point the Windows
Installer is inventorying the product's currently installed components &
keypaths etc. Not sure what would cause it with an MSI, possibly a large
number of
Windows Installer 4.5
Or alternatively how can I check if v4.5 is installed so I can throw up
an conditional message.
Dominique.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 15 September 2009 16:03
To: General discussion for Windows Installer XML
I use dotnetinstaller (http://dotnetinstaller.codeplex.com/) to
bootstrap the .NET 2.0 SP2 Framework (and some other things) with my
MSI's. Works pretty well.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Desig
http://wix.sourceforge.net/manual-wix3/patching.htm (also available in
the WiX.chm)
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 Limit
Ideally you'd implement this by extending the current built-in WixUI
Dialog Sets and/or authoring new ones.
Same goes for "Standard" Custom Actions. That is what things like
XMLConfig/XMLFile etc are.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 14
The only steps which I've seen that take a significant length of time
are the indexing and subsequent cabbing of files.
Are you 100% sure your WiX v2.0 project had the exact same number of
files and the same Media attributes as your WiX v3.0 project? Changing
the compression level down to low or no
Vista doesn't support it? You're not viewing the "Programs & Features"
Control panel in the right view mode to see it (default view mode may
not show it)? It's a bug in Vista which is fixed in Windows 7?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0)
WIN64DUALFOLDERS is I expect since the MSI is compiled as 32-bit.
Brant the solution is to have separate 32-bit and 64-bit MSI's. You can't make
a "one-size fits all" package using Windows Installer.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 1
I think you're all missing the point here.
The issue is not where he installs his files to, his problem is writing to the
registry.
Nate putting all your x86 & x64 DLL's in the same directory is fine. You can do
this in both a x86 MSI and a x64 MSI. They can both install to the same path
under
If the file is generated by a custom action during install, you should
have custom actions to remove it during uninstall & rollback too.
See http://msdn.microsoft.com/en-us/library/aa371101(VS.85).aspx for
suppressing the reboot prompt.
Palbinder Sandher
Software Deployment & IT Administrator
I use the Privileged property in a LaunchCondition to do exactly that
Warne & it works without fail. Tested it on XP, XP64, Vista & Vista64
Virtual machines with user accounts which are only members of the "User"
group & it always works.
If you're checking during InstallExecute the MSI needs to be
If you have Diskid="1" on your Components you're going to need a Media
Element with Id="1" otherwise where will those files be stored when
light tries to compile your MSI?
You don't need anything other than Id="1" unless you have a need for
multiple cabs in which case you need multiple Media Eleme
v3.0.5419.0. Your v3.0 is very out-dated.
You won't be able to simply compile WiX v2.0 XML in WiX v3.0 by
upgrading your compiler. The schema has changed between v2.0 & v3.0. You
would be well advised to run your .wxs files through WiXCop.exe first
and/or re-harvest anything you previously harvest
There is no such thing as "UnInstallExecuteSequence".
Schedule & Condition your action appropriately in the
InstallExecuteSequence. I suggest something like After="RemoveFiles" and
set the inner text to something like "REMOVE AND Installed" (note: those
are suggestions don't just use them without
Right these are getting annoying now.
Are there no list admins around who can unsubscribe this address?
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
Are you totally sure the patch doesn't contain the new files from the
merge module? Have you checked a verbose log of applying the patch? You
may find the problem is Windows Installer not patching the files rather
than them not being included in the patch. If you have files with
resources (executab
You can't *easily* change the background bitmap on the Exit Dialog
without changing it on all other dialogs which use that bitmap
(WelcomeDlg is the main one which springs to mind, can't think of any
others off the top of my head right now but there's a few). If you want
to try it change the bitmap
Do you have the WiXCA DLL declared in a Binary stream?
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.
http://msdn.microsoft.com/en-us/library/aa372039(VS.85).aspx
WelcomeDlg is part of InstallUISequence. Run your Type 51 Custom Action
in it with Before="WelcomeDlg" & it should work.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://
The link for it on http://wix.sourceforge.net/releases/wix3.feed doesn't
work anymore so it's unlikely you can download it.
Why do you need that specific version? It's over a year and half out of
date & there's been almost 60 versions released since then with a
massive number of bugs fixed.
What i
Sigh. This was answered yesterday.
See the topic "Re: [WiX-users] How to change background color behind the
checkbox- last install 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 + Innovat
For released products yes there is generally an archive.
For alphas/betas/release candidates most people will generally not
bother since you inevitably want the release instead of a version still
in active development. Hence WiX v2.0 releases & WiX v3.0 releases are
available on SourceForge while
Works for me. Remember to add the Component to a Feature & it should be
all good. Change the 'On="both"' to "install" or "uninstall" if that's
what you'd prefer.
Only problem is you can only delete files in directories which you know
the names
http://wix.sourceforge.net/manual-wix3/wix_xsd_component.htm
Put SettingsXmlFile in it's own Component & set 'Permanent="yes"' on
that Component. It'll never be removed then.
I sincerely doubt XMLConfig is deleting your XML file during uninstall.
If you put a file on the machine during install, un
It is eminently possible to re-code the ExitDialog in WIXUIExtension so
you can specify a bitmap for only its use rather than it always using
the one defined in the WiXVariable "WixUIBannerBmp".
Will someone do it? Probably not. I've got Visual Studio 2008 now so I
could work on the code now but we
I think the only way for you to have localised text in the remaining
places would be to have a localised versions of the UI dialog(s) &
condition showing the dialog depending on the language code. That would
be a lot of copy & pasting & will likely increase your MSI file size.
You could try to mini
Feature requested it more than a year ago ->
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=2026675&gro
up_id=105970
WiXEdit is quite good for this as it previews your dialogs from the XML
code in an almost "WYSIWYG" type editor ->
https://sourceforge.net/projects/wixedit/
I wouldn't
Simple Answer: No.
Complex Answer: It depends on exactly what your installer does but the
things you can do are so limited they may as well not be possible
either. Hence the simple answer.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
Using the functionality Blair described below you could have your
project build multiple versions of the same MSI, bundle them all with a
bootstrapper & have the bootstrapper launch the correct one depending on
the users locale language settings. I haven't taken time to look at burn
yet but you cou
As Blair says UpgradeCode is only needed for Major Upgrades. Patches
don't need one (but you probably want to add one if/when you patch the
offending product so you can use a major upgrade if you ever have to in
the future). The WiX v2.0 help has a (very short) tutorial on creating
patches at http:
MSI MSDN
help states this is only possible for Windows 7 with MSI 5.0...
cheers,
Tobias
Date: Wed, 21 Oct 2009 10:29:53 +0100
From: "Pally Sandher"
Subject: Re: [WiX-users] Installing a Program for "All users" without
adminrights
To: "G
uot;.
virtually, Rob Mensching - RobMensching.com LLC
<http://robmensching.com>
On Wed, Oct 21, 2009 at 3:28 AM, Pally Sandher
wrote:
> It is potentially possible to either allow the user to choose whether
> to install per-user or per-machine by providing some method of setting
>
Customize it. See Neil Sleightholm's blog for a very good how-to guide
->
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
**Design, Simulate
I think your problem is due to using Level="0". See ->
http://msdn.microsoft.com/en-us/library/aa369536.aspx
Personally I would recommend you don't set your property to anything to
start with, simply use RegistrySearch to set it (so it will be null
unless your RegistrySearch is successful) & chang
Look at InstallDirDlg.wxs in the WiX sources. It does exactly what
you're trying to do without any problems.
Why are you trying to re-write this when it already exists in
WiXUIExtension?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
h
In most cases you would check for the existence of something the primary
product installs such as a Registry Key or a File Version. This is how
the .NET Framework checks in WixNetfxExtension work AFAIK.
I use Properties with RegistrySearches in our plug-in installers to
check for the existence of t
Answered an identical question yesterday.
See ->
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
**Design, Simulate + Innovate with the **
In
Um http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm ?
Also exists in your WiX.chm installed with the WiX toolset on your local
machine.
You may want to go through the tutorial as this is also covered at
http://www.tramontana.co.hu/wix/lesson2.php#2.3
Palbinder Sandher
Software De
Heat can't extract the COM information from your executable but never
fear, all is not lost quite yet.
I've used a tool called RegSpy2 to harvest the /regserver information
from an out-of-process COM server executable in the past. It's available
at http://www.installsite.org/pages/en/msi/tips.htm (
Luckily for you someone else asked the same question 5 hours before you
did.
See my answer to the thread "Heat and .exe COM objects".
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 wi
You should look at what your application needs installed to run rather
than what InstallShield does in the package it generated.
Before I joined IES our packages were created by the IT "manager" (he
'managed' a team consisting of himself) in InstallShield. They were
massively bloated with a lot of
http://msdn.microsoft.com/en-us/library/aa368569.aspx
Exit Dialog is shown by the InstallUISequence. You're also showing it
before that when a user clicks the Next button on your "MyDialog".
Follow the MSDN instructions to replace the Exit Dialog in the
InstallUISequence with your "MyDialog".
Pal
Try using "mszip" instead of "high" for compression on your media tag &
see if that changes the size of the cab file.
Essentially though you're comparing apples and steaks (see
http://en.wikipedia.org/wiki/List_of_archive_formats). If you want your
files be installed without any extra work you're g
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Wesley W. Terpstra [mailto:wes...@terpstra.ca]
Sent: 02 November 2009 16:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] LZMA
You remember incorrectly. They ship 3.1v2 with XP SP3 (see
http://download.microsoft.com/download/6/8/7/687484ed-8174-496d-8db9-f02
b40c12982/Overview%20of%20Windows%20XP%20Service%20Pack%203.pdf) which
was also shipped in SP2 for Server 2003 (and XP64 by extension) quite
some time ago.
4.5 is shi
Dieter if you read Luknos' e-mail you should see the reason why he would
like to disallow installing the x86 package on x64 platforms (see 3rd
sentence).
Rob Hampflett already posted one solution but a simpler way to achieve
this would be to add a Condition element inside your Product Element to
c
2 ways to achieve it off the top of my head.
1 - Easy way, use the Major Upgrade functionality. See the How To at
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm (also in the
WiX.chm). This requires the original MSI created in WISE to have an
UpgradeCode set in it. Having never used WISE
Try
light.exe -ext "C:\Program Files\Windows Installer XML
v3\bin\WixUIExtension.dll" SampleWixUI.wixobj
or
light.exe -ext "C:\Program Files (x86)\Windows Installer XML
v3\bin\WixUIExtension.dll" SampleWixUI.wixobj
if you're on an x64 version of Windows.
If you've installed WiX to a different loc
xobj Now I am getting light.exe : error
LGHT0001 : Unknown error "-1".
Exception Type: System.IO.IOException
What could be the reason?
Thanks and regards,
Shyam.
Pally Sandher wrote:
>
> Try
> light.exe -ext "C:\Program Files\Windows Installer XML
> v3\bin\WixUIExtension.d
Mrtn you need the appropriate version of Visual Studio installed to get
the merge modules. They appear in C:\Program Files (x86)\Common
Files\Merge Modules\ after installation.
Richard what you're asking for is impossible. If you use either the
merge modules or bootstrap the equivalent VC++ redist
What does the RegistryValue code look like? That might help people tell
you what's going wrong. If the value you're writing in this
RegistryValue is a Property which differs *at run-time* in the 2 MSI's
there may not actually be a problem here, it could be expected
behaviour.
Palbinder Sandher
So
Look up setup.exe & msistuff.exe in the Windows SDK. It does basically
what you're asking for.
Most bootstrappers will have some support for this. I've never used
setupbld.exe myself but you could do something this simple by wrapping
your MSI in a self-extracting archive using 7zip, WinRAR etc.
Pa
Without using an external UI or "embedded" UI I seriously doubt it. The
Windows Installer UI doesn't support changing the modality (and rightly
so in my opinion, the only thing more annoying than apps which stick
dialogs to the top of your screen are apps which automatically switch
focus when they
I'm assuming you're trying to use the SelectionTree Control.
Looking at a verbose log using WiXUI_Mondo, when I select & deselect
Features for install in the SelectionTree Control on the CustomizeDlg I
see things like the following:
MSI (c) (3C:E8) [12:24:06:682]: PROPERTY CHANGE: Modifying
MsiSe
What are your "filters" exactly & how are they being registered?
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
I ran into this same issue before the ATL security fix updates were
released. We had to get a hot-fix from Microsoft for the Visual Studio
2005 C++ redistributable controls as installations of MS SQL 2005 would
break our application due to being shipped with a post-SP1 version of
the controls which
I'm assuming you mean you've upgraded to v3.5.0925.0 not v3.0.5925 as
the last v3.0 release was v3.0.5419.0.
Firstly that's quite a massive jump to go from v3.0.2925 to v3.5.0925.
v3.0.2925 is at least 2 years out of date & you've skipped all the other
v3.0 releases & jumped straight to a v3.5 rel
2 ways you could achieve this off the top of my head.
1 - Use WiXUI_InstallDir (or whatever the WiXAware equivalent is)
instead of WiXUI_Mondo/WiXUI_FeatureTree or whichever UI is using the
SelectionTree control. You can then author a second dialog page after
the InstallDirDlg to configure the LOG
Using WiX 2.0 I built plenty of MSP's using those instructions in the past.
They're not completely clear in places but they work fine once you understand
what you're actually trying to do. The (old v2.0) WiX tutorial also helped in
this regard but I don't think it's available any more since the
Rob he's trying to use v2.0 how-to guide with the v3.5 toolset. I'd wait
for someone else to verify this is an actual bug as it works completely
fine in v3.0.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design
ch to patches. Unless I am
misunderstanding something, the 2.0 approach is much, much more useful
for an automated build than the 3.0 approach.
____
From: Pally Sandher [pally.sand...@iesve.com]
Sent: Monday, November 16, 2009 10:52 AM
To: General discussio
My moneys on it being this ->
http://msmvps.com/blogs/installsite/archive/2009/09/12/microsoft-s-recen
t-security-updates-for-visual-studio-break-windows-installer-updates.asp
x
See also ->
http://www.msigeek.com/microsofts-recent-security-updates-for-visual-stu
dio-break-windows-installer-updates/
You are running the MS procedure for building a patch. All WiX is being
used for in this instance is to create the PCP file.
Sigh.
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 wit
John that doesn't necessarily generate a UAC prompt. It will simply
check if the user has the permissions necessary to generate a UAC prompt
before the MSI installs.
Sachin is your custom action running during the InstallUISequence or
InstallExecuteSequence? What is the Execute attribute of the
Cu
Essentially "two installers listing the same component GUID in separate
locations" is how things like the VC++ redistributable merge modules
work.
For example, your installer puts the VC++ 2008 redistributables onto a
users machine. My installer then does the same. Both of our installers
use the m
Perhaps trying "OR Installed" as Blair suggested earlier might give you
better results.
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
That's known as a Minor Update but it's only one of the available upgrade types.
See 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 + Innov
Use tallow.exe from the WiX v2.0 toolset. You can then process the .wxs
files you output with WiXCop.exe in WiX v3.0 to update the XML in the
.wxs files from the v2.0 schema to the v3.0 schema.
Unfortunately that functionality was never replicated in heat.exe even
though it is the tallow.exe repla
I asked a very similar question in September last year on this list. See
-> http://n2.nabble.com/util-InternetShortcut-td838589.html for my
question & Bob Arnson's reply.
More info on util:InternetShortcut on Bob A's blog at ->
http://www.joyofsetup.com/2008/03/18/new-wix-feature-internet-shortcut
Remove the Condition elements in the code you pasted.
That will however enable the Browse button for all Features regardless
of installation status. To selectively enable it for Features which
haven't been installed yet and disable it for those which have you'll
have to modify the inner text of th
Use a LaunchCondition in your MSI to detect for .NET 3.5 SP1 and deny
installation if it's not present. See
http://wix.sourceforge.net/manual-wix3/check_for_dotnet.htm
Also the following page may be of use to you if you're trying to create
a bootstrapper to install .NET 3.5 SP1 before running your
Not unless you can re-write the standard error messages thrown by error
codes in Windows Installer (I'm guessing you don't work for the Windows
Installer team at Microsoft so that'd be a no). See error code 1633 on
http://msdn.microsoft.com/en-us/library/aa368542.aspx
Note that error codes are com
Changing the GUID of your component makes no difference to anything in
your example. Your code is telling the Windows Installer to uninstall
any old version of your software before it installs the current version.
If this is the only way your installers will work then your GUIDs can be
the same or
Same way you're passing your other parameters to your perl script. Only
difference is you need to put square brackets around Properties e.g.
[INSTALLDIR] and you might need to make them Public.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8
Not possible. MSI's have to be targeted at a specific platform type,
either "Intel" (32-bit), "Intel64" (Itanium) or "x64"/"AMD64" (64-bit)
A look at a verbose log of your 32-bit package would probably be quite
enlightening & before you ask, no there is no way to stop
WIN64DUALFOLDERS doing what i
Sounds like the age old IntelliSense bug if it's using 50% CPU on a dual-core
machine (as in 1 full CPU core). I see this on VS 2005 when opening our main
solutions (which have 90+ C++ projects, 0 WiX) but I've got a Core 2 Quad
(Q6600) so it doesn't bother me too much.
Ask Microsoft nicely if
801 - 900 of 1015 matches
Mail list logo
