And check verbose logs when you run into problems. In my experience 95% of the
time it'll tell you what you're doing wrong or at least point you in the right
direction.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.c
BTW Chad is correct, you can't have a single MSI that targets x86 & x64
locations on the system, it's an either/or situation.
x86 MSI's on x64 systems will be redirected to the x86 directories &
registry locations by WOW64, x64 MSI's can't be run on x86 systems.
MSI's must have a single platform sp
1 - Check a verbose log.
2 - Post your Custom Action WiX code. Half the code sample isn't much
help.
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 Environmenta
1 - I don't know. Modify your bootstrapper code so it launches your
MSI's with /lvx* ? Maybe search Microsoft support site & find
this http://support.microsoft.com/kb/223300 ? It's only the first result
in Google when I typed "Windows Installer logging" into the search
field.
2 - Read what I asked
Read the MSDN page I linked.
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
Registered Off
Does your VM have any Printers installed & is the Spooler service running?
It works fine for us using WiX v3.0 build packages on XP 32-bit, XP 64-bit,
Vista 64-bit & Windows 7 64-bit. I have a VMWare ESXi server setup with version
7 virtual machines for my own & QA's testing purposes.
Palbinder
m]
Sent: 13 May 2010 11:20
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Desktop Shortcut on Current User Only?
I did. So it means that unless I change the installer to current user I
have to somehow dynamically obtain the path of the current user desktop?
On Thu, May 13, 2010 a
Not a bug, not even close to a bug. You're using an x86 package on an
x64 system.
Look for WIN64DUALFOLDERS in a verbose log (/l*vx). You'll see that's
what's changing the property.
If you want to access x64 specific locations like C:\Program
Files\Microsoft Help Viewer\v1.0\ on x64 systems you n
Sounds very useful Tomasz. I was in the process of writing something very
similar last summer before a major release to for that release & all subsequent
release installations. Up until that release we didn't require any version of
.NET, just the VC++ 2005 redistributable controls. As we now nee
Do you have anti-virus running on the system you're trying to install
this package on?
Check a verbose log.
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 Envir
Test it on a virtual machine without any AV running/installed & see if
it works. If it does, AV is your problem. You then need to figure out
some way to get your VBS to run while circumventing every AV package
available & then sell the concept to malware authors everywhere & become
rich beyond the
I fully suspect WIN64DUALFOLDERS would still get in your way if you tried to
use %ProgramFiles (which on the XP64 machine I'm on right now maps to
C:\Program Files\ while %ProgramFiles(x86) maps to C:\Program Files (x86)\ FYI)
in a x86 package on an x64 system.
Palbinder Sandher
Software Deplo
1 - Check a verbose log.
2 - Try . That works
fine for me & is what is suggested in the How To page ->
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
**Desi
I didn't want to reply as when I tried to do something similar I
couldn't get it to work properly using the Extension & Verb element tags
so I fudged it using RegistryValues to add keys to
HKLM\Software\Classes. If you can't get it to work using the Extension
element you could always try that inste
dblock has posted a solution to this less than a week ago.
See http://code.dblock.org/ShowPost.aspx?id=101
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 Enviro
It does, I just tested it in WiX v3.0.5419.0. Works absolutely fine for
DLL's & OCX's which export the DLLRegisterServer function. My guess is
his DLL doesn't or it has dependencies which can't be loaded by heat.exe
when it tries to harvest it.
If your DLL can't be registered with regsvr32.exe /s
You'd need to recompile it.
Easier way ->
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 **
Integrate
First question, no idea. There's been plenty of build related discussion
on this list & you'd be better off asking this sort of stuff on the WiX
Developers list.
Second question, yes. WiX 3.0 is built in Visual Studio 2008.
As I said on my earlier reply an easier solution is to customise the WiX
Build your patches with the correct authoring?
>From the code you posted on the 13th you've got 2 completely separate patches.
>The first one updates your Product with Patch 1. The second updates your
>Product with Patch 2. These appear to be mutually exclusive. My guess is that
>you're applyin
Have you set
?
>From the looks of
Property(C): WIXUI_INSTALLDIR = TOP_LEVEL_DIR
you haven't.
See http://wix.sourceforge.net/manual-wix3/WixUI_installdir.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Desi
ComponentRef's & ComponentGroups are used in your Feature Tree not your
Directory Tree. If you want stuff to be in one place rather than another
simply move the Component Elements & everything inside them to where you
want them in your Directory Tree.
See -> http://www.tramontana.co.hu/wix/lesson1
Not in the stock WiXUI's. You'll have to add your own Dialog to gather
that information from the user.
See the last section at ->
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8
1 - answered an almost identical question yesterday funnily enough with
a link to the documentation page explaining exactly how to do what
you're asking ->
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
2 - That's a standard part of the WiX UI & has been for a very long time
-> h
ntents at compile
time based on the contents of the referenced project. I can't find any
actual definition of those component groups in the WiX project.
Cheers,
Rory
-Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, 25 May 2010 7:36 PM
To: General
Check a verbose log.
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
Registered Office - Hel
1 - don't use batch files. There are plenty of standard WiX Custom
Actions like QtExec (http://wix.sourceforge.net/manual-wix3/qtexec.htm)
or WiXShellExec (http://wix.sourceforge.net/manual-wix3/shellexec.htm)
to run external or installed applications & these should return
appropriate error codes.
rs.
So I am stll stuck. Can you bring me further by either showing me where
I was wrong, or showing me ways I didn't think of yet?
Thanks,
AL.
Pally Sandher wrote:
> 1 - answered an almost identical question yesterday funnily enough
> with a link to the documentation page explaining ex
1 - Can you install MSI's on "Windows Mobile Phone"?
If yes then yes you can use WiX to create your installation packages. If
no then no. WiX isn't some magical tool with it's own installation
system, it simply creates Windows Installer packages.
2 - MSDN would be a good start.
Palbinder Sandhe
Removing
>From inside your UI element would be a good place 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 + Innovate with the **
Integrated Environmental Solutions Limited. Re
Not possible using standard Windows Installer UI. At best you can run a
CustomAction when the user clicks the Next button depending on which
option they have selected in the radio button & move your ComboBox to
the next Dialog page.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44
More information on what you're actually trying to do, where things are
going wrong & the code you're using to do it might get you further
towards answers.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, S
I'm guessing this is a problem because the files are non-versioned. Try
using the CompanionFile attribute on those 2 files & link them to some
versioned files (DLL's, executables, etc) which will get replaced on
upgrades.
See -> http://wix.sourceforge.net/manual-wix3/wix_xsd_file.htm
Palbinder Sa
Try using "msiexec /i /l*vx " to get verbose logs.
I'm not sure on what info the WiX Standard Custom Actions like SqlExtension put
into the logs but those options should get everything & might help point out
where it's failing. For some reason I've got a feeling there is some Property
or vari
Not an IIS user myself but from what I've read IIS7 support is still in
mid-development for WiX 3.5 so you may be hitting a bug. Make sure
you're using the latest build of WiX 3.5 as bugs are fixed very
regularly.
Also your log extract is from the rollback, that's not where your error
is occurring
Personally I'd go with 3 but I already implemented something almost identical
for Shared data files rather than Shared libraries in our software 2 years ago.
If you want to block a user from uninstalling the MSI's manually & force them
to use your boostrapper simply add LaunchConditions with you
Ah so the old installer is the problem then not your new one. This will
be why people like Rob M. & Bob A say you should test upgrades before
you ship your first product (step 4 at
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm &
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/)
ijaychander2...@gmail.com]
Sent: 02 June 2010 06:04
To: Pally Sandher
Subject: Re: [WiX-users] wix installer for both GUI installation and
Commandline installation
Hi,
I'm new to WiX-users and I dont know whether I can reply directly are
not. I'm really sorry if this is the wrong proc
"yes" any errors will be swallowed (they may be in
> the log). If you are doing this only to make the uninstall robust against
> the database not existing, perhaps you should wrap the detach process in a
> test of the database existing instead.
>
> Michael
>
>
>
f
InstallExecuteSequence, I just wasn't sure of the to make it work with
uninstall. By the way, is there a list of these actions and install steps that
I can reference?
Thanks!
Nate
On Thu, Jun 3, 2010 at 5:52 AM, Pally Sandher wrote:
> Couldn't you just reschedule the Execu
Sign your MSI to make the UAC prompts look prettier.
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.
S
The answer would be no. Changing the Product Code means it's not a Minor
Upgrade, it's a Major Upgrade. See ->
http://msdn.microsoft.com/en-us/library/aa370579.aspx
You could deploy the changes as an MSP rather than an MSI.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141
You can't do it in Windows Installer so you can't do it with WiX. WiX
only makes Windows Installer packages (MSI's & MSP's), it's not some
magical voodoo that allows you to do stuff you're not supposed to be
able to for very good reasons.
Use a bootstrapper to chain the .NET Framework 3.5 installe
Personally I use XP 32-bit with SP3 & all "high priority" updates from Windows
Update as the baseline (no .NET of any flavour even though our app requires
Framework 2.0) for my own & my QA teams virtual machines (same for XP 64-bit
with SP2, Vista x64 with SP2 & Windows 7 x64). I figure if you c
I'd also recommend updating your WiX v3.5 to latest. IIS 7 support is
still under development in WiX v3.5
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 Environm
http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.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 Scotl
You're wrong about dotnetinstaller. You can chain together any
executables, MSI's, MSP's & MSU's using it. Doesn't need to specifically
be pre-requisites.
If you want an external UI and don't want to use dotnetinstaller or
something else already written, write your own. Good place to start
would b
When are you unchecking those features? During install or maintenance
(modify) or what? If it's during install I don't understand what you're
asking, nothing is installed at that point. If it's during maintenance,
that's how it works as long as your features are authored correctly.
Palbinder Sandh
Looks like your Type 50 custom action is authored correctly to me. Check
the BROWSER property is being set during the InstallExecuteSequence. Try
adding 'Impersonate="yes"' to the CustomAction, "http://"; to the URL &
maybe even adding 'Execute="immediate"' to the CustomAction (that's the
default b
It should work like that if your Features are properly authored without
any extra work. That's one of the basic functionalities of Windows
Installer.
Do you have Components referenced in more than 1 Feature per Component?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 94
Image attachments get stripped from the list. You may want to upload it
to somewhere & paste a URL to it or describe what you're trying to do.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + In
Looking at the WiX sources has all that information. In the v3.0
src\ext\UIExtension\wixlib\MaintenanceWelcomeDlg.wxs there is the
following:
Installed AND NOT RESUME AND NOT Preselected
Your code looks to me to be a quick & elegant solution to this issue
You could get rid of for
a 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 + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Well good luck with that.
Also from the code you pasted you've only got 1 Feature. What exactly do
you expect to happen when you have no Features selected for install but
you want your Product to still be installed? I assume you're using
WiXUI_Mondo or a derivative of it when there's no benefit ov
Why are you development teams using 2 different development environments for
the same product? If it's a 3rd party library or tool which needs the other one
when your dev team are developing using the primary one then fair enough but if
not, upgrade everything to VS 2008 & drop any requirement f
1 - Post the Custom Action WiX code. Could be a number of things.
2 - See 1.
3 - That's expected behaviour. Windows Installer won't request elevation
until it needs to which is when the InstallExecuteSequence starts (hence
anything needing elevation should be in the InstallExecuteSequence
between
Nope. Until Burn is done you'll need to write your own to do that (I
don't know if Burn will support that sort of scenario when it's
finished, just speculating since it's still in development).
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 85
http://wix.sourceforge.net/manual-wix3/heat.htm &
http://www.tramontana.co.hu/wix/lesson6.php#6.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 So
You could disable the Next button until MYSTUFFISVALID = "1" using
Control Conditions.
1
MYSTUFFISVALID =
"1"
But with that you will need another way to run the "ValidateMyStuff
Custom Action so you may have to move it to a new button
essional. The thought is
that there is something wrong with my installation which is why Windows
7 has to ask permission. This is a cause for concern and phone calls.
As a result, my supervisor and salesmen want no messages and no requests
for permission.
5) "You can do all this in a plain M
http://wix.sourceforge.net/manual-wix3/util_xsd_xmlconfig.htm or
http://wix.sourceforge.net/manual-wix3/util_xsd_xmlfile.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 **
The only other thing I could think of is having 2 dialogs which are a
clone of each other & simply looping round between them until the user
enters some valid data.
1
Do the same on the copy but reference the original dialog in the 2nd
NewDialog e
You only need an x64 MSI if you need to write to x64 specific folders &
registry locations. Otherwise an x86 MSI will do fine for x86 & x64
platforms.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simula
Sounds suspiciously like a Windows Installer issue.
Have you checked verbose logs when you use the ESC key to exit? What
code are you using to launch the webpage? I'd assume it's copied from
the "How To: Run the Installed Application After Setup" page at
http://wix.sourceforge.net/manual-wix3/run_
According to Microsoft the CAB file format has an internal limit of
approximately 2 GB -> http://support.microsoft.com/kb/836160 There is a
manual workaround for splitting files > 2 GB across multiple cabs listed
there which you may be able to use in your WiX project if you use the
-cc & -reusecab
1 -
2 -
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
and Condition the ExitDialog with "Installed" in the InstallUISequence
so they're mutually exclusive.
FYI an easier/proper way to do it would be to get the user information
out of the user before the InstallExecuteSe
See my reply to your other post & try to keep your issues limited to one
thread if they are the same topic (which these pretty obviously are)
otherwise you're going to confuse yourself & others when you start
getting replies to one thread advising you to do x when the other thread
is advising you t
It's conditioned with "Installed AND (RESUME OR Preselected)" so
anything which sets the Preselected Property (such as patching with
MSP's) after your MSI is installed will show it. See
http://msdn.microsoft.com/en-us/library/aa370839.aspx
Palbinder Sandher
Software Deployment & IT Administrator
What's stopping you asking the user questions in the InstallUISequence &
running the DLL function in the InstallExecuteSequence as is standard
practice? Your custom action doesn't need to run immediately as soon as
you gather information from the user, you can still schedule it after
InstallFiles o
ModuleInstallExecuteSequence doesn't exist in an MSI, only an MSM ->
http://msdn.microsoft.com/en-us/library/aa370049(VS.85).aspx
Even if you get your Custom Action into it, your MSI is still going to
have the same problem once the merge module is consumed if the Custom
Action is not Conditioned
http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
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
Binary Elements are extracted to temporary directories using auto
generated filenames (see a verbose log for an example). It's not
possible to use an application in a Binary Element with QtExec (I looked
at the same thing a while ago for a plug-in installer). You'll either
need to change it to use
You're trying to put Components marked as 32-bit into 64-bit only
locations.
For "RegistryValues" and "EulaPdf" I'm guessing all you need to do is
remove the Win64="no" attribute.
For the Visual C++ 8.0 Merge Modules, simply put them under TARGETDIR
(see -> http://wix.sourceforge.net/manual-wix3/i
Setup.exe is running your MSI with some parameters which double clicking
the MSI itself isn't (sounds like it's trying to do either Repair or
Reinstall by default). Find out what they are & then find out how to
remove them.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 9
Error 1 - Author a ProgramMenuDir. You can't link to something which
doesn't exist. See ->
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
Error 2 - Author an Icon Element. You can't link to something which
doesn't exist. See ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_i
1 -
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
However from looking at the sources WiXUI_FeatureTree already has
LicenseAgreementDlg after the WelcomeDlg. If you want a second one
showing a different RTF you'll need to write it (or copy & paste from
the LicenseAgreement
t way to test setups when you can do your tests and then revert to an
untarnished image.
Phil Wilson
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Friday, June 18, 2010 3:21 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
Answer to problem 1: I already posted a link to yesterday on this very
thread (in fact I can see it on my screen as I type this further down
the thread). Between Neil S's blog & the WiX UI pages in the WiX manual
you should have all you need to make the changes required.
ExitDialog is called by Wi
HasMSMQ & HASMSMQ are not interchangeable when talking about Windows Installer
Properties. Also Launch Conditions fire the error when the inner text evaluates
to false. Hence
would be a better choice for the inner text (assuming you set HASMSMQ_CORE in a
RegistrySearch for t
See the Id attribute @
http://wix.sourceforge.net/manual-wix3/wix_xsd_file.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. Re
indows Installer XML toolset.
Subject: Re: [WiX-users] Customizing WixUI_FeatureTree
Pally Sandher wrote:
> Answer to problem 1: I already posted a link to yesterday on this very
> thread (in fact I can see it on my screen as I type this further down
> the thread). Between Neil S's blog &
-Original Message-
From: Ivo Beltchev [mailto:i...@roadrunner.com]
Sent: 22 June 2010 16:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Customizing WixUI_FeatureTree
Pally Sandher wrote:
> If it's a readme why not use the "Launch an Ap
http://wix.sourceforge.net/manual-wix3/util_xsd_serviceconfig.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
Why does your Feature Tree have every Feature selectable as disabled?
Surely there's some core components of your application you'd want to
always be installed if the user is running your installer?
It's kind of pointless to try & handle a case where the user doesn't
select anything for install. W
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.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
FYI dblock posted http://code.dblock.org/ShowPost.aspx?id=101 on this
list a few times recently which covers this & other similar conditions.
I would recommend using the code on that post.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
Well first off you'd need to capture the details of an account which has
permissions to create accounts in the domain. Generally this is a domain admin
account but accounts can have permissions delegated to them so it doesn't
necessarily have to be.
Then you'd need to connect to a domain control
>From the sounds of it you're following the Component Rules
>(http://msdn.microsoft.com/en-us/library/Aa370561) quite well so it should
>work fine if all 30 installers install that Component to the same location.
>Just build a new installer with the updated file & it should update when you
>ins
It'll be rendering with the font specified in the DefaultUIFont Property
unless you tell it otherwise
Try
The standard fonts are listed in WiXUI_Installdir.wxs but you can define
your own using the TextStyle Element if you want to use something
different, just use them in the same way as above.
"I am trying to create HKLM\Software\Spiricon\Version5\"
You can do that with simple RegistryValue and/or RegistryKey elements in
WiX. Why do you need a Custom Action?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
He doesn't seem to care about using standard Windows Installer or even
WiX functionality Rob.
A direct quote:
"our experience is that Windows Installer works if it is done perfectly
and in the correct order. our code is defensive and deals with installs
and uninstalls that failed in the middle.
It should remove the file if the component is removed from a Feature.
Have you tested it? If so have you checked a verbose log?
If you're getting an orphaned file try scheduling RemoveExistingProducts
Before InstallInitialize e.g.
See http://msdn.microsoft.com/en-us/library/aa371197.aspx
Palb
Use <> instead of !=
See http://msdn.microsoft.com/en-us/library/aa368012.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.
? I
can't visualise how this would work with a Minor update...
Correct me if i'm wrong?
Stelios
Pally Sandher wrote:
> It should remove the file if the component is removed from a Feature.
> Have you tested it? If so have you checked a verbose log?
>
> If you're getting
Try using a MaskedEdit Control instead of an Edit Control. See ->
http://msdn.microsoft.com/en-us/library/aa369797.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 **
Inte
Try adding the Impersonate attribute with value "no" to your CustomAction
element. You may also want to change the Execute attribute to "commit" or
"deferred". See ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_customaction.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44
Could have already been reported as a bug. Sounds very similar to ->
http://sourceforge.net/tracker/index.php?func=detail&aid=2927773&group_id=105970&atid=642714
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**De
WiX != Windows Installer. You would do well not to confuse them or use
them interchangeably.
If you're using Major Upgrade functionality remove the Upgrade table
entries and/or your Launch Condition which block installing an older
version.
If you're not using Major Upgrade functionality, educate
If the file is installed as part of your installation you can simply use
it's Id as a Property e.g. [#foo.config] if you set Id="foo.config" in
it's File element (see ->
http://msdn.microsoft.com/en-us/library/aa368609.aspx). Use that
Property as the path for either XMLConfig or XMLFile to make you
want these files
also in previous state. I want to go to the previous state of the
installation directory.
Pally Sandher wrote:
> WiX != Windows Installer. You would do well not to confuse them or use
> them interchangeably.
>
> If you're using Major Upgrade functionality remove the Up
Change the HelpDirectory attributes for the TypeLibs in the pasted code
which point at SystemFolder to point somewhere else such as
"dir07B00FE80C030860241E2DB3BAF7AE7D" (that's an example, might not be
correct for your COM DLL's).
heat.exe generates sample code, you shouldn't expect to be able to
301 - 400 of 1015 matches
Mail list logo
