I am using Wix 3.6.
Unfortunately, I do not see any error message :(
Here is a part of the log file :
[0F8C:0F90][2011-11-03T09:47:10]: Apply complete, result: 0x0 restart: No
[0F8C:0F90][2011-11-03T09:47:10]: Shutting down, exit code: 0x0
[0F8C:0F90][2011-11-03T09:47:10]: The prerequisites were
Not being able to modify the shortcut is what I expected but no permissions at
all, i.e. not being able to see it as a shortcut only as a file that the user
can't double click to start or even have permissions to see it's icon, that is
not what I expected.
Kjartan
-Original Message-
I'm writing an installer for a WDF driver, and am finding that
MsiProcessDrivers is being run after files have been removed. The
problem is that according to the documentation, I need to run
WdfPostDeviceRemove() after the service has been deleted - which
requires WdfCoInstaller01009.dll to be
Hi Guys,
This is my first email to this list. I have already seen the very same
problem somewhere else, but there was no satisfying solution to it.
I have 7 installers created with WiX. 3 of them are windows services. Most
of them use post-install and pre-uninstall scripts in the form of batch
On 03/11/2011 11:54, Bruce Cran wrote:
I'm writing an installer for a WDF driver, and am finding that
MsiProcessDrivers is being run after files have been removed. The
problem is that according to the documentation, I need to run
WdfPostDeviceRemove() after the service has been deleted - which
I made a lot of payloads but now seem to have another problem. I try to
assign the following SourceFile to a Payload element:
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700.cat
However, when I attempt to build it I get the following:
error LGHT0103: The system cannot find
Hi,
It turned out that all of the missing entries were of type rawBase and it was
expected behavior not to show them. But the problem with gathering data still
exist: it should be able to work with multiple instances and setting on/off
MultiInstance attribute does not allow to catch anything.
Is it possible to create a burn bundle that will install either a
32bit or 64bit msi depending on the architecture? I am creating a
custom BA already if that is what is needed.
Dieter Lunn
http://ubiety.ca
--
RSA(R)
I browsed the bug database and eventually found out
https://sourceforge.net/tracker/index.php?func=detailaid=2086871group_id=105970atid=642714
pyro actually diffs the files on disk and not from inside the MSIs. In
other words, the 'before' and 'after' copy of files have to exist at the
same
If you do an admin install from the source and target MSI's, you get the files.
--
John Merryweather Cooper
Jack Henry Associates, Inc.
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: john.burak
I'll try to experiment with that sometime today. My assumption (from the
bug-report comment) was that pyro or torch used the original source paths
for the files, which won't be the same as the administrative install
locations for my installers.
This is all very strange to me. I feel like I must
Marcin,
We had similar issues, so decided to just create the performance counters
when the application is started the first time, have you thought about doing
that? (we allow our customers to configure which counters they actually want to
use because we have over 15,000 metrics available
Yes. Put both MsiPackage elements in your Chain and Condition them
appropriately. The default Burn behavior should be what you'd expect.
On Thu, Nov 3, 2011 at 10:46 AM, Dieter Lunn coder2...@gmail.com wrote:
Is it possible to create a burn bundle that will install either a
32bit or 64bit msi
During my products lifetime there are a lot of files that will have been
created in my applications bin folder, for example .config files. I
currently just remove them at uninstall by having entries in the RemoveFile
table.
I would on occasion like to be able to leave the files behind on
Found under
C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\SQL Server
Compact Edition
This is part of the SDK for Win 7 .NET 3.5
SP1http://www.microsoft.com/download/en/details.aspx?displaylang=enid=3138.
I would think it would be part of
I think I figured it out! Using the pyro/torch approach, patching can be
done from MSIs without the original source dirs. Sorry to add so much noise
to the list.
For the benefit of future generations, here is what I did that differed from
the
That is essentially how I do it. I have a wixproj hacked to make my patch. In
a PreBuildEvent, I have:
if exist $(ProjectDir)Target\Admin\some.msi del /q
$(ProjectDir)Target\Admin\some.msi
if exist $(ProjectDir)Target\Admin\some-install-dir rmdir /s/q
17 matches
Mail list logo
