, the surrounding lines in a verbose installation log around the error are
often helpful in diagnosing installation errors.
From: Kagiso Seboni [mailto:kagisoseb...@yahoo.com]
Sent: Tuesday, June 29, 2010 6:08 AM
To: Blair wix-users
Cc: wix-users sourceforge
Subject: Fw: [WiX-users] Fw
Using * for components should always be appropriate for all components
that accept * for the Guid, as long as you have never shipped the
component with a different GUID before.
It won't cause problems with generating Patches. What will cause problems
with generating patches is removing any
are always present and
haven’t likely been corrupted or lost.
If you are using tutorials or example code designed for 2.0, you will need to
upgrade those examples.
From: Kagiso Seboni [mailto:kagisoseb...@yahoo.com]
Sent: Monday, June 28, 2010 11:10 AM
To: Blair
Subject: Re: [WiX-users
that it will interface with. Tools built for WiX v2 generally won't work with
v3.x, and it is not expected that v3-level tools will directly work with the
future v4 of WiX (at least without some edits and recompiling).
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, June 28, 2010 12
Yes, but I don't think you have to rebuild the setup.exe stub. You could
instead try using the mt tool and replace the manifest with one that
contains all the appropriate elements needed for both style and privilege.
-Original Message-
From: Sagar [mailto:sagarkavitak...@gmail.com]
The idea behind fragments is that they supply blocks of authoring (aka code)
that are included or excluded as units. They allow you to build entire
libraries of authoring that are at your disposal without having to have all
of them included. Only those fragments that contain elements referenced
Unfortunately Windows Installer does not publish any events from its Edit
control. It does update the property associated with the control, but only
when the control loses the focus.
The only reasonable workarounds I see are:
1. You can compare two properties to see if the property was changed
If your feature won't be affected at all by the transaction (such as when
removing a different feature) MyAppFeature may very well be -1, which would
make your condition be true.
-Original Message-
From: Ivo Beltchev [mailto:i...@roadrunner.com]
Sent: Saturday, June 26, 2010 8:11 AM
To:
to run before InstallValidate,
because I want to run before the Restart Manager pops up and asks to
close the app for me.
What is the recommended way to debug such problems? Is there a tool that
can trace through the install process?
Blair wrote:
If your feature won't be affected at all
After building run dumpbin /imports path-to-your-dll and verify that
every DLL listed is part of windows and not a VC runtime. If you find a
non-Windows VC runtime DLL (it'll usually have an 8, 9, or 10 embedded in
the filename) you need to go back to the properties of your VC project and
make
Does your CA DLL have a VERSION resource?
-Original Message-
From: Tim Krehl [mailto:tim.kr...@shavlik.com]
Sent: Thursday, June 24, 2010 9:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] What can cause WcaInitialize to fail?
Yes it is being
assumed this would
always be logged and not seeing this line I assumed the WcaInitialize was
failing. I am looking into the option that the custom action work it
failing which seems a lot more probable. Not sure why logging
isn't occurring.
On Fri, Jun 25, 2010 at 5:39 AM, Blair os...@live.com wrote
Remove the Custom tag and instead Publish a DoAction event from the
Done/Finish/Close button on your finished dialog.
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: Thursday, June 24, 2010 6:36 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
Just looking at it from a naïve point-of-view, and seeing what is on my own
computer (I have two instances of SQLServer installed/running, one 2005 the
other 2008), this is what I see:
If the dependency were local, it appears that the service name is
MSSQL$instancenamepart. Local means that the
In your custom action, create and start a new thread and then wait on it. In
that new thread, initialize COM for STA mode (or just initialize OLE, which
will do that for you) and then call the OpenFileDialog class. After you copy
your file path out of the class, let that thread end, which will
I haven't installed VC Express, but the location for them in VS 2010 is
C:\Program Files (x86)\Common Files\Merge Modules (or C:\Program
Files\Common Files\Merge Modules if your box is 32-bit) but they are an option
for the paid versions of VS (I don't know if they are in the defaults or not).
I'm not certain but I have a guess:
Change Directory Id=XML Name=XML to Directory Id=Xml Name=XML
and try again.
What I am suspecting is that the public name XML is not being changed when
you change the value of INSTALLDIR. By changing the case, you make it a
non-public so it's default value
table with a -1 value.
-Original Message-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
Sent: Monday, June 21, 2010 6:08 PM
To: General discussion for Windows Installer XML toolset.
Cc: Blair
Subject: Re: [WiX-users] Customizing WixUI_FeatureTree
Two problems
In 3.0, all !(bind.*) variables are generated by the binder itself (I think
all of them are file information values) while !(wix.*) values can be
declared in .wxs/.wxi files using the WixVariable element or on light's
commandline (which is populated by WixVariables elements in
MSBuild/Votive).
On a control, like next, on the previous dialog. Order it before the
action involving MyDlg.
-Original Message-
From: gapearce [mailto:mr_gapea...@yahoo.com]
Sent: Tuesday, June 22, 2010 11:28 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Invoking a custom action on entry
No, it does not.
-Original Message-
From: Uma Harano [mailto:uhar...@esri.com]
Sent: Tuesday, June 22, 2010 11:30 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Component rules
Hi,
Does this below break the component rules?
Create one merge module
)' != '' $(Property);ItemTwo/Property
/PropertyGroup
-Blair
-Original Message-
From: Elfe Xu [mailto:elf...@microsoft.com]
Sent: Tuesday, June 22, 2010 5:26 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Undefined preprocessor variable error
Interesting. Why
Not if you use the Windows Installer integration with ARP. You would have to
use the Legacy ARP interface, which requires using the ARPSYSTEMCOMPONENT
property AND programming the uninstall registry key yourself. This has been
discussed on this list before.
However, I don't believe that is what
-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
Sent: Monday, June 21, 2010 12:32 PM
To: General discussion for Windows Installer XML toolset.
Cc: Blair
Subject: Re: [WiX-users] Customizing WixUI_FeatureTree
Basic UI or Reduced UI level installations give the user the option
| www.timeamerica.com
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, June 18, 2010 9:34 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Set package name dynamically
The summary information stream is MSI metadata outside of the MSI
Yes. However, if the bootsrapper (A) runs silently any prerequisite
installations that are not launched with ShellExecute or that are
incorrectly manifested for elevation or that are MSI they may fail if as a
result the UAC prompt for them never appears.
I don't know enough about the bootstrapper
You set your ReadmeDlg the way that ExitDialog is currently invoked, then
have ReadmeDlg's Next button go to ExitDialog. You can then enable/add back
in ExitDialog's Back button and set it to return to ReadmeDlg.
-Original Message-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
ran Setup.exe?
If that is true, does Setup.exe then launch Setup.msi?
Probably I misunderstood how wix and bootstrapper work, can you clarify
please? Thank you!
From: Blair [os...@live.com]
Sent: June-17-10 7:13 PM
To: 'General discussion for Windows
Windows Installer caches a copy of your MSI but it strips out any embedded
cabinets. You'll need the original source for repairs. I'll let somebody
with more knowledge provide advice.
I have heard mentioned that Windows Installer requires that the MSI package
filename does not change
Microsoft Hyper-V Server 2008 R2 is free to download and use, if you don't
have a Server 2008 license available. It requires an x64 box with certain
CPUs that support hardware virtualization.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Friday, June 18,
Also, most people starting an application at the end of an installation do so
from the final UI screen of the installation, often with a checkbox selecting
whether to start the installation or not. WiX has this functionality pretty
much built in (such that it is only offered if the UI was used
Property Id=WriteIIS7ConfigChange Hidden=yes/
It would hide the property, so if you need other parts of that property in
the log for diagnosis you would need to set the Debug policy appropriately.
http://msdn.microsoft.com/library/aa370308.aspx
-Original Message-
From: Pierson Lee (PIE)
Aren't most shell extensions DLLs that Explorer.exe loads when needed? I never
had to run one I installed...
-Original Message-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
Sent: Friday, June 18, 2010 2:39 PM
To: General discussion for Windows Installer XML toolset.
Cc: Blair
med...@layout attribute is used during the build to facilitate placement of
the files into your media layout (the way you transfer your build output
onto your multiple CDs or whatever). The data in that attribute is not
preserved in the MSI and is not available/doesn't alter the way that Windows
, if one were so inclined, you could
reauthor every other MSI file in WiX).
-Original Message-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
Sent: Friday, June 18, 2010 12:11 PM
To: Blair
Subject: RE: [WiX-users] Can this be done with WiX?
Blair os...@live.com wrote
by us and we will change the ProductCode for
all languages at that time.
On Thu, Jun 17, 2010 at 11:08 AM, Blair os...@live.com wrote:
Your certificates are based on ProductCode? There is no reason I can think
of that a Major Upgrade can't retain/reuse files or configuration from a
previous
affect the property itself? It isn't a property I
create, its from the IIS custom action.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, June 18, 2010 2:35 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Password showing in text
There are properties that are defined by the system, properties that are
defined by the package (initial values are in the Property table), and
properties that are created while the installation transaction proceeds
(whether by searches or custom actions).
To see final values for all custom
I see. So as I understand it, I have to keep the MSI around while the
software is installed. Is there a
recommended location for such cached MSIs? And is it even possible for the
MSI to delete itself during
uninstall?
How does Burn handle this?
If the MSI is installed per-user, it would
things, and non-elevated code for launching things.
-Original Message-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
Sent: Friday, June 18, 2010 5:25 PM
To: 'General discussion for Windows Installer XML toolset.'; Blair
Subject: RE: [WiX-users] Can this be done with WiX
The summary information stream is MSI metadata outside of the MSI SQL
database (but inside of the MSI file) and uses a different set of APIs to
access than the rest of the data in the file. Changing it would have to
occur before you start an installation transaction, and if you codesign your
MSIs
is 'redacted'.
Are these the properties?
Andrew
On Fri, Jun 18, 2010 at 4:49 PM, Blair os...@live.com wrote:
There are properties that are defined by the system, properties that are
defined by the package (initial values are in the Property table), and
properties that are created while
How does that file get on customers' machines and why didn't the original
author have it GAC'd in their distribution of that file? Could it possibly
not be intended for use from the GAC? Might that create a security issue?
What if the original installation needs to remove or upgrade that file,
Things in the Binary table are only extracted when other code calls the APIs
to extract them, so the/a custom action would be required to know to get it
from there. To make it more complicated, the extraction code must be run
from an immediate action, so an immediate/deferred pair (immediate to
Look in the Bootstrapper folder, under the Packages subfolder. Each folder
in the Packages folder contains a bootstrapper package. Each package
directory contains a Product.xml file. The root node of those files is named
Product. It has a ProductCode attribute. The value of that attribute is the
From the Candle Task page in the documentation:
InstallerPlatform Optional string parameter.
Specifies the processor architecture for the package. Valid values are x86,
x64, and ia64. (Deprecated values include intel for x86 and intel64 for
ia64.) This is equivalent to the -arch switch in
Your certificates are based on ProductCode? There is no reason I can think
of that a Major Upgrade can't retain/reuse files or configuration from a
previous installation.
-Original Message-
From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com]
Sent: Thursday, June 17, 2010 8:31 AM
Blair for pointing to the place.
When I install on a test machine, I still get the error saying like setup
wizard ended prematurely because of an error. Your system has not been
modified. ..
Cannot figure out why. Here is my code. Can someone help out if you see
somewhere obviously wrong? Thanks
CopyComponents=True
OutputPath=$(OutputPath)
Path=C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Bootstrapper\/
/Target
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: June 17, 2010 4:33 PM
To: 'General
(1) It is common in many big shops that the build platform is standardized
servers which may have little to do with the actual target platform of the
product. Thus, there is often a need to be explicit.
(2) There are many 64-bit packages that install just one 64-bit component
and all the rest of
Installer XML toolset.
Subject: Re: [WiX-users] Detecting MSI dependencies
Thanks Blair that is useful to know (I can see it in the uninstall log
now I look closely).
Mandar, I think the other place to look is the key
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\UpgradeCodes but you
need
The short answer is: Bootstrapper. You need one.
UAC is probably the reason your getting a failure in Win7.
-Original Message-
From: Panop S. [mailto:aun.pa...@gmail.com]
Sent: Tuesday, June 15, 2010 8:28 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] need help ! Error on
It is by design of Windows Installer.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Wednesday, June 16, 2010 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Setting Permissions on a 64 bit system folder from a 32
bit msi.
Hi,
Depends on your servicing strategy. Keeping the same ProductCode for two
different languages can compound small update component rule upgrade
violations if packages from two different languages were ever to be applied
to the same computer, and considering that you can change a computer's
language
You must always use the handle supplied to you from the entry point (custom
action function) into your DLL. Do not ever save it for a different entry
point, because it may not be valid in other calls or any time after code
returned back out the entry point it was supplied to you on. If you have
Look at this control:
Control Id=Finish Type=PushButton ... Default=yes Cancel=yes
Text=$(loc.WixUIFinish)
It says whatever the localized WixUIFinish string is (I assume Finish)
and is the button clicked if you press the Enter key and the button
clicked if you press the Esc key. So,
I have a question: How would you prefer to associate a .REG file with a
binary if you were harvesting an entire directory? Are your .reg files named
the same as your .dll/.exe files?
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday,
If your base XML file (as shared by all three products) is fairly static,
you should be able to create a shared component (a component where the GUID
and the directory are the same for all three products). If your XML
transformations can be applied in any order, you shouldn't have any
problem
Look in a verbose log. It is possible that INIPATH has the merge module's GUID
appended to it in its name.
-Original Message-
From: Jonas Kahlert [mailto:jonas.kahl...@docufy.de]
Sent: Tuesday, June 15, 2010 4:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Modify Ini
'cos it would work really well.
On uninstall FindRelatedProducts is run doesn't that populate the
upgrade table?
Mandar, You could use a registry search for the product/upgrade code but
it is not easy in my experience.
Neil
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 15
I'm assuming you are not trying to change your install directories in your
maintenance transaction.
Already installed components should be correctly repairing in the location
they were previously installed into. Components that were not previously
installed as well as custom actions that use
Upgrade table is not checked during uninstall, so that won't work. You will
need some other means of detecting the dependent installation(s).
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, June 14, 2010 1:42 PM
To: General discussion for Windows
One scenario: If you have a suspended installation (say, the power went out
during a previous attempt) and after starting up the computer again you
restart the installation, the ResumeDlg is the dialog you would see that
would direct you to either rollback or complete the suspended installation.
?
Thanks Blair.
I checked the wix.ca.targets. Seems when using this in our TFS build
environment, I need to do a little change of the path values, because the
wix on build machine is not installed, but by copying files into the public
folder.
@Rob: yes, the articles in wix document are very clear
The magic inside is the following line at the bottom of the csproj file
(AFTER the line that imports the Microsoft.CSharp.targets file):
Import Project=$(WixCATargetsPath) /
That line requires the following properties and items be set in your csproj
file:
CustomAction.config must be included as
and then there's done. If all goes well, I hope to get
the source code posted this weekend (my wife is away so I'll have some
quality coding time). After that, you'll be able to see how it can be done
with Burn.
On Thu, Jun 10, 2010 at 2:33 PM, Blair os...@live.com wrote:
Burn will support that scenario
sequence where you know that TOMCATHOME is
properly set (before you consume T2) and use a SetProperty instead of a
Property element to assign T2.
Blair
--
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad
Session.GetProductProperty can only be used on a Session obtained from the
Installer.OpenProduct method, which is documented as not able to be used in
a custom action (realize that DTF is intended to be used in much more than
just custom actions).
If you are looking for the AGENT_SERVER
or WIX3.5beta?
I agree *except* IIS support. IIS7 support in WiX v3.5 is still having the
bugs worked out.
On Wed, Jun 9, 2010 at 6:53 PM, Blair os...@live.com wrote:
The core toolset in 3.5 is quite stable, but it is still recommended that
you upgrade at least every month (grabbing the latest weekly
drivers.
Also, there is a current bug where the directory is not removed after
the custom action is done.
Kurt
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, June 09, 2010 6:06 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re
Burn will support that scenario when it is done because it gives the
developer complete control over the UI. However, it won't be done until the
end of 3.6.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, June 10, 2010 7:42 AM
To: General
I believe it would be something like:
Session.Property(TOMCATHOME)
-Original Message-
From: cge [mailto:ell...@avaya.com]
Sent: Thursday, June 10, 2010 2:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Evaluate property
I have a registry entry that contains a directory:
Does your framework installation use an UpgradeCode? If so, you can use the
UpgradeTable to locate it. Just make sure you put OnlyDetect=yes on those
entries that set your detection properties.
You can use the Upgrade element several times in your WiX code and the
Upgrade value for each can be
A couple of observations:
Add Impersonate=no to your CustomAction declarations. That attribute
defaults to yes. You are impersonating the installing user instead of
running those CAs as SYSTEM.
Normally custom actions are run from the Binary table instead of the File
table, unless you also need
The core toolset in 3.5 is quite stable, but it is still recommended that
you upgrade at least every month (grabbing the latest weekly release each
time) until it RTMs.
The stuff in 3.5 that is not in 3.0 has less bake time than most of the
toolset, but if you are not using any of that, it
They have the same GUID because they both are related to the same Merge
Module (the guid is your merge module's guid).
The warning is ignorable because the two properties don't depend on each
other. Mergemod.dll from Microsoft's own SDK is what creates those actions,
and I don't know of a way to
See
http://blogs.msdn.com/b/heaths/archive/2006/10/25/how-windows-installer-uses
-languages.aspx for a really good analysis on how these two values are used.
packa...@languages becomes the PID_TEMPLATE value that Heath mentions
(defaults to the produ...@language value), while the produ...@language
When and in which table(s) is your DLL sequenced? What does the installation
log say?
-Original Message-
From: vijay chander [mailto:vijaychander2...@gmail.com]
Sent: Monday, June 07, 2010 5:20 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Can we control registration of
, 2010 at 10:46 AM, Blair os...@live.com wrote:
To use your new error 25001 you need to call (something in your custom
action that will eventually call) MsiProcessMessage passing it the
INSTALLMESSAGE_ERROR value and a record that includes your error number as
described in the page http
, 2010 at 9:56 AM, Blair os...@live.com wrote:
I don't know if it as simple as removing the quotes or not:
UI
Error Id=25001!(loc.Error_25001)/Error
/UI
Also, your light.exe commandline looks more like WiX v2 instead of WiX v3.
-Original Message-
From: Pratapa Reddy Sanaga
In v2 it was $(loc.StringId). That was changed to !(loc.StringId) in v3
(IMHO to make it more obvious when the replacement happens [precompile vs.
late-stage linking/binding]).
V2 users must use MSI-SDK tools for creating transforms. See MSDN for
examples.
-Original Message-
From:
Generally MSIs are authored to remove previous installations that they
replace. However, any MSI can be authored to remove pretty much any
arbitrary set of MSIs upon installation.
Also, to help you in your knowledge search, the process that installs (and
possibly uninstalls) several different
To use your new error 25001 you need to call (something in your custom
action that will eventually call) MsiProcessMessage passing it the
INSTALLMESSAGE_ERROR value and a record that includes your error number as
described in the page http://msdn.microsoft.com/library/aa371614.aspx.
The custom
://msdn.microsoft.com/en-us/library/aa367525(VS.85).aspx
Or is there a way to do it in the wix file somehow. I haven't found
anything, but hoping there's something other than the c++ option.
Thx, Craig
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, October 14, 2009 10:49 AM
The service doesn't exist until StartServices. BTW, the StartServices action
will start all services that show up in the ServiceControl table. I
recommend you read the following blog:
http://www.joyofsetup.com/2007/07/01/semi-custom-actions/
-Original Message-
From: gapearce
Sorry, I meant InstallServices. But around StartServices (or after) is when
you want to schedule starting your service.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, June 03, 2010 9:26 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re
Looks like a bug. Do you have the stack trace?
-Original Message-
From: Francesc Castells [mailto:fcaste...@dgtexperts.com]
Sent: Thursday, June 03, 2010 6:34 AM
To: wix users
Subject: [WiX-users] error LGHT0001: Unable to cast object
Hi,
I'm using WIX 3.0.5419.0 in a VS project. I'm
Do your transforms change the ProductCode or not?
The only way that two instances of a product can be installed side-by-side
is if they have different ProductCodes. Otherwise, the second instance is
simply an minor update of itself and the first instance no longer
exists.
-Original
SQL Server is likely being shut down by Restart Manager (via Windows
Installer's integration with Restart Manager). You would probably need to
disable MSI's use of RM.
-Original Message-
From: Nathan Zaugg [mailto:nza...@gmail.com]
Sent: Thursday, June 03, 2010 11:12 AM
To: General
to cast object
Not sure. Does light log by default somewhere? that message is the only I
get on screen.
On Thu, Jun 3, 2010 at 5:42 PM, Blair os...@live.com wrote:
Looks like a bug. Do you have the stack trace?
-Original Message-
From: Francesc Castells [mailto:fcaste...@dgtexperts.com
for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Message-ID:
b44aabaf1aea674cad53f403cba619acdfd...@exchange.dk.sitecore.net
Content-Type: text/plain; charset=us-ascii
Hello Guys,
I apologies for the long silence.
Blair: Why do you need it?
Well, I now
Chander
Date: Thu, 3 Jun 2010 18:16:49 -0700
From: Blair os...@live.com
Subject: Re: [WiX-users] Unable to use msiexec /i WIXinstaller.msi
/qn
To: 'General discussion for Windows Installer XML toolset.'
wix-users@lists.sourceforge.net
Message-ID: blu111-ds17820bdb2ed2a707429e92cd
Use the UILevel property.
http://msdn.microsoft.com/library/aa372096.aspx
Blair
-Original Message-
From: vijay chander [mailto:vijaychander2...@gmail.com]
Sent: Thursday, June 03, 2010 10:18 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Through WIX how to know whether
Also, if there is no scripted UI, the InstallUISequence table is skipped.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, June 03, 2010 10:46 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Through WIX how to know whether
//
// MessageId: ERROR_OPEN_FAILED
//
// MessageText:
//
// The system cannot open the device or file specified.
//
Sequence issue? What CA are you using to access the .config file?
-Original Message-
From: Velu [mailto:velusa...@syncfusion.com]
Sent: Wednesday, June 02, 2010 6:50 AM
When an installation is suspended, properties that have already been setup
are retained, so what you see is by design (text straight from the DB is
transformed, text from properties is not). You need to either complete the
previous installation or roll it back.
-Original Message-
From:
Your application would have hold a lock on those PNG files that denies
Delete (via sharing mode) using its file handle until the application is
shutdown.
-Original Message-
From: Stefan Kuhr [mailto:kustt...@gmx.li]
Sent: Tuesday, June 01, 2010 3:45 AM
To: wix-users@lists.sourceforge.net
Wix actions can be set into verbose mode by setting the property
LOGVERBOSE to 1. (read the comments in the following blog post:
http://www.joyofsetup.com/2008/07/15/verbose-logging-from-wcautil/).
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday,
?
Hi Blair,
I did some more investigation and reading archived posts to this group.
Until now I had RemoveExistingProducts scheduled before InstallInitialize in
all my installs. If I now schedule it after InstallFinalize, everything
seems to work. Is this the way to go? Is there any downside
The path of the CommonAppData directory is found in the CommonAppData
property after CostFinalize. The same with all the entries in the Directory
table.
-Original Message-
From: Joshua Chambers [mailto:jos...@tdronline.com]
Sent: Tuesday, June 01, 2010 12:43 PM
To:
901 - 1000 of 1942 matches
Mail list logo
