A person does need to use OnlyDetect=no to have a product removed. With it
set to yes it will only detect that it is there, but not remove it.
It's at least one thing to try.
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: Wednesday, November 07, 2012 1:43 AM
That Windows for you. Existing CMD consoles don't get updated environment
variables. Happens with no installer involved, too. For example, open a CMD
Prompt. Then go to your Environment variables and alter your Path. The altered
Path won't show up in the running CMD Prompt, but new CMD Prompts
If you gather a verbose log file you might search it for the word ROOTDRIVE.
This property can alter where an installation automatically goes.
You can set ROOTDRIVE manually in your WiX code, too.
Property Id=ROOTDRIVE Value=C:\ /
-Original Message-
From: Chaitanya
In addition to that you might want to read up on the ROOTDRIVE property as it
appears it is somewhat involved in the symptoms you are describing.
http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx
Also, don't forget about the well-known properties that identify various
Windows
these various Windows folders in my DIRECTORYREF its not taking.
How can I overcome this problem.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: 07 January 2013 23:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Changing
+1 for Orca. I use it a ton to inspect the resulting MSI and see if it looks
like it built like I wanted it to. You can sort by Sequence number in those two
tables to see what relative order things go in. Very handy.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Check to see if the InstallShield is a Per-user or Per-machine install and
compare that to your WiX installer. A per-user install can't be removed by a
per-machine install. If ALLUSERS isn't set or is set to 0 then that's per-user.
If ALLUSERS is set to 1 then it's per-machine.
-Original
I'd bet you haven't changed this variable.
Id=$(var.ProductCode)
While in there make sure this is set to what you want also.
Version=$(var.VersionNumber)
Make sure you do keep this one the same (it is if you get the message you
mentioned)
UpgradeCode=$(var.UpgradeCode)
-Original
Try setting this
Property Id= CA_WebAppPoolPassword.SetProperty Hidden=yes/
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Thursday, May 02, 2013 2:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Hide/blank out
If possible paste in a snippet of your log file around where the password is
seen. I tried for a long time to hide passwords using the same method. But it
was some built-in custom actions that were logging my passwords rather than
code I'd written myself.
Property Id=ConfigureIIsExec
Look at what you pointed to. It's an article from 2006 dealing with
InstallSheild 12 (NOT 2012) so it is very old. Some of it still applies to
older projects but I don't think that applies to a Basic MSI project.
If you run your MSI with MSIEXEC.EXE command line parameters to generate a
Aren't shell extensions either a DLL or OCX file as the entry point?
Think about what you have to do to manually deploy your shell extensions
and write down the steps (if it helps). These are the steps that you
would then author in WiX to automate the process through an MSI. A
simple outline with
You can't generally launch one install program from within another.
However, I am not familiar with the specifics of this scenario, so,
maybe?
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
Sent: Monday, December 28, 2009 10:23 AM
To: General
In InstallShield, its very simple I can literally launch any program
using LaunchAppAndWait(SOURCEFOLDER\SQLServer2008\setup.exe) but here I
can't find any tutorials or sample or even a code snippet to say you can
do that.
Arun Perregattur
-Original Message-
From: Chad Petersen [mailto:chad.peter
) to execute a
CustomAction. I thought that can be done?
Arun Perregattur
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Monday, December 28, 2009 4:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install external
=SourceDir exists?
Arun Perregattur
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Monday, December 28, 2009 5:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install external program from CDROM drive
And, maybe I
Our 32-bit .NET 2.0 Web app was having difficulties on this 64-bit
platform. Our assemblies were compiled as x86 (rather than Any CPU)
and they just would not load on this platform initially. If we set the
Application Pool advanced setting Enable 32-Bit Applications from
False to True that fixed
I set a bunch of different Properties depending on what is not-installed
and then display one dialog that lists all missing pre-reqs. I don't
care to show them the ones that are already installed, just those that
aren't.
Property Id=FIRSTBLURB Value=[ProductName] requires the following
To expand on that response, you might also need to prepend the vdir
property with an http://[ComputerName]/ before your vdir property that
you gather from the user.
-Original Message-
From: Chad Petersen
Sent: Tuesday, January 26, 2010 11:18 AM
To: 'General discussion for Windows
I would take what the user types in and put that in a Property (might
already be if you check a verbose log file) and then use that Property
to populate the config file in an XMLConfig element. Should be a piece
of cake.
Is that Pontiac Motor Division Arrow?
-Original Message-
From:
I do use a custom dialog to present the Web Site, IP address and TCP
Port and then use a custom action to validate what the user provides. If
it is all correct then the install proceeds and I use the Port Number
just as you describe in your reply. I default the TCP Port to 80, but
they are welcome
In your UpgradeVersion element you might try adding the OnlyDetect=no
attribute. OnlyDetect YesNoType Set to yes to detect products and
applications but do not uninstall.
Other than that, I'd get a verbose log and search in the area of
FindRelatedProducts and see what it says. If you changed the
Look at the Tallow.exe utility. I think Tallow -s filename might be a
first step to try.
Chad
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Monday, March 29, 2010 2:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
You're running into something a bit odd here. Notepad doesn't open files
in exclusive locked mode. For example, open a txt file in Notepad and
while it is opened in Notepad go to Explorer and you should have no
problems deleting the file. Same with WordPad. If it doesn't work like
that on your
You oughta talk to the other fella who emailed this list yesterday. He
*doesn't* want to see the USB drives as available to install upon. You
might have just the opposite condition of what he has. I might suggest
you search your project for Removable=no and see if it exists. If I
remove that
You might think that would be what you'd want, but the upgrade is NOT
Installed until you install it. That condition would apply to the
upgrade and not to the original version you installed. If you're other
logic was working you could probably add OR
OLDER_VERSION_BEING_UPGRADED.
You might want
You might want to look at or post your Control element and attributes
you have set. Something subtle like Integer=yes on that Control
element would make it act this way since it is not expecting a string in
that case. Personally I prefer to use Integer values for WiX checkboxes
as they seem a bit
In your case don't you want to say
CheckBoxValue=TRUE
I'm not sure what your CheckBoxValue=CheckBox would do, but it doesn't
look correct to me.
-Original Message-
From: Velu [mailto:velusa...@syncfusion.com]
Sent: Tuesday, May 11, 2010 8:02 AM
To: wix-users@lists.sourceforge.net
Verbose log file would be where I'd look next.
Best of luck Velu.
Have a good day.
-Original Message-
From: Velu [mailto:velusa...@syncfusion.com]
Sent: Tuesday, May 11, 2010 8:19 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Based on CheckBox value have to show the
Actually, I'd probably try without having the checkbox hidden. Something
in the back of my mind makes me think hidden controls don't behave
exactly like visible controls. But, a verbose log file is how I solve
just about every run-time install issue I've ever run across.
-Original
Dangerous move since other Web applications might be running (without
the customer necessarily knowing) and all will fail once the IIS Reset
is done.
But, if you really want to do that you could, as one alternative, run
IISRESET through a custom action.
-Original Message-
From: Carolina
Found this also. Haven't tried it, but if I had a need it would look
promising.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, May 11, 2010 11:12 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] FW: Reset
Ooops, helps to Paste: http://www.dalun.com/wix/06.10.2005.htm
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, May 11, 2010 11:21 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] FW: Reset IIS
Found
Working great for me. I even nest WebVirtualDir three levels deep in my
project and have not hit a problem yet and no reports from customers.
We've had 5 major upgrades since our product shipped.
You don't mention what it does or doesn't do when you use that element.
Does the MSI not launch? Does
Try this
Run the command MSIEXEC /X
Notice the same message. No installer is involved. Message is coming
from MSIEXEC.EXE or other Windows components associated with it. Message
is not coming from an installer. It's using a slightly different code
path depending on where you run it from (Command
Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: 11 May 2010 19:26
To: General discussion for Windows
If you folks are using WiX 3.5 then you could be hitting a bug. I'm
thinking it's the first to support IIS 7, which that method
WriteIIS7ConfigChanges seems to imply.
-Original Message-
From: gaurav_th [mailto:t_gaura...@yahoo.com]
Sent: Wednesday, May 12, 2010 4:23 AM
To:
.tmp, version 3.5.1710.0
CommitIIS7ConfigTransaction: Error 0x80070002: failed to delete config
backup
CustomAction CommitIIS7ConfigTransaction returned actual error code 1603
(note this may not be 100% accurate if translation happened inside
sandbox)
-Original Message-
From: Chad Petersen
Kurt - I have several files in one (huge) installer called web.config.
Each is a completely different file internally and each in their own
Directory and Component with unique GUID. What's the error message you
are getting? What version of WiX?
I think I've read on here that you can't write one
It is the ServiceInstall element in native WiX that sets the Start type
of the service. Since your installer is not installing this service
(Windows did that for us all) then I don't think you get to control that
aspect through your installer using native WiX. You'd almost certainly
be looking at
can tell. Just a
Registry element and a ServiceControl element.
Chad
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Wednesday, May 12, 2010 1:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Start an existing
RegistryValue element and ServiceControl element. Too much caffeine
today...
Sorry for the spam...
-Original Message-
From: Chad Petersen
Sent: Wednesday, May 12, 2010 1:38 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Start an existing disabled
If you Google that error it seems select people hit it even on real physical
boxes, under other flavors of Windows (98, XP), too. Windows misreporting the
drive type if I had to guess. Probably nothing wrong with your authoring. I'm
not seeing any definitive solutions out there.
-Original
I would probably be doing two Components as you mention in your last
attempt. The ICE30 error is probably related to duplicate shortnames.
You can probably get around this by specifying your own shortnames
rather than having WiX generate them for you. It might be giving each
Component the same
I can offer some help. For the command line you append your PROPERTYNAME
followed by an equal sign and then the value you want to assign to that
property. Like this.
msiexec /L*v c:\log.txt /i my.msi PROPERTYNAME1=value1
PROPERTYNAME2=value2
In my experience it seemed like if you gave it all
Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Wednesday, February 23, 2011 11:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re
In another area of your code look for the Product/ element and make
sure you change the Id= guid there as one necessary step. But, leave
the UpgradeCode unchanged in that same element. Also make sure you
increment your version number to something higher than that one you have
already installed.
I believe I might know what you are running into. You can't access things
destined for the GAC *during* the install. You probably will need to expose a
regular COM interface to your assembly and put it someplace accessible other
(also) than the GAC. We've had to do this with some of our .NET
Of course, there's more than one way to skin a cat. Check out Phil's suggestion
here
http://social.msdn.microsoft.com/forums/en-us/winformssetup/thread/9E48A3D0-ADF2-4CF3-B9BA-D5E9DE584C8F
-Original Message-
From: Colin LeMahieu [mailto:clemah...@gmail.com]
Sent: Tuesday, March 01,
I think it is because your Conditions are not mutually exclusive.
-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com]
Sent: Tuesday, March 15, 2011 2:25 PM
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] One install for multiple OS
I've got an
I found OR Priviledged to work better than OR AdminUser. It actually
triggered a Windows message rather than the message in the condition.
!-- first make sure the platform is at least win 2003 --
Condition Message='Your operating system must be Windows 2003 or
greater'![CDATA[VersionNT =
Is this a major upgrade or a minor upgrade? Sounds like the uninstall of
the older version might not be removing the service. Verbose log file
might be helpful. You can also hit Cancel during an install to
effectively pause it (then hit Resume to continue) to look at the state
of the machine at
Actually, I've been using [ComputerName] since MSI 2.0. If you read
those requirements a bit closer it goes on to say...
Windows Installer on Windows Server 2003, Windows XP, and Windows 2000.
Which implies just about any version.
The 4.0, 4,5 and 5.0 are required if you are on the newer OSes
X2
Even installs where I never use [ComputerName] the verbose log file
still lists the entry
Property(C): ComputerName = my computer name
Showing that this is always available for use in any install.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent:
Or you could publish the property just before entering your custom
dialog, like in the preceding dialog.
Publish Property=MACHINENAME Value=[ComputerName]1/Publish
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Thursday, March 24, 2011 12:59 PM
To:
If you run a CMD prompt and change to c:\windows\assembly folder and
then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as
subfolders. Yours is apparently in GAC_MSIL. From there it has folders
following a name similar to your DLL name. Then a version specific
folder in which your DLL will
I think this is happening because your Silverlight check has a version
number in the registry Data and the URLProtocol has no value in the
registry Data for that string. I think you might need to check a setting
that would actually have a value. As soon as I put a value of Test in
the URLProtocol
You might check with Adobe and see what their recommended method is for
detecting their application. I've had good luck doing that with third
party apps I've needed to detect. Never actually needed to check for
Acrobat myself.
-Original Message-
From: kim [mailto:contactme...@gmail.com]
be missing something simple, because it
doesn't
seem
that it should be so difficult to get this to work.
On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen
chad.peter...@harlandfs.comwrote:
If you run a CMD prompt and change to c:\windows\assembly
folder
and
then do a DIR
Oh, and an easy way to see what each MSI was used for is to open the
C:\Windows\Installer folder in Explorer and add the Subject column to
the details. I can immediately see what each MSI belongs to. Quite
informative.
-Original Message-
From: Chad Petersen [mailto:chad.peter
PM, Chad Petersen
chad.peter...@harlandfs.comwrote:
Oh, and an easy way to see what each MSI was used for is to open the
C:\Windows\Installer folder in Explorer and add the Subject column to
the details. I can immediately see what each MSI belongs to. Quite
informative.
-Original Message
Check a verbose log file and it should say why it is not replacing that
file. Typically because it is newer than the file you hope to replace it
with.
The RemoveFile element can be handy for some of these types of issues.
Not positive it's what you'll want, but maybe.
-Original
file is unversioned but modified
I will look at RemoveFile. It seems kind of counter intuitive that on
installation I want to remove a file. Would I put the RemoveFile
element in the same component as the component that is installing the
file?
-Original Message-
From: Chad Petersen
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Wednesday, April 13, 2011 2:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.
Yes
My syntax is a bit different than yours, but you might try removing the
[WPFINSTALLDIR] property from your RemoveFile element. But, I always
nest my Components under a Directory element, so our approach is
somewhat different.
-Original Message-
From: Kevin Burton
I might have missed but does this happen during a clean install, upgrade
or both?
-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com]
Sent: Tuesday, May 10, 2011 1:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Publishing to
http://msdn.microsoft.com/en-us/library/0c6xyb66.aspx
-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com]
Sent: Wednesday, May 11, 2011 7:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] missing assemblies referenced by
Heat /? shows usage. Looks like -ke is keep empty directories. I don't
see a way to exclude files, but maybe somewhere in the mix.
-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
Sent: Friday, May 13, 2011 11:20 AM
To: General discussion for Windows Installer
Versioning is built into certain files like DLLs and EXEs and not into
other files like XML and text files. That much has nothing to do with
WiX or MSI. Files are either versioned or they aren't. MSI simply
reflects those versions, by default.
-Original Message-
From: Dave Combs
What I find immediately odd is that your sample shows single quotes
around double quotes on the Target/ attribute. I'm thinking it should
be one or the other, but not both. Maybe it's correct, but it is
different than the manual shows, too.
-Original Message-
From: Jonah Dahlquist
Your isn't working like that already? Well, it's a simple fix, but may
be needed in quite a few places. In the following example the amp; in
front of the character you want to use as the hotkey should do the
trick.
Control Id=Next Type=PushButton X=230 Y=243 Width=57
Height=18 Default=yes
I'd suggest taking one step back. You mention a log file created in the temp
folder. Have you tried running your installer when the temp folder doesn't
exist or the TEMP variable isn't defined? If you are calling MSIEXEC /L*v and
wanting it to log to a TEMP folder I recommend you try it in
We place some of our shared files in C:\Program Files\Common Files\our
company name
-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com]
Sent: Tuesday, June 28, 2011 1:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How do you
Oh, and there is a known property called CommonFilesFolder as documented
here.
http://msdn.microsoft.com/en-us/library/aa367994%28VS.85%29.aspx
So, makes it real easy to use.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, June 28, 2011 1:46
I'm used to Major upgrades removing the previous release(s) so only the
newest major version shows in Add/Remove Programs. But, that probably
won't work if you have OnlyDetect=yes. And maybe that's not what you
want to do.
You might also check a clean install to see if all four files get
.
Do these files contain Version information
yes, all files have strong names
Is each file in its own Component?
yes
Kurt
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Wednesday, August 17, 2011 1:51 PM
To: General discussion for Windows Installer XML
Another option is to use the RemoveFile/ element tied to the same
Component as your File/ element. This will always clear out the
existing file prior to the current install writing the new one. Works
for rollback and uninstall.
Component Id=Filetxt DiskId=1 Guid=someguid
RemoveFile
That's very odd. The old MSI that installed those v.3 assemblies is the
one that should be removing them, not the newer MSI. If you don't
consider the upgrade, but just uninstall that older MSI through Control
Panel does it not remove the GAC'ed files? The Major Upgrade simply
uninstalls that
are the files being GAC'ed in the old installer? Custom action or
using the File element attributes?
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.) Build Install
Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: Chad
Trying to figure out the right approach to validate that a Web site
already exists during my install. In IIS6 I used
GetObject(IIS://localhost/w3svc) and queried that for the info the
user typed in. Any of you that target IIS7+ how are you dealing with
this? I am using a Web site locator for an
ServerManager
class.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Friday, October 21, 2011 1
if
end if
next
FindElement = -1
End Function
Thanks,
Greg
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Friday, October 21, 2011 12:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Validating Web site
Absolutely possible. Wouldn't be much fun if all files on installation
media had to be in the same folder. Wouldn't even work for files with
the same names that should go into different subfolders like you are
asking about.
On your hard drive just set up the folders the way you ultimately want
That does seem overly complex right out of the gate. Have you taken a good look
at the Binary element? This is how I make my files available to my custom
actions without having to copy anything to the local computer. Might not be
what you are after, but it's worth mentioning.
-Original
Microsoft used to provide the Windows Clean-up Utility (MSIZAP.EXE was
one common name) but I believe they must have removed it from their web
site.
This might be a viable copy of that same program. They seem to indicate
the author is Microsoft Corp.
The inner text in a Publish element is the Condition expression. An
inner text of 1 says to always do it. I could be off here, but it
seems like you just need to set up a proper Condition for each inner
text to only show the given dialog under a given condition.
Mine look a bit like this
Publish
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370556(v=vs.85
).aspx
Would probably look about like this. You don't have to use CDATA blocks,
but my example used the symbol so I just went with it.
Component Id=XP Guid=[yourguid]
Condition![CDATA[(VersionNT = 501)]]/Condition
If you open up your MSP in Orca does it have a FileShare and/or
FileSharePermissions tables? It sounds like it does based off of the
behavior you describe, but I'd hope it doesn't because I'd think
(ideally) your minor update should leave the shares and permissions
alone that were created by the
Of course each feature name is different, duplicate feature names aren't
allowed, but if the end user chooses more than one feature to install on a
given machine you don't really want the same exact SQL running multiple times
on that machine, do you? I'd think no matter how many features they
I wrote some VBScript that I call Files by Feature that I run against the
resultant MSI file. It opens the database and dumps a list of each file that is
in each feature to a CSV file that I can then open in Excel. It's basically a
manifest of what gets installed.
Otherwise, the XML seems
as a login name.
2009/6/22 Chad Petersen chad.peter...@harlandfs.com
Of course each feature name is different, duplicate feature names aren't
allowed, but if the end user chooses more than one feature to install on a
given machine you don't really want the same exact SQL running multiple
times
I can add to the conversation that CoreXT is an internal MS-only build
environment. This blog has some details.
http://blogs.msdn.com/clichten/archive/2005/06/07/DDCPX-Aftermarket-Solu
tions.aspx
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: Monday, June 22, 2009
We let the user modify the target directory in our UI, but I find I need
to use a type 35 Custom Action (no external code involved, though) to
alter the property being used. Also, on an upgrade we present the user
with the same directory they chose the first time around, but they can
alter it to
If you check out the @Return attribute of the Custom Action element
there is an asyncNoWait type.
Indicates that the custom action will run asynchronously and execution
may continue after the installer terminates.
-Original Message-
From: phillip_sid...@dellteam.com
We usually check with the vendor (manufacturer) of the software to see
what their recommended approach is as we consider them to be the expert
on their software. Heck, you work at Microsoft, can't you ask someone
there?
-Original Message-
From: Subrahmanya Jagadeesh Madduri
In addition to what Neil said I believe this link somewhat explains the
overriding issue and possible ways to help overcome the result you
experience.
http://blogs.msdn.com/astebner/archive/2007/02/08/assemblies-may-be-miss
ing-from-the-gac-or-winsxs-cache-after-an-msi-major-upgrade.aspx
I ran into the same issue with our installer. If you include an IIS
element in the installer it always seems to want to configure it.
They way I got around it was to write a VBS script that cracks open the
MSI database after it is built and modifies the ConfigureIIS action to
be Conditioned to
-related elements in your code.
Hope this helps.
-- Yan
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tue 9/29/2009 20:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing without IIS in spite
The Control element should have the attributes I believe you are looking
for.
Control Id=Combo Type=DirectoryCombo X=21 Y=64 Width=277
Height=80 Property=HARLANDFSROOT Removable=no Fixed=yes
Remote=no /
-Original Message-
From: Jahanzeb Khan [mailto:jk...@commondesk.com]
Sent: Friday,
Be careful there. A short name (8.3 convention) is different than a
Shortcut, which is what your subject line implies.
-Original Message-
From: Dave Kolb [mailto:d...@dotnetcodeslingers.com]
Sent: Tuesday, October 13, 2009 8:56 AM
To: 'General discussion for Windows Installer XML
1 - 100 of 267 matches
Mail list logo
