Suitable de-fanged:
!--
DirectoryRef Id=InstallDirectory
Component Id=AssignServerPermissions Guid=NEED-A-GUID-HERE
Win64=yes KeyPath=yes
sql:SqlString ContinueOnError=no ExecuteOnInstall=yes
Id=CreateLogin Sequence=1 ExecuteOnReinstall=yes ExecuteOnUninstall=no
SQL=IF NOT
Where GPO is an issue, I create special installers tailored to the GPO
transforms (in particular, I concentrate on make installers that are easy to
both make transforms of and apply transforms too). GPO is still a very
significant deployment vehicle--especially for user-facing products. It
Another exciting scenario that can create this I've run into occurs during
testing. If I make an install, then uninstall, then install again in rapid
succession, you can run into a race where the folder you're trying to X to
(where X can be create, copy into or set permissions on) is still
[mailto:kirann.he...@gmail.com]
Sent: Tuesday, January 08, 2013 6:09 AM
To: John Cooper
Subject: Hello - are you aware of test mutations?Kindly assist me with some
answers
NOTICE: This electronic mail message and any files transmitted with it are
intended
exclusively for the individual or entity to which
It's a difference of focus. Much like conventional unit tests, LUX is designed
to validate the logic of your immediate custom actions. It's not really
designed to validate your installer overall. Those would be validation tests,
not unit tests anyway.
So, the focus is much narrower. That
Not really. The properties one could refer to aren't finalized until after
CostFinalize which is going to be too late for most of your dialogs.
The way I worked around it with one my multi-feature installers as to maintain
a set of shadow properties that tracked each of the features. This
answers
On 08-Jan-13 10:54, John Cooper wrote:
Conceptually, it requires carefully embedding debug code in your working
immediate custom actions that is triggered only when the mutating variable is
set to certain values. The part about embedding debugging code into my
custom actions is a little
See the Iis Extension in the Wix documentation.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Hertfelder Javier
For a given installer, open it in Orca and look at the appropriate table.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From:
The Wix documentation under InstallExecuteSequence and InstallUISequence has a
very comprehensive list.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
Where, specifically? Can you please provide a link? If it does exist, I haven't
been able to find it, somehow.
Thanks.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: January 18, 2013 16:51
To: General discussion for Windows Installer XML toolset.
Subject: Re
point it in the online documentation if possible:
http://wix.sourceforge.net/manual-wix3/main.htm
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: January 18, 2013 17:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] List of all
www.jackhenry.com
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Saturday, January 19, 2013 12:31 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Hello - are you aware of test mutations?Kindly assist
me with some answers
On 11-Jan-13 10:31, John Cooper
Using the existing ZIP deprives you of one of the key benefits of the Windows
Installer Service--that it manages the files you install. All but a handful of
my installers deploy web services.
Basically, you install the files to the point in the file tree you want them,
and then setup the
Look in the assemblies in the runtime (ILDASM will work). If there are any
.NET 4.5 dependencies, it will be a no-go on anything before Windows 7.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: John Cooper
Sent: Friday, January 25, 2013 11:16 AM
To: chr...@iswix.com; General
Yes, we do it in a very similar way. We just treat the status of
IntegratedSecurity as another component of building a valid connection string.
As part of the dialog process, the UI visible bits (server/instance,
Authentication Type, and User and Password (if SQL Authentication)), are passed
Another way to do it would be to generate a NuGet package. If there is
interest in this, I could help create such a package. (I make quite a few for
internal use--just haven't done it to Wix).
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee
One way would be to designate one file as the KeyPath file, and make the other
files CompanionFile's of the KeyPath file. Effectively, the version of the
KeyPath file becomes the version of all of its CompanionFile's.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry
What sort of error? I use util:PermissionEx extensively to set permissions on
certain files.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
Yes, I suspect the timestamps are tweaked during signing--I've never been able
to get signing to work right except in an AfterBuild target at or near the end
of the run. How do you link in your features. We use a wixlib for each
feature, link it into the main install build, and then sign
There's an important gotcha. The 64-bit SQL CE assemblies are just thunks for
the 32-bit pieces. This means installing the 32-bit assemblies is sufficient
on a 32-bit platform, but both need to be installed to work on a 64-bit
platform.
--
John Merryweather Cooper
Build Install Engineer -
Basically, you're going to have to modify the source code in setupexe.cpp by
commenting out the lines that setup CONFIGURE_ACTION_REINSTALL and
CONFIGURE_ACTION_MINOR_UPGRADE and compile your own custom setup.exe.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates,
I've had the same experience with Windows 7, but the explanation seems pretty
clear--setting the System Restore Point (by the OS) can take several minutes.
I've even added ProgressText to warn of this, but it is plain from the logs
that a lot of time is spent churning waiting for the OS to
Interesting problem:
One of our products uses the System.Management.Automation.dll assembly from
AppFabric 2.0. It has AssemblyVersion 1.0.0.0 and AssemblyFileVersion
6.1.7600.16385.
The System.Management.Automation.dll assembly that appears to come with
AppFabric 2.1 or PowerShell v3.0 has
, Apr 11, 2013 at 12:11 PM, John Cooper jocoo...@jackhenry.comwrote:
Interesting problem:
One of our products uses the System.Management.Automation.dll assembly
from AppFabric 2.0. It has AssemblyVersion 1.0.0.0 and
AssemblyFileVersion 6.1.7600.16385.
The System.Management.Automation.dll
this
System.Management.Automation.dll.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: John Cooper
Sent: Thursday, April 11, 2013 3:03 PM
I've got a product that now has a dependency on PowerShell version 3.0. The
POWERSHELLVERSION property in the PS extension only probes the v1/v2 location.
Are there plans to either add a POWERSHELLVERSION3 property or otherwise extend
detection of installed PowerShell to include PowerShell
Ext
If someone contributes it, yes. Want to send a pull request against wix38 with
that?
On Mon, Apr 22, 2013 at 9:05 AM, John Cooper jocoo...@jackhenry.com wrote:
I've got a product that now has a dependency on PowerShell version 3.0.
The POWERSHELLVERSION property in the PS extension only
The preferred method I like to use is to:
1) carry around my binary dependencies for a custom action in the Binary Table;
2) deploy them and set them up with a preparatory custom action in a sub-bolder
of the TEMP tree;
3) run the custom action itself from inside that sub-folder;
4) clean up the
I'm migrating the development branch of one of my products from Wix 3.5 and
setup.exe to Wix 3.6 and Burn. I'm having an issue getting the upgrade story
to work.
The upgrade code in both MSI's is the same. The later MSI by itself upgrades
the earlier product no problem.
But when I run the
package:
{B892ABD4-6B9B-432A-8B31-D849CBEA6969}, scope: PerMachine, version: 7.0.127.0,
language: 0 operation: Downgrade
Seems a bit off. How are you referring to the package(s) in the bundle?
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Monday, April 29
The guts of my code to do this looks like:
using (View binaryTable = session.Database.OpenView(ParameterizedBinaryQuery))
{
// Execute the parameterized query (id is substituted for '?')
// to get the binary record
using (Record idRecord
Yes, they get bound in. My case is to support stuff that I want to be
different from installer to installer. Also, there are runtime special cases
like SqlPackage deployment where you may need to copy a special DACPAC into the
deployment directory based on the version of the SQL Server on the
In general, it would be better to use the HeatDirectory / element. For
example:
EnableProjectHarvestingTrue/EnableProjectHarvesting
Target Name=BeforeBuild
HeatDirectory ToolPath=$(WIX)bin\
Directory=..\Folder
You can pass the server/instance pair to the Server attribute. I've never
tried this with SqlDatabase, but can you pass the server/instance,port?
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
Sent: Monday, May 13, 2013 1:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Is is possible to change default database port?
On Mon, May 13, 2013 at 11:20 AM, John Cooper jocoo
It is the standard practice for deployment to our farms. The Browse port is
firewalled off and the service disabled. We deploy to FQDN server name, a
non-standard port name, and one of two instance names. In operations,
deployment where we can browse the instance or use the default port is
, 2013 6:40 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Is it possible to change default database port?
Wix already has a separate instance attribute. So for Server attribute,
specify server,port?
-Original Message-
From: John Cooper [mailto:jocoo
There's an undocumented NETFRAMEWORK45 Property in the NetFX extension in Wix
3.6 that does the business.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
It is possible, but there will be a lot of edge cases.
It may be better to simplify. What does your application really need? It
sounds like it needs .NET Frame 4.0. If that's the case, .NET 4.5 is a
superset and will satisfy the need for 4.0 in most cases. In which case, you'd
be better
Use an immediate custom action that runs just after AppSearch to load the file,
process the XPATH, and load the appropriate MSI property with the value.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434
You need to write one. As custom actions go, it's not hard. I would recommend
a table-driven approach.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
: Thu, 16 May 2013 22:08:12 +
Subject: Re: [WiX-users] Install Net Framework 4.5 as prerequisite
only if on windows 7-8 and not installed
I ran into a similar situation, and in the end, I too just set 4.5 as the
prerequisite for my installer.
-Original Message-
From: John
First off, scheduling. The values of Directory properties (including one like
INSTALLDIR), aren't going to be meaningful until after CostFinalize. Since
you're running in the InstallExecSequence after InstallFiles, that's not it.
However, you should be able to resolve INSTALLDIR like any
No. You need to read in the Util schema.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: chennam
It is very bad practice not to have the install registered with Add/Remove
programs. I would adamantly recommend against it.
That being said, see the documentation for ARPSYSTEMCOMPONENT property.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee
It's just like setting any other property default:
Property Id= ARPSYSTEMCOMPONENT Value=1 /
This will put it in the Property Table with a value of 1. (assuming the
Fragment it's in gets linked into the installer).
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry
Well, for your website to be created, it needs to be in a component:
Fragment
?include ConfigurationInitialize.wxi ?
iis:WebSite Id=CoreWebservicesV3 Description='CoreWebservicesV3'
Since your iis:WebSite element is outside of a component, it serves only as a
locator and the site is not
Do you have the Util extension added as a reference to your Burn project?
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From:
If it doesn't get built, it won't get tested. Period.
Dev's have a tendency to consider installer building a waste of time (they
always think they can do it better with a 3rd-party zip lib and some sort of
XML config document) until it's one week before beta and suddenly you need to
shake the
Links or wixlibs.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wheeler, Blaine (DSHS/DCS)
the .wxs files on the candle command line?
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Friday, May 31, 2013 2:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn and Wixlibs
Links or wixlibs.
--
John
Properties are not persisted. You need to have authoring to do this.
Generally, there is a Registry component to save the information to the
registry, and a RegistrySearch to recover it. Rob even has a blog on persist
patterns although the URL escapes me at the moment.
--
John Merryweather
The log got stripped off. I've installed Wix 3.6 on quite a few Server 2008 R2
boxes (all but two of my build servers, developer boxes, and one of my two
boxes--all Server 2008 R2).
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS
Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.commailto:jocoo...@jackhenry.com
www.jackhenry.comhttp://www.jackhenry.com/
From: Mustapha Kone [mailto:mustaph...@yahoo.com]
Sent: Wednesday, June 05, 2013 2:37 PM
To: John Cooper; General discussion
Yes. All but one of my installers supports a web-based WCF service. One of
these services also deploys a significant amount of HTML, jScript, and CSS.
Payload is payload.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
The attachment WixError.txt is really a ZIP file based on the header. Comes
through as garbage although it may be recoverable.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
Use XmlFile and/or XmlConfig from the Util Extensions.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: chintala srinivas
On my net, there is GPO active such that two things essential to running
validation on my Windows 7 laptop are not met: 1) VBS cannot be run by a build
process; 2) the Windows Installer Service cannot be run by a build process.
If you're like me, you'll need a waiver from CIS to allow both
Adding a Name=. attribute to the Directory element will get the . in there.
I'll do some experimenting on a toy.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
I was able to get the .:System32 by using
Directory Id=ExperiementFolder Name=. SourceName=System32
Component Id=ProductComponent Guid=*
File KeyPath=yes
Source=$(var.SolutionDir).nuget\NuGet.exe /
/Component
/Directory
--
John Merryweather Cooper
.'
Subject: RE: Resolve Light 1056 Warning
Thanks, John.
That did it for me.
-Original Message-
From: John Cooper
Sent: Wednesday, July 10, 2013 12:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Resolve Light 1056 Warning
I was able to get
I also have a short article on how to write NuGet packages for application to
Wixproj Wix project files at my blog at:
http://borgsdemons.com/blog/2013/06/13/wix-and-nuget-creating-nuget-packages-to-deploy-wix-wixlibs-and-msbuild-tool-task-assemblies-to-wix-wixprojs/
--
John Merryweather
Burn is meant to provide this functionality, but it is under developed. There
are plenty of chaining/bootstrapping products out there in the meantime. One I
like is DotNetInstaller: http://dotnetinstaller.codeplex.com/ . You could use
this to install the prerequisite Adobe AIR, if
If you use the MajorUpgrade element then it is the default behavior. You're
using the older way, so you need to specify it explicitly.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
You can generate the instances in a preprocessor for loop. Since this stuff is
branded, you're likely to know a countable list of brands. You could define
list in a semicolon delimited var, pass it to a ?foreach? and build your
transforms that way. Not perfect, but doable.
--
John
How many CPU cores on the machine you're building from the command line?
Visual Studio forces serialize build, but the default for msbuild from the
command line is to thread the build with the number of CPU cores. If you don't
have your project references and dependencies just right, this
Well, you need a UIRef element for the UI you're trying to link it, to start
with. There are some properties you'll probably want to set up too. Take a
look at the Using Built-In WixUI Dialog Sets under Modifying the
Installation User Interface in the help.
--
John M. Cooper
-Original
Got a challenging problem. I have an include file that has versioning
constants in it. Running from the Desktop, all goes well, the constants are
defined, and the correct version number is set on the MSI.
However, on the TFS 2010 Build agent, the include doesn't seem to work. I get
the
personally. But I'm not a fan
of .wxi files. smile/
On Thu, Jul 14, 2011 at 1:39 PM, John Cooper jocoo...@jackhenry.com wrote:
Got a challenging problem. I have an include file that has versioning
constants in it. Running from the Desktop, all goes well, the
constants are defined
Very familiar! Just ran into it this past week . . .
--
jmc
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, July 20, 2011 8:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix 3.6.1518.0 to 3.6.1915.0 issue
Well, the whole point of a patch versus a major upgrade is it's smaller, so one
generally wants to include only the stuff that has changed. If you find
yourself wanting to throw more in, that may be a good sign that you might want
to do a major upgrade instead.
--
John Merryweather Cooper
Actually, it's best if everything that might get patched gets authored into its
own fragment. If you patch whole fragments, pretty soon the MSP file is nearly
as big as the MSI--defeats the purpose.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install
See the attributes to the PatchFamily element; most specifically, the
ProductCode, Supersede and Version attributes.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
Condition your dialog on WIX_UPGRADE_DETECTED.
However, is unattended upgrade or an install important? If it is, popping a
dialog during an upgrade scenario is going to force an attended install.
--
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install
From the documentation:
The following table shows the feature and component state values used in
conditional expressions. These states are not set until MsiSetInstallLevel is
called, either directly or by the CostFinalize action.
Since Launch Conditions are normally evaluated before
How are your Components authored? For patching to work as you expect, you need
one File in one Component in a separate Fragment for each. Otherwise, the Wix
linking rules will pull all the Components in a fragment even if you just want
to reference one.
--
John Merryweather Cooper
Jack Henry
Look at firstSequence for the Execute attribute to the CustomAction element
in the documentation.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
In general, you can't assume the UI is going to run for a repair. For example,
running Repair from the Control Panel button runs the repair in Basic mode
with only the basic progress dialog showing. It works from the
MaintenanceTypeDlg when you press the Change button off Control Panel
%WIX%\bin\heat.exe should work. The quotes are important as there maybe
spaces in the path. The WIX environment variable should be defined as pointing
to the WIX install location.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
As the error message implies, you need to do an /admin install of the MSI
before running pyro/torch so that it has access to the files if you don't want
to use wixpdb's.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
Office:
As the others have said, there's nothing special about wixproj
Projects--they'll build fine as part of a VS 2010 Solution. To get build order
right, you'll want to have appropriate references to projects consumed by the
wixproj in it. All of our builds make either an MSI or a wixlib, and
Yes.
--
John M. Cooper
-Original Message-
From: David Rickard (USA) [mailto:davri...@microsoft.com]
Sent: Wednesday, September 21, 2011 11:02 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Best way to invoke Wix from a TFS build workflow?
VS2010.
I concur. And having just had both the magically disappearing and the
magically appearing file situation, it's no fun to figure out. Generated
builds are great to prototype an installer or to run a very pre-release
installer, but I want both hands on the wheel for anything that's going to be
Is there any list of know issues with Windows Installer 4.5/5.0? Occasionally,
I see zombie msiexec.exe processes. This occurs even on a successful installer
verbose log. It's not common, and it appears to be random. Killing the
msiexec.exe zombies usually works. Rebooting always works.
The main installer I support creates a web site with several web services and
is specifically targeted at IIS7.5 and Windows Server 2008R2 including SP1.
While Wix doesn't support all the configurations I need to do to IIS7.5, the
ones it does support work fine.
-Original Message-
Do you have Orca?
What's in the IIsWebAddress table? Not much works right on configuration if
this table doesn't have some reasonable values in it.
What is in your IIsAppPool table? Again, it needs to be populated with some
minimal values before AppPool configuration is going to happen.
--
Interesting, the link How To: Run the Installed Application After Setup
seems to be dead in the wix.chm.
--
John M. Cooper
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: Friday, October 14, 2011 4:07 AM
To: General discussion for Windows Installer XML toolset.
In the wix.chm, go to Creating Installation Packages-Modifying the
Installation User Interface-Customizing Built-in WixUI Dialog Sets and then
scroll down to the Customizing the ExitDlg header.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer
Yes, GenericExecute is what you probably want.
--
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: David Watson [mailto:dwat...@sdl.com]
Sent:
Getting the following error randomly on fresh installs and upgrades during
testing:
ExecXmlFile: Configuring Xml File: some path\Web.config
The installer has encountered an unexpected error installing this package. This
may indicate a problem with this package. The error code is 25543. The
I query the IIS6 Metabase Compatibility layer (the custom action hasn't been
migrated to a pure IIS7 form using ServerManager ) to populate a ComboBox
(which gets queried for the Default Web Site if the UI is suppressed). In UI
mode, A dialog box with the contents of the ComboBox is displayed.
that only on Win2003 and using some newer method with
Win2008 that didn't require that Compat layer.
Thoughts?
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Friday, October 21, 2011 12:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re
Custom Actions to behave mostly well.
On Thu, Oct 20, 2011 at 1:05 PM, John Cooper jocoo...@jackhenry.com wrote:
Getting the following error randomly on fresh installs and upgrades
during
testing:
ExecXmlFile: Configuring Xml File: some path\Web.config The
installer has encountered
They get set too late. At the earliest, CostFinalize, and some states are
really good until InstallValidate. Your dialogs are occurring before that,
more than likely.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech)
Build Install Engineer - jXchange
Office:
.
85).aspx) though it appears to not actually be doing anything...
-Adam
On Tue, Oct 25, 2011 at 2:47 PM, John Cooper jocoo...@jackhenry.comwrote:
They get set too late. At the earliest, CostFinalize, and some
states are really good until InstallValidate. Your dialogs are
occurring
I use a customize version of the setup.exe from 3.5 RTM. Much less
functionality than Burn, but it works and I get caching which is mainly what I
was after.
--
John M. Cooper
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, October 25, 2011 4:13 PM
Well, the problem is, in my experience with the FeatureTree control, is that
you need an event triggered by it or after it to update the states. Otherwise,
the states seem to sometimes hold their pre-FeatureTree states until sometime
around InstallValidate. I've tried toggling INSTALLLEVEL
FOLDERID_ProgramData might be a good choice.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech)
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: Lars Augensen [mailto:lars.augen...@confirmit.com]
1 - 100 of 628 matches
Mail list logo
