hi all,
i'm getting a strange issue like, while installing an update(PATCH) on top
of my installer. after license dialog, installation is stopping with out any
error thrown. while digging into the logs it says as follows:
DlgLicense] User Response: 3002
MSI (c) (C8!78) [11:30:26:531]: PROPERTY CH
>> Long story short: XmlFile is being executed during upgrades when I
>> only want it executed on new installations.
>>
>
> The owning component controls whether XmlFile is run; conditionalize it
> so it doesn't run during upgrade.
Thanks for the reply Bob, unfortunately I already tried this with
Hi All,
It seems that the light.exe in Wix3 is much slower than Wix2. Does anyone know
the reason? Or is there any way to speed up the linking processing in Wix3?
I've tried to use -sval to turn off the ICE validation. But it seems that the
ICE validation doesn't take much time. So what is the
Could you send the lines from the log starting from
InstallWindowsFeaturesDeferred returning to the second mention of "rollback"
following the above line? Also, which version of MSI?
-Original Message-
From: Lian Jiang [mailto:lji...@microsoft.com]
Sent: Monday, September 21, 2009 5:16 PM
Thanks Blair for your explanation.
I tried:
As you see, I removed "Return='ignore'" from InstallWidnowsFeatures and set
Return='ignore' in InstallWindowsFeaturesDeferred.
The compile can pass without ICE68 error but running msi failed because the
return value is not 0 (shown in the log)
We use Wix 3.0.
We have this code to show support url in ARP:
In XP and Windows 7, it works - we can see the url when checking ARP. But in
Vista, the support info url field is empty. In the log of the Vista
installation, the ARPHELPLINK is setup:
Property(C): ARPHELPLINK = http://www.thecomp
A so-called SetProperty "custom" action is a built-in type (it is a Type 51
custom action), and setting a session property value isn't ever expected to
fail. Why do you want to set Return='ignore'? And what would you do in your
deferred action if the immediate SetProperty ever did fail?
Because yo
Hi,
I have a custom action:
When I compile, it failed due to ICE68 - Invalid custom action type for action
'InstallWindowsFeatures'.
If I bypass ICE68 when linking, running the msi will fail with "Custom action
InstallWindowsFeatures specifies unsupported type".
The trick is that if I
>From the immediate side: a CustomActionData is a property with the same name
as the deferred/rollback action it is intended for. From the
deferred/rollback action: it is a session property with the name
"CustomActionData".
The WiX custom actions are almost all of the following model:
Immediate cu
Hi Blair,
That makes sense. I tried it as a deferred action, but ran into errors running
the custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. --->
Microsoft.Deployment.WindowsInstaller.InstallerException: Cannot access sessio
Immediate custom actions don't participate in the installation/rollback
script and can't be elevated (unless you started the installation elevated
or you turned off UAC). They also may have run before the part of the
deferred script that actually writes the file to disk runs. All custom
actions tha
Hello,
I'm creating an installer for an Office Add-in that uses some .NET components
which requires changes in CASPOL. I've had some success creating the code
groups using CASPOL in a custom action based on some code that I found for
installing Office Add-ins using the Visual Studio Installer b
You should be able to use the Session that is passed into your custom action
code. Then just do Session.Log("Message") to write your custom message to the
log file.
Note that this does not work if your custom action is invoked from a dialog.
In that case, you can have your custom action write
If you're reasonably certain that you will never need R2 again:
I assume V1 looks like this:
<... Id='R2'/>
<... Id='R3'/>
For V2:
Preferred
1: Change ProductCode(s) (make this a major upgrade)
2: Force an updated version resource in R1 (sorry)
<... Id='R3'/>
I can wor
I would be interested in seeing the design of the merge module as well as
install logs.
With my previous employer we designed and had written much of such a tool
(integrated into our evolving build system). I have plans to write such a
tool, if there is interest I could push it up in the list.
--
In version 1 of my application I have a component C1 which contains multiple
resources.
C1 = { R1, R2, R3 }
The file R1 is the key path for C1.
The rest of the application requires that the resources are installed with
the same path and names in V1 and V2.
In version 2 of my application I need
Check out:
http://blogs.msdn.com/astebner/pages/8999004.aspx
The tool supports a silent mode with return codes indicating state. I guess
you could call that as part of a custom action ( assuming it's redistributable
) but I didn't go down that road and I'm not sure if I'd want to or not.
Ei
The problem seems to have occurred on a few customer installation over
the last week or so. Some are institutions where the machines should be
pretty well locked down, so I have asked them how they install the .Net
3.0 Framework to get a handle on this.
Ultimately it is a user issue and they will
Thank you! It works!
-
!
--
View this message in context:
http://n2.nabble.com/C-two-custom-actions-from-one-DLL-tp3663658p3685278.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Come build with
Getting back to the original problem. The files that were missing after my
major upgrade install were in a merge module that I created that was the
same in both products and therefore followed the component rules (since
there were no changes to the install path or content of any components).
Woul
For the reused component, that should be defined in a merge module
that gets merged into each download. The component reference counting
done by the Windows Installer should then only remove it when the
reference count is zero.
I don't have any ideas about the activation issue other than to
sugges
This is a new problem area to me. I know .NET 3.5 has the client profile
deployment model, but does 3.0? What is causing you to have an incomplete 3.0
installation?
We had a problem once where a machine that was syspreped was missing some .net
3.5 components. This seems to be a common probl
Hi All,
I have a question relating to the installation of .Net 3.0.
According to this page:
http://msdn.microsoft.com/en-us/library/aa480217.aspx#winfxdeployreadme_
topic6a
it is possible for a sys-ad to deploy .Net through active directory
without certain elements, such as WCF/WPF
Hi experts,
I am relatively new to WiX have created some msi packets which work
pretty good, and now I am seeking some time-saving leads/doc
links/hints, how I can create what I consider a fairly complex
installation scenario.
Here are the basic infos you need:
a software is to be installed,
In my WIX source 2 properties are defined (both are path to folders)
their default is directories I created in the wix. for example:
WIXUI_INSTALLDIR
.
.
from the definition you can see that the default value is c:\p
Hello,
I want to deploy a temp file and merge a file already
installed and delete that temp file at the end of installation. I want to know
how to make sure the temp file was
delete after merged? I know that we can
use RemoveFile element when a component selected but this done before merge.
Maybe this thread can answer your question
http://www.wixwiki.com/index.php?title=NetFxExtension
--- On Sat, 19/9/09, Steve Lessard wrote:
From: Steve Lessard
Subject: [WiX-users] requiring .NET 3.5 or greater
To: "'General discussion for Windows Installer XML toolset.'"
Received: Saturday
27 matches
Mail list logo
