That looks like a message box from a custom action. It's vaguely possible
it's coming from a WiX CA, but either way, you'll need to get a verbose log
of the install to see where it's coming from.
Phil W
-Original Message-
From: Kannan24 [mailto:skan...@syncfusion.com]
Sent: Tuesday,
There are a few things that may be worth mentioning...
ExeCommand='[TARGETDIR]Windows\System32\net.exe user wsdUser wsdPasswd'
That doesn't look right. TARGETDIR is your application folder, typically
the browsable one, and having it prefix the system folder seems wrong. Also,
if you need the
(or add) features. Using features like this is generally safer if the two
components you're referring to are connected in some way and perhaps sharing
files.
Phil Wilson
From: vij [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 31, 2006 9:37 PM
To: [EMAIL
It may be that features are what you could use. If each component is in its
own feature then users can go to the single entry in Add/Remove and choose
to add or remove each feature.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stefan
Calling Assembly.Load and checking the GlobalAssemblyCache property should
work. Another alternative might be the obscure
IAssemblyCache::QueryAssemblyInfo call (C++).
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joe Kaplan
Sent: Friday
This is a list of some of the possible causes for 1603:
http://support.installshield.com/kb/view.asp?articleid=Q107182
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, August 24, 2006 9:22 PM
To: Joe Kaplan
Cc
Sequence the custom action before files get copied so yes, somewhere early
in the sequence is fine.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Biryukov
Sent: Monday, August 07, 2006 1:28 AM
To: [EMAIL PROTECTED]; wix-users
version of your product it will
be silently uninstalled. Whether there is an older version or not, every
install will be an install of a new product.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter G.
Sakhno
Sent: Wednesday, July 26
I don't *think* this surprises me. In the standard
search for assemblies (as in MSDN "How the runtime locates assemblies") if the
assembly is in the GAC it gets used, and if there's also one in the application
folder it gets ignored.
Phil Wilson
From: [EMAIL PROTECTED]
[mai
is missing when the service is started.
If it doesn'r start at reboot time, this can be a dependency on another
service that you haven't configured.
As an aside, you should look at MsiHiddenProperties as a way of not exposing
passwords in a log!
Phil Wilson
From
This typically means that schema of the MSI file (such as 200 for MSI 2.0)
is higher than the current version of MSI on the system.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 7:45 AM
To:
and these ref counts get set on folders you might get into the
situation where the folder and therefore the files it contains cannot be
removed because there is a SharedDlls ref count on that folder. This is
just another reason to not cause msidbComponentAttributesSharedDllRefCount
to be set.
Phil Wilson
601 - 612 of 612 matches
Mail list logo
