Getting the following exception while executing candle.exe from Mapped
Network Drive(i.e. Z:\)
Z:\workspace\workspace\WindowsBuilds\IRPortal\repackaging\IRPortal\wics>Z:\WiX\c
andle.exe -ext WixUtilExtension -ext WixIIsExtension -nologo -pedantic
-dProdu
ct_Id=* -dProduct_UpgradeCode=C3E163
Sorry to say, but I have validated it to work from the command line. The WEVT
should have 3 parameters - im, /RF and /MF and the command line I do see in
the logs only has one. Care to explain that?
When I register all three manually it works.
When I rely on the WIX generated call, it does not
Hey guys, I'm running into some really strange behavior with managed Custom
Actions (C#) and DTF's compilation (?) of them. I've made a few WIX
installers before, all with C# Custom Actions, and never run into this
before, so I think I've covered all the basics and it's got me really
scratching my
I have not worked with callout drivers, but your comment that the INF does
not have a SourceDisksName section and yet you get a file not found error
implies that the Class setup application processing the INF file is trying
to do a file copy. In looking on msdn at "INF Files for Callout Drivers" i
Hi,
your components are correct, I use it the same way and it is working
properly. IMHO the call to wevtutil in your log looks correct too, as the
custom action will adjust the resource and message file paths in the
manifest XML. No need to pass those to wevtutil.
If I remember correctly, the har
While I am not doing what you are doing, and I have a lot to learn about
wix/msi, when I tried to install several different pnp printer drivers, each
of which install using non-msi setup by calling the Difx API (or by using my
SetupAPI app), I could not get them to install using DifxApp in wix. I
Ok, I'll try that again.
There was some reason that perMachine wasn't working before but I'll try it
again.
Feb 3, 2014 04:22:18 PM, wix-users@lists.sourceforge.net wrote:
===
Set your InstallScope to "perMachine". If your product must install in the
Set your InstallScope to "perMachine". If your product must install in the
Program Files tree, then it needs to be "perMachine".
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.c
Thanks Phill.
You're right; WFP drivers are non-PNP drivers. I did try to use the legacy
flag, but then the installer was complaining that the .sys file was missing
even though it was copied properly to the target folder. I'll give it
another try. Otherwise, I'll have to make a custom app that ins
Phil, sorry, correction, my configuration is:
InstallScope="perUser"
InstallPrivileges="elevated"
On 02/03/2014 02:52 PM, Gerry Reno wrote:
> InstallPrivileges="elevated"
> InstallScope="perMachine"
>
>
>
> Feb 3, 2014 02:31:46 PM, wix-users@lists.sourceforge.net wrote:
>
> =
Thanks for the ideas. I will study them.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-Attributes-tp7592263p7592319.html
Sent from the wix-users mailing list archive at Nabble.com.
-
InstallPrivileges="elevated"
InstallScope="perMachine"
Feb 3, 2014 02:31:46 PM, wix-users@lists.sourceforge.net wrote:
===
What relevant settings are you using now? InstallScope="perMachine"?
Anything else?
---
Phil Wilson
On Mon, Feb 3, 20
I'm assuming there isn't a simple check you could do based on
VersionNT64 because you have a mix of 64 and 32 bit CAs, so...
The kind of thing you'd do at run time is the usual SQL query game.
MsiGetActiveDatabase, MsiDatabaseOpenView() with a SQL Select that
returns the component's attributes, th
I think that dialog is part of Windows, so you can't modify it.
---
Phil Wilson
On Sun, Feb 2, 2014 at 9:40 PM, ak m wrote:
> Dear All,
>
> Can we hide the intial processing dialog in Wix?
>
> Attached Screenshot for reference...
>
> Best Regards,
> Anil
>
> Wix_InitialProcessingDi
I do not have experience with WFP callout drivers, however I observe that
msdn indicates that they are non-PNP drivers. The DifxApp by default
installs PNP drivers. I assume that the basic process of installing the
driver by right-clicking the INF is successful. If setting the legacy flag
for Di
WiX generates MSIs etc for you to install, but after that there's
nothing running on the system except your app. The type of update you
want is typically done by implementing:
1. A web service at your company site with access to a database of
product guids, upgrade code guids, version, and downloa
What relevant settings are you using now? InstallScope="perMachine"?
Anything else?
---
Phil Wilson
On Mon, Feb 3, 2014 at 10:38 AM, Gerry Reno wrote:
> I am still having difficulty getting this install to work reliably.
>
> Today I go to uninstall / reinstall on this Win 7 machine w
The MSCOMCTL merge module (and most likely the others) contain COM
registration in the class table, so you don't need to harvest it -
that is the whole point of the merge module. It's easy enough to check
with Orca. If your source MSI file didn't contain a Class table then
the merge would (or shoul
FYI: I just tested this and it does the upgrade no problem.
Background: My bundle is composed of a per user MSI which installs my
application and three per machine MSIs which installs two drivers and a
certificate to prevent the "do you want to allow this driver from unknown
company " popup.
I am still having difficulty getting this install to work reliably.
Today I go to uninstall / reinstall on this Win 7 machine w/UAC enabled and it
refuses to install.
First, I uninstalled the previous install. It asked for permission to change
things on the machine. I said OK and it uninstall
I'm attempting to install a WFP (Windows Filtering Platform) callout driver
via WiX. All the driver's .inf file does during installation is to copy the
.sys file to the Drivers folder and that's that.
The driver isn't a "typical" driver in the sense that its .inf file doesn't
have a SourceDisksN
Hello
We want to write installers in WIX as it gives us lots of flexibility. But we
also want the auto-update system that ClickOnce provide.
We want the end client to see an icon at the bottom right informing them that
there is a newer version available.
Can WIX do this?
I found this article but
Hi Bob,
Thanks for the feedback. I can understand why burn doesn't presently support
it. I'm not opposed to implementing the feature but will have to look into what
is involved.
Dan
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Sunday, February 02, 2014 7:29 P
I am not sure, but I think a bafunction.dll with WixStdBA (3.8) could be used
to change the behavior of UI controls. I started down that route based on
information at http://wixextba.codeplex.com/. Then several months ago I
also decided to create a mba, so my memory about bafunctions may be getti
I understand that component attributes are bit flags. I want to test for the
64 bit flag in my immediate CA, which schedules a deferred CA, so that I
know whether the CA is running on a x64 architecture. There are several
examples in the source code of testing the component attribute flag in
secu
Hmm, this is interesting
I created a small VB6 app that used the MS Flex Grid. This means it needs the
MSFLXGRD.MSM in the setup.
Using WIX my installed test app failed because MSFLXGRD.OCX was missing a
dependency.
However, if I add
In my wix source file and recompile everything
After some more research the question again.
Is the EventManifest (in the utility namespace) broken or do I just use it
wrong?
EventManifest is the WIX version of wevtutil.
In order to properly register one needs three parameters - the manifest and 2x
the compiled manifest.
Regardless how I a
27 matches
Mail list logo
